Limits and quotas
Aozumi is in beta, and workspaces start with the same limits. Reaching one never stops what is already running.
Workspace limits
| What | Limit | Notes |
|---|---|---|
| Apps | 5 | Delete an app you no longer need to make room. |
| Deployments | 20 per 24 hours | A rolling window. Failed and cancelled deployments do not count. |
| Members | 10 | Per workspace. |
| Pending invitations | 10 | Unanswered, unexpired invitations. |
| Custom domains | Capped per app and per workspace | The console shows the cap when you reach it. |
| Managed Postgres | Capped during the beta | Size and count are limited. |
Size limits
| What | Limit |
|---|---|
| Static site release | 5,000 files, 256 MB |
| Prebuilt server artifact (CLI) | 512 MB |
| One secret value | Under 32 KB |
| .env import | 256 KB and 200 variables per file |
When you reach a limit
Aozumi refuses the new action and tells you which limit applies and how to free room, for example by deleting an app, waiting for an older deployment to leave the 24-hour window, or cancelling an unanswered invitation. Apps that are already running stay up, and nobody is removed automatically.
Need more room for a real project? Email support@aozumi.dev.
Questions
- How many apps can I deploy on Aozumi?
- During the beta, each workspace can have up to 5 apps and start up to 20 deployments in any 24 hours. Failed and cancelled deployments do not count.
- What happens when I hit a limit?
- The action is refused with a message that names the limit and how to free room. Nothing already running is stopped or removed.
Checked against the product on .