API
Limits
Plan limits, rate limits, and why reads are unlimited.
Reads are unlimited
No plan counts or caps reads. What limits reads is per visitor, not per plan:
| Kind of read | Answered by | Limit |
|---|---|---|
Public bin (?env=, ?v=N, ?query=) | Cloudflare's cache, almost always | None from hotcfg |
| Public bin with testing parameters, or a cache miss | hotcfg's servers | 600 a minute per IP address |
| Private bin (with a key) | hotcfg's servers, every time | 600 a minute per IP address |
Per plan
Per organization. Usage against them is shown under Settings → Plan & billing and by hotcfg usage.
| Limit | Free | Pro |
|---|---|---|
| Bins | 3 | 250 |
| Seats (members and pending invites) | 2 | Unlimited |
| Payload size (compacted JSON) | 256 KiB | 2 MiB |
| Versions kept per environment | 10 | 100 |
| Storage (all kept versions) | 25 MiB | 500 MiB |
| Bins created in any 24 hours | 100 | 1,000 |
| Invites sent in any 24 hours | 20 | 100 |
| Private bins | Yes | |
| Keys limited to bins, environments or a lifetime | Yes | |
| Audit log | 90 days |
Older versions beyond the kept count are deleted when you publish.
For everyone
| Limit | Value |
|---|---|
| Writes | 60 a minute per key or user, at most 20 in one burst; 120 a minute per organization, at most 40 in one burst |
| Sign-in | 10 a minute per IP address |
| jq filter | 512 bytes, 50 ms, 2 MiB result; 30 new evaluations a minute per IP address without a secret key (repeated filters on public bins come from the cache and don't count) |
?delay= | 10 s; at most 4 delayed reads at once per IP address |
| JSON Schema | 64 KiB; 3 million subschema checks per validation |
| Bin id | 1–64 characters of a–z, 0–9, - and _, unique within the organization |
Last updated 10 November 2026