Why run an API gateway yourself?
You still get one, you just don’t run it. APIblaze is a gateway with nothing to deploy, patch or scale.
Put it in front of the API you already have. Keys, rate limits, sign-in, a developer portal and an MCP server come with it.
Put APIblaze in front of your API
$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yamlPaste it in a terminal. No sign-up, no servers. The link is a sample restaurant API; swap in your own.
The work that comes with running a gateway
Running your own gateway means looking after a second piece of software next to your API. These are the jobs it comes with, and who handles each one.
| Who does it? | Self-hosted gateway | APIblaze |
|---|---|---|
| Servers or containers to run the gateway | You | Handled |
| The database or config store behind it | You | Handled |
| TLS certificates for your domains | You | Handled |
| Scaling up for traffic spikes | You | Handled |
| Security patches and version upgrades | You | Handled |
| Choosing and configuring plugins for keys, limits and sign-in | You | Handled |
| Watching the gateway itself, and being on call for it | You | Handled |
| Your API itself | You | You |
Kong and Tyk also sell managed versions that take the servers off your hands.
Already switched on, no plugins to pick
Every new proxy starts with the basics on. The rest is a setting or one command away.
On from the start
Rate limits and quotas
10 requests a second per key and 3,000 a day on every new proxy. Change them any time.
How it worksA developer portal
Hosted for every proxy, with sign-in already set up.
An MCP server
Every proxy also gets an MCP address, under the same rules.
How it worksWhen you need it
Scoped, revocable API keys
Keys your customers mint, rotate and revoke themselves.
How it worksRoles and groups
Who can do what, set at the gateway, not in your code.
How it worksClaude and ChatGPT connectors
Sign-in that AI assistants understand.
How it worksAn endpoint per customer
Each customer gets its own address and its own keys.
How it worksWhen Kong or Tyk is the better pick
APIblaze is built for teams that want their API in front of customers without a gateway to run. It is not for everyone.
Pick Kong or Tyk when
- The gateway must run inside your own network or data centre
- You need a large plugin ecosystem, or plugins of your own
- You govern many teams’ APIs across a whole organisation
- You already run one and have the people for it
Pick APIblaze when
- You want your API in front of customers without running servers
- Your product is multi-tenant, and each customer needs its own keys, users and limits
- Developers and AI agents should use your API under the same rules
- You want to start small and keep the option to move
Use APIblaze today. Leave whenever you like.
One command exports everything you set up into a bundle you can run on Kong yourself. Your customers keep their API keys, and a report tells you anything that did not carry over exactly.
In APIblaze
- Routes, CORS and rate limits
- Request and response rewrites
- Authorization rules
- Users, groups and logins
- API keys
- MIGRATION-REPORT.jsonwhat carried over, and how well
- project-config.jsonroutes, CORS, rate limits
- openapi.jsonyour API spec
- transforms.jsonrequest and response rewrites
- authz/rules and relationship data
- tenants/<name>/
- auth/logins and JWT issuers
- users/end users and groups
- keys/API keys, as hashes
- auth/keycloak-realm.jsona login system to import
- kong/ready to run
- kong.yamlservices, routes, consumers
- plugins/keeps your keys working
- docker-compose.yml
- start.sh
Your customers keep their keys
Keys travel as one-way hashes, and a small plugin in the bundle checks them, so nobody has to change a key.
Free Kong, just Docker
The bundle runs on open-source Kong. No paid plan, and Docker is the only thing to install.
Nothing hidden
The migration report marks every item exact, approximate, lossy or skipped, with the reason.
Export your setup any time
$ npx apiblaze@latest export myapi --kongPrefer a clean break? Add --keys mint for fresh keys and a note to send your customers.
Common questions
Can I host APIblaze myself?
No. APIblaze is managed only; there is no self-hosted version. If you must run the gateway inside your own network, Kong or Tyk is the better fit.
Where does it run?
On Cloudflare’s global network. There are no regions, nodes or clusters for you to pick.
Does my API have to move?
No. It stays where it is, and APIblaze sits in front of it.
What about an API on my laptop?
npx apiblaze@latest dev tunnels it to APIblaze while you build, with the same rules as production.
How is it priced?
Per request, with no subscription and no servers to pay for. Prices are on the pricing page.
Does it match Kong feature for feature?
No, and it does not try to. The APIblaze vs Kong page lists what each one does.
Prices are on the pricing page.
An API gateway without running one
No sign-up, no servers. Keys, limits, sign-in, a portal and an MCP server in front of the API you already have.
$ npx apiblaze@latest create --target https://ninopizzas.com/openapi.yaml