The Foundation Layer

The reason an API programme normally takes a year to assemble is not that any one part is hard. It is that each part holds its own copy of the truth — the gateway has routes, the portal has a catalogue, the auth server has scopes, the billing system has products — and somebody has to keep five copies agreeing as the API changes.

Apiway has one. You publish a contract, and everything downstream is derived from it. There is no reconciliation because there is nothing to reconcile.

What The Specification Becomes

Your OpenAPI document is not documentation that sits beside the running system. It is the input the running system is produced from:

From the specification	What it produces
Operations and paths	The routes the gateway serves
Operation identifiers	The scopes a consumer is granted and the gateway enforces, per operation
Request schemas	The contract validation applied to inbound requests
Declared security	Per-operation authentication and authorisation requirements
Responses and examples	The mock that goes live before any implementation exists
The document itself	The catalogue entry consumers discover and subscribe to

Change the contract and those change with it, because they were never separate things that had to be updated in step.

One Deployment Model, Many Runtimes

Apiway’s deployment model is abstract: it describes what should be true — this route, these scopes, this rate limit, this metering — rather than how any particular gateway expresses it. Workers translate that model into each runtime’s native configuration: routes and plugins for Kong, APIs and policies for Azure API Management, proxies for Apigee, and the policy pipeline for Alpha.

That is why the gateway you run is not an architectural commitment. The governance, the scopes, the metering and the audit trail are properties of the model, not of the runtime that happens to be serving traffic. See Multi-Gateway and Deployment Models.

Why This Reads As One System

The capabilities you would otherwise buy separately are here as one set of parts sharing a single source of truth: design and the contract, governance and approvals, identity and entitlement, the gateway, metering and cost, the catalogue and subscription, service levels, risk, and the compliance record.

The distinction that matters is not how many parts there are — it is that they are not integrated. Integration is what you do to products that were built separately and hold their own truth; it is the work that never finishes, because each new version of each part has to be re-reconciled with the others. Here the parts are derived from the same artefact, so agreement is not maintained. It is structural.

What You Still Own

Your services, and the contract you choose to publish. Apiway does not implement your API and does not decide what it should do — it takes the contract you commit to and makes everything else follow from it.