Appearance
Usage & Quotas
Your plan decides how much your organization may use at once. The usage page shows the plan's limits and what the organization uses now. Check it before scaling workloads, adding replicas, creating storage, or opening more editors.
Opening Usage
Go to Settings > Usage ("Resource Usage"). Every member can open it. The Plan limits section shows what your plan allows, grouped as Editor, Apps, CI / CD and Organization.
Default Limits per Plan
| Starter | Basic | Team | Enterprise | |
|---|---|---|---|---|
| Members (seats) | 1 | 10 | 50 | 500 |
| Editors running at once | 1 | 2 | 5 | 100 |
| Saved editor workspaces | 3 | 10 | 25 | 200 |
| Largest editor size | Small | Medium | Medium | Large |
| App pods, all deployments together | 3 | 10 | 25 | 100 |
| App CPU / memory reserved, total | 1 CPU / 2 GiB | 4 / 8 | 12 / 24 | 64 / 128 |
| Largest single container (CPU / memory) | 1 / 2 GiB | 2 / 4 | 4 / 8 | 16 / 32 |
App data volumes (/data), per environment | 3 | 10 | 25 | 100 |
| CI runner pods | 2 | 3 | 5 | 20 |
| Git storage | 2 GiB | 5 GiB | 20 GiB | 100 GiB |
| PostgreSQL databases (storage) | 1 (5 GiB) | 1 (10 GiB) | 10 (50 GiB) | 20 (500 GiB) |
These are the platform's defaults. Shaep can set different values per plan, or grant your organization custom capacity; the Plan limits section always shows what applies to you. During a free trial, the limits of the plan you picked apply.
Dev and Prod Share One Allowance
App pods, CPU and memory are counted over every deployment in the organization, dev and prod together, and so are PostgreSQL databases. On Starter and Basic that means one database in total, not one per environment. Editors, CI runners, seats and git storage are counted for the whole organization. App data volumes are counted per environment; a stopped app keeps its volume, and so does an app whose storage was switched off, until the app is deleted.
What Is Checked, and When
| When you… | What is checked |
|---|---|
| Create, scale, update or start a deployment | Replicas, CPU and memory against the shared allowance, and the per-container maximum. A stopped deployment reserves nothing. |
| Create an app with persistent storage, or turn storage on | Data volumes in that environment. |
| Create an editor | Saved editor workspaces. At the limit for running editors, the new editor is created but left stopped. |
| Start an editor | Editors running at once, and the largest editor size. |
| Configure CI runners | Runner count, CPU and memory. |
| Create a workspace | Git storage; there is also a hard cap of 50 repositories per organization. |
| Invite a member | Seats, when inviting and again when the invitation is accepted. Open invitations do not take a seat. |
| Provision a database | Number of databases and their total storage. |
If something is over a limit, it is refused with a message that names the limit, what is in use and what your plan allows. Nothing that already runs is removed because of a limit: not after a downgrade, and not when a trial ends. Only growth beyond the limit is refused.
Troubleshooting
| Symptom | What to check |
|---|---|
| A deployment is refused with a pod, CPU or memory limit | Dev deployments count too. Stop or scale down deployments you don't need, or upgrade the plan. |
| An app with storage is refused with a data volume limit | Run the app without persistent storage, or delete an app you no longer use. Switching storage off does not free a volume. |
| A new version never starts; the app says "A new pod was refused" | The environment is at its limit and the update needed one more pod for a moment (a rolling update). Stop or scale down another app, switch the app to the Recreate strategy, or upgrade, then redeploy. The previous version keeps running meanwhile. |
| A new editor is created but stays stopped | You are at the limit of editors running at once. Stop another editor, then start this one. |
| An editor cannot be created | All saved editor workspaces are in use. Delete an editor you no longer need; stopping one keeps its workspace and its slot. |
| An invitation is refused, or cannot be accepted | All seats are taken. Remove a member or upgrade the plan. |
| A database cannot be provisioned | Check the number of databases across dev and prod together, and their total storage. |
| Usage looks stale | Refresh the page and check Support & Status if the value still does not update. |
Only an owner can change the plan, from Settings > Subscription.