Hi HN. There are lots of API gateways out there. What we couldn't find was one with everything built-in to go from “my business logic works” to “I can safely consider publishing it on the internet”. So we spent a year building the features in APIblaze: A serverless MCP and API gateway. Here’s what makes it different:

- Authorization. Most gateways stop at authentication: they check who is calling. What they can and cannot do is left to your code or a plugin connecting to some sort of complex Authorization system. APIblaze provides users & groups management and enforces Authorization policies at the gateway, as a default suggested from your API spec. You add groups and write Authorization rules in plain English ("only whoever created a record, or an admin, can read or change that record"), tested and enforced by the gateway.

- Hosted end to end. APIblaze hosts the MCP server, the gateway, OAuth discovery and the login pages on the internet. One thing we really wanted to make easy was local development so the hosted API gateway forwards the requests to your backend, even if this backend runs on your localhost. So you can connect Claude/ChatGPT/… to the hosted MCP, bring your own oAuth and log into it (which is important because MCPs are all about taking actions and you have to know “who” is taking those actions), chat with your API to test it, and change your code live while the calls stream in your terminal.

- UI widgets: self-service API keys, users and groups and chat window. A drop-in React widget lets your users create, rotate and revoke their own keys on the developer section of your site. Another lets your customers' admins manage their own users and groups. A last one lets end users chat with your API on your App.

- Multi-tenant. Each customer gets its own keys, users, portal and MCP address to serve their own service to their end-users.

- The usual gateway tools: rate limits and quotas, transformations, custom domains and more.

- No lock-in: one command exports your setup (config, users, groups, and API keys as hashes so your callers keep theirs) to a runnable Kong bundle once you outgrow APIblaze.

To try it, paste this prompt into Claude Code or Codex, in an empty folder (you get a sample app) or in your backend's folder:

> Show me what APIblaze does using npx apiblaze skills

Or by hand, no sign-up needed:

  npx apiblaze create --target https://ninopizzas.com/openapi.yaml

It's in beta. I'd love your feedback, what you like and what you don't.

Show HN: RcloneView 1.6 – A desktop GUI for rclone with 40 cloud storages