Limits & quotas
Cloudrizz has three kinds of limits: per-plan quotas that scale with your subscription, universal hard caps that protect the platform, and rate limits that contain bursts and abuse.
Per-plan quotas (free tier)
The free tier is shown below. On paid plans each app gets a larger free allowance (e.g. 1M requests / month), and usage above it is metered rather than blocked — so paid apps stay online. Every plan includes one app; add more for a flat $5 each. Your plan mainly sets the org-level limits (storage pool, managed AI credits, custom domains, seats). See pricing for the full comparison.
| Limit | Free |
|---|---|
| Apps | 1 |
| Deploys / month | 20 |
| Requests / month (per app) | 100,000 |
| Storage | 250 MB |
| Emails / month (per app) | 100 |
| Scheduled jobs (per app) | 1 (daily only) |
| Managed AI credits | None — bring your own key |
| Commits / branch | 25 |
Hard caps (all plans)
These are fixed regardless of plan:
| Cap | Value |
|---|---|
| Max file size (per file in a commit) | 100 MB |
| Max commit size (total) | 500 MB |
| Max files per commit | 2,000 |
| Resources per app | 1 each: database, storage, cache, AI, email |
Files larger than 20 MB are served from storage rather than the asset bundle.
Rate limits
Short-window limits keep bursts and abuse in check. They're rarely hit in normal use:
| Surface | Limit |
|---|---|
| Sign-in / auth | 5 / minute |
| MCP (before auth) | 60 / minute |
| MCP (per organization) | 300 / minute |
| Email send (per app) | 100 / minute, 1,000 / day |
On the free tier, if an app exceeds its rolling request quota its .cloudrizz.app subdomain is paused until usage falls back under the cap. On paid plans the app stays online and the overage is metered.