Create account
Product

Everything the edge does for your API

One proxy in front, no code in your backend. What follows is the whole surface: what runs at the edge, what you get in the panel, and what's underneath.

Protection at the edge, control in your panel

What Quota does for your API, and where you control it from.

At the edge

Adaptive rate limiting

Per-plan and per-endpoint limits that adjust to how each client actually behaves. Good clients never notice; abusive ones never get through.

Spike & abuse protection

Circuit breakers, burst mitigation and connection control. Bad traffic dies at the gate, not at your origin.

A Rust engine

A high-performance proxy with its hot state in memory. Designed to never be your bottleneck.

In your panel

Real-time metrics

Requests, blocks and node health, live. You know what's happening while it's happening.

Reports that come to you

A monthly summary of your traffic in your inbox, and another one the moment an alert fires — with what tripped it and what the edge did about it. No dashboard to remember to open.

Regional deployment

We deploy in Europe today; North America and Asia-Pacific are on the roadmap. Every request resolves close by.

Zero friction

You bring the backend; Quota stands in front. No SDKs, no middleware, no rewriting your stack.

Pro plan on the way · ships with Quota

Backend on your local network? Quoxy

Not everyone wants a public API. Quoxy is our ngrok-style proxy: it opens a secure tunnel from your network to the Quota edge, and your backend stays right where it is — at home, at the office, in your rack.

  • Actual self-hosting — your API is never exposed to the internet.
  • No open ports — the tunnel dials out from inside, like ngrok.
  • The edge still rules — rate limiting and protection, identical.

Building it yourself vs plugging in Quota

Everything Quota does, you could build. The question is whether you want to maintain it.

  Yourself With Quota
Time to production Days: nginx, redis, lua, load testing Minutes: point your traffic at the edge
Per-endpoint & per-client limits Hand-written config and scripts, per service From the panel, nothing to deploy
Adaptive rate limiting An engineering project of its own Included — it learns from behaviour
Circuit breakers & spikes Yet another system to maintain Included in every node
Real-time metrics Exporters + Grafana + alerts Included in the panel
Maintenance Yours. Forever. Ours. You sleep.
Quota's databases

arkeion runs Quota. inro runs your node.

Both are ours, both are written in Rust, and there are two because the two jobs pull in opposite directions. No Postgres, no Redis anywhere in the picture.

  • arkeion holds Quota's own records — every configuration change versioned and audited, with its full history. Who raised the limit on /orders to 150, and when.
  • inro holds your node's traffic — requests and reports, in one file that is yours alone. 34 bytes a row, a whole node's analytics in under a megabyte.
  • Why not one engine for both — history costs space, and your traffic data is the part there's a lot of. inro gives up versioning to fit; arkeion keeps it where it's worth paying for.

Quota is where both get their first trial by fire in production. arkeion is also on its way as a managed database.

Ready to put it in front?

Deploy my first node See pricing