Annual plans · one yearly payment
Create gateways and endpoints, issue and revoke API keys, inspect every request, and track a full twelve months of usage against a single annual subscription — with admin tools for users, plans and transactions.
Twelve monthly allocation rows, one annual invoice. No hidden renewals, no surprise overage bills.
Exposing an API, securing it, watching it, billing for it — every stage has a module in the console, and they share the same data model.
Create gateways with a base URL, attach endpoints per method, and enable or disable traffic instantly.
Issue scoped API keys, show the secret once, then keep a masked record with revocation history.
Every call recorded with method, endpoint, status code and response time for fast debugging.
Twelve months of request volume and success rate, charted so trends are obvious.
One annual payment, twelve monthly allocation records, and downloadable invoices.
Platform-wide view of users, subscriptions, plans and transactions with role-based access.
Admin and user roles enforced at the database with row-level security.
Every gateway, key and log row is readable only by its owner or an admin.
Server-rendered routes with cached queries keep navigation instant.
Requests, success rate and plan consumption in one view.
Group endpoints under gateways so the surface stays understandable.
Recent calls surface on the dashboard the moment they are logged.
Sign up with email and password or continue with Google, then pick your annual plan.
Name it, set the base URL, then attach the endpoints you expose.
Generate an API key, copy the secret once, and start routing traffic.
Watch usage build up and settle the plan with a single annual payment.
Four steps, no infrastructure setup. Gateways, keys, quotas and logs are wired together from the moment your plan is active.
Register your upstream service once and hand partners a key instead of raw credentials.
Consolidate request logs and monthly volume so capacity conversations use real numbers.
Give each engagement its own gateway and keys, with usage tracked independently.
Quotas stop runaway scripts before they reach the service behind the gateway.
Point any client at your gateway path and pass the key you generated in the console. Requests are validated against the gateway, checked against your plan quota, logged and counted before they reach your upstream service.
Call a gateway endpoint
curl https://yourapi.dev/api/public/gw/my-gateway/users \
-H "x-api-key: $YOURAPI_KEY"From JavaScript
const res = await fetch(
"https://yourapi.dev/api/public/gw/my-gateway/users",
{ headers: { "x-api-key": process.env.YOURAPI_KEY } },
);
const data = await res.json();12
Months of history per plan
1M
Requests / month on Enterprise
<1s
Log write after each call
2h
Premium support first response
Secrets are hashed on the server; the plaintext value never returns after creation.
Postgres policies restrict every table to the owning account or an admin.
Admin rights are resolved server-side, never from client state.
Plan limits are checked in the database and at the proxy, not in the UI.
Unregistered paths are rejected with a 404 before any upstream call.
Plan changes, renewals and invoices are written to a transaction ledger.
Access rules live in the database, not only in the UI. Keys are stored as hashes, roles are held in a dedicated table, and every gateway, log and invoice row is scoped to its owner.
Every plan is billed once per year. Monthly rows inside the console track usage allocation only — there is no second invoice.
$399.00
Billed annually, one payment
$791.50
Billed annually, one payment
$1,967.44
Billed annually, one payment
| Feature | Starter | Professional | Enterprise |
|---|---|---|---|
| API Gateways | 3 | 10 | Unlimited |
| API Keys | 5 | 25 | Unlimited |
| Requests / month | 50,000 | 250,000 | 1,000,000 |
| Request logs | Standard | Extended | Full |
| Usage analytics | — | Included | Advanced |
| Priority processing | — | — | Included |
| Support | Basic | Priority | Premium |
“We replaced a spreadsheet of partner keys with one console. Revoking access is now a single click instead of a deploy.”
“The monthly usage chart settles capacity arguments in a minute. Everyone looks at the same numbers now.”
“One annual payment with a twelve-month allocation view is exactly how our finance team wanted it.”
Gateways can reject any path that is not registered.
Ticket priority and response targets follow the active plan.
Renewals generate invoices and extend the annual term.
Push quota and failure events to your own endpoints.
Invite teammates into one workspace with scoped roles.
Each subscription is a single annual payment. The twelve monthly rows in the console are allocation records for tracking usage — they are not separate charges.
Yes. Upgrades are pro-rated against the time left on your term, and downgrades are checked against your current gateways, keys and usage before they apply.
The full secret is shown once at creation. After that only a hash and a masked prefix are kept, so a lost key must be revoked and reissued.
Requests beyond the quota are rejected at the gateway with a clear error, and the usage screen shows how much of the allowance is consumed.
Turn on allow-list mode for a gateway and only the endpoints you registered will be routed; everything else returns a 404.
Create an account with email and password, or continue with Google. Password reset is available from the sign-in screen.