Limits & Credits
Deltex meters everything with one unit: the credit. There are no separate line items for reads, writes, and compute — every plan includes a monthly credit allowance, and paid plans bill only for usage beyond it.
How credits are counted
| Action | Cost |
|---|---|
| 1 query (any statement) | 1 credit |
| 1 write (INSERT / UPDATE / DELETE) | +1 credit |
| 10 rows read internally | 1 credit |
| 1 second of compute | 1 credit |
So a read query is about 1 credit and a write query is about 2 (the statement plus the write). A run of 1,000 simple SELECTs costs roughly 1,000 credits; 1,000 inserts roughly 2,000. Compute-heavy analytical scans add a credit per CPU-second.
Track your live credit usage in the console, or fetch it with GET /v1/usage. The pricing page has an interactive calculator.
Plan allowances
| Plan | Monthly credits | Storage | Rate limit | Overage |
|---|---|---|---|---|
| Free | 2,000,000 | 1 GB | 200 req/min | Hard cap |
| Pro | 5,000,000 | 10 GB | 1,000 req/min | $0.50 / 100K |
| Scale | 50,000,000 | 100 GB | 5,000 req/min | $0.30 / 100K |
| Enterprise | Custom | Custom | Custom | Volume |
When you hit a limit
- Free credit cap — the free tier is hard-capped. When you reach your monthly credits, requests return
429until the allowance resets at the start of the next month. You are never billed overage on free. - Paid overage — Pro and Scale keep serving past the included allowance and bill the overage at the rate above. There is no hard stop.
- Rate limit — exceeding your per-minute request rate returns
429with aRetry-Afterheader. This is independent of your credit balance.
Per-request limits
| Limit | Value |
|---|---|
| Request body size | 1 MB |
| CPU time per request | 50 ms (hard ceiling at the edge) |
| API key length | 128 characters |
The 50 ms ceiling is the edge runtime's per-request CPU budget; the Server-Timing header on every response reports the vcpu time consumed so you can see how close a query runs to it. For very large result sets, stream them with the /*+ STREAM */ hint instead of buffering a single response.