Edge proxy · rate limiting · protection

You decide
who gets through and who waits

Quota stands in front of your API and enforces the rules at the edge: legitimate clients flow, abuse gets stopped and spikes get absorbed. Your backend never even notices.

Deploy my first node See what it does

rocky@edge-eu-1 — quota.at

$ curl -i https://api.yourcompany.com/orders

HTTP/2 200

x-quota-limit: 100

x-quota-remaining: 97

$ for i in $(seq 1 200); do curl -s -o /dev/null … ; done

HTTP/2 200 ×99

HTTP/2 429 too many requests

retry-after: 12

── your backend never noticed ──

▊

< 2 ms

added latency (p99) · 0.5 ms median

Rust

in the hot path, in-memory state

lines of code in your backend

live region · NA & APAC on the way

Blue gets through. Orange waits.

Live in three steps

Connect your backend

Tell us where your API lives. We deploy your edge node in Europe — more regions on the way — in minutes.

Set the rules

We detect your endpoints and you decide the limits: per plan, per client, per route.

Sleep well

The edge absorbs the spikes, stops the abuse and tells you all about it in the panel.

It all starts at your DNS

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

One record. Traffic comes in through the edge and flows on to your backend.

What your backend receives

x-quota-limit: 100
x-quota-remaining: 97
— and the excess: a 429 with retry-after
   that never reaches your origin

Standard headers on every legitimate request. Nothing you're forced to parse.

The next traffic spike
is no longer your problem

Deploy my node See plans

From €9/month · Node deployed in minutes