Docs / Limits & Credits

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

ActionCost
1 query (any statement)1 credit
1 write (INSERT / UPDATE / DELETE)+1 credit
10 rows read internally1 credit
1 second of compute1 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

PlanMonthly creditsStorageRate limitOverage
Free2,000,0001 GB200 req/minHard cap
Pro5,000,00010 GB1,000 req/min$0.50 / 100K
Scale50,000,000100 GB5,000 req/min$0.30 / 100K
EnterpriseCustomCustomCustomVolume

When you hit a limit

Per-request limits

LimitValue
Request body size1 MB
CPU time per request50 ms (hard ceiling at the edge)
API key length128 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.