Limits and quota

A unit is consumed only after a valid submission is accepted and durably stored. Validation failures, blocked requests, rate-limited requests, spam, webhook attempts, and idempotent replays do not consume production allowance.

Plan	Production / month	Sandbox / month	Maximum payload
Free	50	200	256 KB
Starter	Pricing pending benchmarks	2× production	256 KB
Growth	Pricing pending benchmarks	2× production	512 KB
Agency	Pricing pending benchmarks	2× production	1 MB
Enterprise	Negotiated	Negotiated	Negotiated

When allowance is exhausted, submission acceptance stops. Usage warnings begin at 70%, then repeat at 75%, 80%, 85%, 90%, 95%, and 100%. Optional production top-ups expire with the current monthly usage period and do not roll over. Sandbox top-ups are not sold.

Every submission is also bounded to 100 fields, 128 characters per field name, 64 KB per individual text value, and 20 nested object/array levels.

Independent one-minute abuse limits apply to the submitter network key, form, project, and account. The API returns 429 with an RFC 9457 problem body when a limit is reached. These controls protect ingestion capacity and do not consume quota. Exact thresholds are operational safeguards and may be tuned without changing plan allowances.

#Limits and quota

Limits and quota