Limits
Limits apply per tenant: your personal account and each organization have their own. They depend on the plan.
Resources
Section titled “Resources”| Free | Pro | |
|---|---|---|
| Apps | 3 | 15 |
| Memory per app | 512 MiB | 512 MiB |
| CPU per app | 0.5 | 0.5 |
| Volume | one per app, 2 GB | one per app, 2 GB |
| Databases | 1, with a 2 GB volume | 5, each with a 2 GB volume |
| Custom domains | none | 5 per app |
| Upload | 200 MB compressed |
flitzy whoami and the dashboard show what you use. A deploy of a new app name at the limit fails with app_limit_reached; redeploys of existing apps always work. Delete an app to make room, or upgrade.
API rate limits
Section titled “API rate limits”| Limit | Counted per | |
|---|---|---|
| Reads (status, logs, lists) | 300 per minute (Pro: 600) | user |
| Changes (deploys, env, deletes, …) | 60 per minute (Pro: 120) | user |
| Deploys | 30 per hour (Pro: 60) | team |
| Deploys building at the same time | 2 | team |
| Open live log streams | 6 | team |
| Failed sign-ins | 30 per 10 minutes | IP address |
Over a limit the API answers 429 with a Retry-After header and says which limit was hit. The CLI and the MCP server wait and retry reads by themselves. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset.
A live log stream ends after 30 minutes; flitzy logs -f reconnects.
App and database names are global: 1 to 32 lowercase letters, digits and dashes, starting with a letter and not ending with a dash. A name another account uses is taken. A few names are reserved: www, api, admin, deploy, registry, mail and some DNS names.