Rate Limits & Quotas
Tellodb uses per-cluster rate limits to ensure fair resource allocation across tenants. Limits scale with your tier.
How Rate Limits Work
Every API request to the Tellodb platform is counted against a rate limit for the originating cluster. Limits are enforced in two dimensions: requests per minute (RPM) and requests per day. When a limit is exceeded, the API returns HTTP 429 with a Retry-After header.
Rate limits reset at the end of each window (1 minute for RPM, midnight UTC for daily). 429 responses include X-RateLimit-Remaining and X-RateLimit-Reset headers so your application can adapt.
Free Tier RPM
60
1 request per second average
Free Tier Daily
10,000
Resets at midnight UTC
Pro Tier RPM
300
5 requests per second average
Pro Tier Daily
100,000
10x free tier capacity
Enterprise
Unlimited
Custom SLA, no rate limits
Response Headers
| Metric | Header | Description |
|---|---|---|
| X-RateLimit-Limit | The maximum requests per minute for this cluster | |
| X-RateLimit-Remaining | How many requests are left in the current window | |
| X-RateLimit-Reset | Unix timestamp when the window resets | |
| Retry-After | Seconds to wait before retrying (on 429 only) |
Best Practices
- Implement exponential backoff: on 429, wait Retry-After seconds, then double the wait on subsequent failures.
- Use the X-RateLimit-Remaining header to pre-warn when approaching limits. Slow down requests when remaining < 10% of limit.
- Batch ingest operations rather than sending one-at-a-time. Each batch-ingest call counts as 1 request regardless of size.
- Monitor your usage in Mission Control → Analytics. The usage dashboard shows daily trends and remaining quota.
- Upgrade to Pro for 5x higher limits. Contact Enterprise sales if you need more.