Docs

One DNS record, and that's the integration

There is no SDK to install and no middleware to wire. Traffic comes in through the edge node and flows on to your backend, with two headers added on the way.

1 · Point your domain at the edge

api.yourcompany.com.  CNAME  edge-eu-1.quota.at.

One record. Your certificate is issued and renewed at the edge; your origin keeps serving on whatever it serves on today.

2 · What your backend receives

HeaderMeaning
x-quota-limitRequests allowed in the current window for this client.
x-quota-remainingHow many are left. Counts down to zero, then the 429s start.
retry-afterSeconds until the window resets. Only on a 429.

Nothing you're forced to parse: they're there for clients that want to back off politely. The enforcement happens at the edge either way.

3 · What the caller gets back

200 Whatever your backend returned. Quota adds headers and gets out of the way.
429 Rate limit hit. Never reaches your origin; retry-after says when to come back.
502 Your backend did not answer. The edge is up; the origin is not.
503 Circuit open: your backend has been failing, so the edge stops hammering it for a while.

4 · The limits of each plan

PlanRequests / monthSustained req/sIndividual requests kept
Micro200K5~3 weeks
Starter2M25~6 days
Pro15M150~2 days
Enterprise50M+500+~2 days

The rate is the one you hit first. A plan with room to spare on the monthly figure can still throttle a spike: 5 req/s is 13 million a month if you could sustain it, and nobody can. Size on the rate, not on the total.

5 · When something is wrong

You choose what an outage of ours means for you: fail open, and traffic reaches your backend unfiltered, or fail closed, and it stops at the edge. Per node, from the panel. Alerts reach you by email the moment one fires, with what tripped it and what the edge did about it.

Integration questions

Do I have to touch my backend?

No. Quota is a proxy that stands in front: you point traffic at the edge node and it forwards to your API. No SDKs, no middleware, no code changes.

What does my backend see with Quota in front?

Legitimate requests arrive as always, with headers added (x-quota-limit, x-quota-remaining). The excess gets a 429 with retry-after at the edge and never touches your origin.

How are the limits defined?

From the panel: per endpoint, per client or per plan. Quota detects your endpoints automatically and you set the rules for each one.

What if my backend lives on a local network?

That's what Quoxy is for — our ngrok-style proxy: it opens a secure tunnel from your network to the edge, so you stay self-hosted without exposing your API to the internet. It ships alongside Quota and is included in the Pro plan.

Where do the nodes run?

In Europe today. North America and Asia-Pacific are on the roadmap. Every node is yours — you never share a queue with anyone.

That's the whole integration