Limits
Tier limits and rate limits.
Tier limits
| Resource | Free | Pro | Enterprise |
|---|---|---|---|
| Projects | 1 | 5 | Unlimited |
| Records per schema | 100 | 10,000 | Unlimited |
| Storage | 100 MB | 10 GB | 200 GB |
| File size (per file) | 10 MB | 100 MB | 500 MB |
| MCP access | ❌ | ✅ | ✅ |
| Webhooks per project | 3 | 20 | Unlimited |
| API tokens | 3 | 20 | Unlimited |
Rate limits (per token)
| Tier | Requests / minute |
|---|---|
| Free | 60 |
| Pro | 600 |
| Enterprise | 6,000 |
Window is rolling. Burst traffic is allowed up to the limit. Sustained traffic above the limit returns 429 Too Many Requests with a Retry-After header.
Payload limits
- Request body max: 10 MB (50 MB for file uploads).
- Record
datapayload max: 1 MB. - Schema field count max: 200 fields per schema.
What happens at the limit
- Record limit hit: writes return
402 Payment Requiredwith a message indicating the tier limit. Reads keep working. Existing records are unaffected. - Storage limit hit: file uploads return
402. Existing files remain available. - Rate limit hit:
429withRetry-After. No data loss; just throttling. - API token limit: create returns
400until you revoke an existing token.
Hard limits (apply on all tiers)
- Project slug length: 1–63 characters.
- Schema slug length: 1–63 characters.
- Field slug length: 1–63 characters.
- Record
id: 26-character ULID (system-generated; you cannot set it). - Pagination max: 100 items per page.
- Action payload max: 64 KB.
- Webhook delivery retry: 5 attempts over ~15 minutes.
Upgrade
Hit a tier limit and want more headroom? Upgrade in settings.
