Limits
Plan quotas and read rate limits
Grepticon enforces two kinds of limit: quotas on how much you can store, and rate limits on how fast you can read. Quotas are checked when you create a workspace or upload a file, never on the read path, so reads stay fast and predictable. Rate limits guard the read path.
Plan quotas
| Limit | Free | Pro |
|---|---|---|
| Workspaces per account | 3 | 100 |
| Account storage | 500 MiB | 5 GiB |
| Max file size | 50 MiB | 50 MiB |
| Files per workspace | 10,000 | 100,000 |
Exceeding a quota fails the write with a clear message, never a silent drop. The free plan needs no card and is enough to build and evaluate against the hosted stack.
Read rate limits
Reads are rate-limited on two windows at once, per credential and per account:
| Window | Free | Pro |
|---|---|---|
| Reads per credential | 60 / minute | 600 / minute |
| Reads per account | 300 / minute | 3,000 / minute |
The per-credential window keeps a single runaway agent from starving the rest; the per-account window is the aggregate ceiling across every credential you hold.
When you cross a window, the request returns 429 Too Many Requests with a
Retry-After header naming how long to wait. The SDK handles this for you:
it retries a 429 up to twice, honoring Retry-After before surfacing the
error. Bursty agent traffic mostly rides through without your code doing
anything.
Only the four read tools ls / find / cat / grep count against these
windows. Management operations like creating workspaces, uploading files, and
minting tokens are not on the read path.
Upgrading
Higher quotas and rate limits come with the Pro plan. Manage your plan and billing in the console under Billing. Upgrading lifts the caps on your existing account without any migration.
Where to go next
- Quickstart: everything below runs comfortably on the free plan.
- Support: need a limit raised beyond Pro, or hit something unexpected? Get in touch.