Usage & plan limits
Every plan carries a set of ceilings — how many projects you can create, how large a service can be, how long logs are kept. This page lists what plans gate, where to watch your live usage, and what happens when you reach a limit.
What plans gate
Plans differ on:
- Projects and environments — how many of each the account can hold. See projects & environments.
- Services — how many services of each type (web, Postgres, Redis) the account can run.
- Seats — how many members the account can have.
- Service size — the largest CPU and memory a single service may request, and how many replicas it may run. See resources & scaling.
- Deploy locations — how many locations a single service may run in, and whether multi-location deploys are available at all.
- Custom domains — whether you can add them, and how many. See custom domains.
- Deployment history depth — how far back you can roll back.
- Log and metric retention — how long logs and metrics are kept.
- Git auto-deploy — whether pushes to a connected repo can deploy automatically.
The numbers live in the plan comparison, rendered from the current pricing config:
| Free | Plus | Pro | Enterprise | |
|---|---|---|---|---|
| Base price | $0 | $20/mo · $200/yr | $60/mo · $600/yr | Contact sales |
| Seats included | 1 | 3 (extra $8/mo) | 10 (extra $6/mo) | 25 |
| Monthly compute credit | — | $20/mo | $60/mo | Contact sales |
| Projects | 1 | 10 | Unlimited | Unlimited |
| Locations per service | 1 | 2 | 5 | 10 |
| Free web service | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB |
| Free Postgres | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB |
| Free Redis | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB |
| Custom domains | — | 3 | 25 | 100 |
| Auto-deploy from Git | — | ✓ | ✓ | ✓ |
| Priority support | — | — | ✓ | ✓ |
| Log / metrics retention | 1 d | 7 d | 30 d | 90 d |
| Deployment history | 10 versions | 30 versions | 100 versions | 500 versions |
On the Free plan the ceilings are exactly the always-free allowance: one free unit (0.5 vCPU / 1 GiB) of each service type, and nothing above it. Custom domains, git auto-deploy, and multi-location deploys start on the paid plans — the table shows which.
Watch your live usage
- Open your account and go to Usage in the sidebar.
- The Plan limits section shows live counts against your plan's ceilings — projects, environments, members, custom domains, and services of each type.
- The page also shows the compute you've accrued this cycle, the plan credit applied, and the resulting net — see billing for how that's computed. The cost meters are visible to the account owner.
When you're over a limit — for example after a plan change — the Usage page shows a banner naming exactly which limits you're over.
When you reach a limit
An action that would cross a ceiling is refused — nothing is silently changed or shrunk. The message names the limit you hit and the smallest plan that fits what you tried, and the console offers the upgrade right where you were working.
The API answers the same way: the request fails with a quota_exceeded error that carries the plan to upgrade to.
Downgrades and limits
A downgrade to a plan below your current usage never discards anything on its own. You resolve the excess first — letting Koo shrink what can shrink, and choosing what to remove where the target plan can't hold it. The flow is described under Downgrade on the billing page.