Limits

Tier limits

Every tier, including Free, has full read + write MCP access (browse, export, generate code, create, update, delete, upload). Free is bounded by volume — the 100 requests/hour rate limit and the Free quotas — not by access. Actions and webhooks require Pro or Enterprise (Free allows 0 of each).

Rate limits (per token)

The window is a rolling hour. 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 data payload max: 1 MB.
• Schema field count max: 200 fields per schema.

What happens at the limit

• Record limit hit: writes are blocked with a tier-limit message. Reads keep working. Existing records are unaffected.
• Storage limit hit: file uploads are blocked with a tier-limit message. Existing files remain available.
• Rate limit hit: 429 with Retry-After. No data loss; just throttling.

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: UUID (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.

What you may store

Limits govern how much you can store. What you may store is a separate question: Jaina is not a place for personal data about other people (end users, customers, employees). If you are deciding whether your use case fits, read Personal Data & DPAs — it explains the policy and why, as a result, you do not need a Data Processing Agreement to use Jaina.

Upgrade

Hit a tier limit and want more headroom? Upgrade in settings.