Pricing

One subscription.
Everything included.

Design, gateway, credentials, access control, developer portal, metering and governance — one price, instead of four or five products and the people to keep them working together.

Start on the free tier with no credit card. Move up when your traffic does.

The Subscription Ledger

Architectural Tiers.

Every capability is available on every tier. Tiers differ by how much usage they carry — nothing is held back for a higher plan, and nothing has to be upgraded to before it works.

That includes the free one. Start Free is the same platform, with the same governance, the same security and the same gateway — not a sandbox, and not a trial that expires. What you build on it stays where it is when you start paying for more of it.

Credits pay for everything the platform does — design, publishing, compliance, risk, impact analysis, and serving your traffic. Traffic is the cheap part: a call through the gateway costs a fraction of a unit, and there is no separate charge per environment, so your credits go on the work rather than the requests. Rate limits bound throughput per subscription — reads and writes capped separately, because writes are the costly verbs.

Level 00

Start Free

€0 · NO CARD REQUIRED

200,000

CREDITS TO START

CONTROL PLANE

  • ✓ Any email — personal or company, both fine
  • ✓ 100 reads · 10 writes / min
  • ✓ 200,000 credits on a company address, 100,000 on a personal one — once, to build and prove it. They never expire: move up and they stay yours as a reserve, on top of every monthly allowance.
  • ✓ Pay as you go — not ready for a plan? Top up credits when you need them, with no subscription.
  • ✓ Every capability included — see below
Start building free →
Level 01

Foundation

€12,000 / ANNUAL

A team putting its first governed APIs into production.

100,000

CREDITS EVERY MONTH

1.2 million a year · about 1 cent a credit

CONTROL PLANE

  • ✓ 500 reads · 50 writes / min

Every capability included — see below.

Level 02

Business

€24,000 / ANNUAL

A department’s estate, with several teams producing.

200,000

CREDITS EVERY MONTH

2.4 million a year · about 1 cent a credit

CONTROL PLANE

  • ✓ 2,000 reads · 200 writes / min

Every capability included — see below.

Level 03

Professional

€48,000 / ANNUAL

An organisation-wide programme, many teams and consumers.

400,000

CREDITS EVERY MONTH

4.8 million a year · about 1 cent a credit

CONTROL PLANE

  • ✓ 5,000 reads · 500 writes / min

Every capability included — see below.

Level 04

Enterprise

TALK TO US

1,000,000

CREDITS / MONTH

CONTROL PLANE

  • ✓ 20,000 reads · 2,000 writes / min
  • ✓ Fair-use overflow
Talk to us →

Included on every tier.

Including Start Free

✔Design studio — intent to a governed contract
✔Automated breaking-change detection
✔Impact reporting before you change an API
✔Approval flows and four-eyes governance
✔Identity and access enforcement at the edge
✔Payload protection on request and response
✔Service levels as a specification — OpenSLA
✔Real-time risk classification
✔Marketplace and self-service consumer onboarding
✔Metering and cost attribution per consumer
✔MCP endpoint with an AI identity
✔Any identity provider — OIDC and OAuth2
✔Kong, Azure APIM, Apigee, Tyk, Zuplo or the Apiway gateway
✔PaaS, hybrid or self-hosted deployment
✔Portable contracts, history and subscriptions

Like for like

Delivering a product yourself means all of this.

A gateway, even one that can charge for calls, is the runtime line of this list. Taking a product to market takes every line. Elsewhere each line is a capability — bought separately, then integrated, then kept working with the others every time something changes. Here each line is already done.

Traffic in and out
A runtime to buy, set up and keep running
Done — traffic routed and limited
Credentials for each customer, scoped to what they bought
An authorisation server to buy or build, and wire into every route
Done — each customer holds their own at sign-up
Sign-in for your own people
An identity provider, connected to all of the above
Done — your people sign in with the one you have
Customers find your APIs and sign themselves up
A portal to buy, configure and keep in step with every change
Done — live when you register
Contracts designed and kept to standard
A design tool, rules to write, and someone to enforce them
Done — standards applied as you design
Something to call before the backend exists
A mocking tool, scripted per resource, thrown away at launch
Done — stateful, per partner
What each customer used, into your invoices
A metering service, and the code that joins it to billing
Done — every customer's line items ready by API, for whatever invoices them
Never breaking a paying customer
Whatever you deploy goes live — a gateway ships breaking changes too
Done — breaking changes are refused onto live versions
Service levels you can sell and enforce
Rate limits, and a monitoring tool to guess the rest
Done — limits and quotas enforced on every request, risks raised as they happen
Evidence for GDPR, NIS2 and DORA
Logs to export, and people to turn them into evidence
Done — produced as you run
Abnormal use spotted and its reach known
Rules in a SIEM, written and tuned by hand
Done — raised as it happens, with which customers it reaches
Making them work together
Your engineers — to integrate them, and then to keep them agreeing with each other for as long as the product lives
Nothing to integrate — one subscription

Continue

Work Out Your Return

Put in your own traffic, prices and running costs, and see what is left.

Read more →

Credits and Resource Usage

What draws on your balance, and what does not.

Read more →

Get Started

What the first hour looks like, from a specification to something a consumer can call.

Read more →