Fizzlayer Gateway

The secure connection layer for AI agents.

Fizzlayer Gateway is one MCP endpoint in front of the servers your agents can call. You allow a tool, deny it, or hold it for approval. If the tool's description changes, the call stops until you pin the new text.

You can run this from the repository today. Docker is the only extra install. fizzlayer.com does not host a shared gateway yet. Join that list if you want a hosted URL. Create an account opens gateway setup. Sensors stay at /sensors. Apache-2.0, Fizzlayer LLC. The data plane is unmodified agentgateway v1.7.

An agent calls Fizzlayer Gateway. The gateway checks the policy, the tool pin, and any approval, then forwards the call.
MCPStreamable HTTP
Agent Claude Code, Cursor, or any client that can send a bearer token
Fizzlayer Gateway fizz-guard on agentgateway
  • Allow
  • Deny
  • Approve
  • Pin
MCP servers HTTP or SSE. stdio only on a dedicated or self-hosted gateway.

A phone, webhook, or log line can tell you an approval is waiting. The agent retries the same call after you approve it once.

What you can use

The proxy runs on your machine. The hosted one does not.

Creating an account opens gateway setup. Sensors stay at /sensors. fizzlayer.com does not host a shared gateway yet.

How a call moves

The risky call waits. The agent tries again.

  1. 1

    The client presents a Fizzlayer JWT

    ES256, issuer fizzlayer, audience set to that gateway's URL. The public key is at /api/gateway/jwks.

  2. 2

    fizz-guard reads the rule

    Each tool is allow, deny, or approve. No matching rule denies the call. A tool you have not pinned is hidden from the list by default, and a call to it is denied.

  3. 3

    Approval is one retry

    The gateway rejects the call, stores the argument hash, and returns. You approve that row. The same call is allowed once, then a second retry is rejected.

In the data plane

Rules, pins, and tokens.

These are the pieces in gateway/. Longer notes are in the docs.

Per-tool policy

Allow, deny, or approve. A rule can name one server or every server, and one tool or *. Notifications are a log line, a webhook, or a phone call.

Tool pinning

The pin is a hash of the tool name, description, and input schema. A changed description drops the tool from tools/list and blocks tools/call until you approve the new hash.

Single-use approval

The rejection names an id and tells the agent to retry the same call. The default window is 10 minutes. Approving it does not approve the next different argument list.

Client JWTs

Mint a token for "Cursor on this laptop", revoke it later. fizz-guard reads revoked_at. The default life is 1 hour. You can ask for up to 30 days.

Encrypted upstream keys

An MCP API key is stored as AES-256-GCM ciphertext. List responses do not include it. The signed-in config preview leaves credentials out.

Hot reload from a file

Standalone mode writes agentgateway YAML and replaces the file in one rename, which the proxy watches. Linked mode runs fizz-agent, which polls the control plane and writes that same file. Do not run both writers on one file.

Quickstart

Docker from the repo, or a place on the hosted list.

Self-host

Docker Engine with Compose. The script builds the local image, checks the database policies, and runs an MCP client through the gateway. It removes the containers when it finishes. Passwords stay in gateway/compose/.env and are not printed.

git clone --depth 1 https://github.com/fizzlayer/fizzlayer.git
cd fizzlayer
gateway/compose/test.sh

To leave the sample gateway listening on 127.0.0.1:3000, use the compose command in the docs. Linked mode is gateway/compose/test-linked.sh, or fizz-agent pull against your own control plane. Docker Hub does not have a fizzlayer/fizzlayer-gateway tag yet, so Compose builds the image.

Hosted

There is no shared URL to paste into a client. A Pro plan is priced to include one dedicated gateway, and the API will store that mode, but no machine is provisioned.

Join the hosted list

An account at /app.html is the Sensors workspace. It does not open a gateway dashboard. If you already have an account, the control-plane routes are under /api/gateway once that database migration is applied. A row in that API is not a running proxy.

Pricing

Same four prices. Sensors now, gateway limits in the API.

Full comparison. Phone calls are the column that is dialed today. Gateway and server counts are enforced when you call the control plane. Monthly tool-call totals are stored and not metered yet.

Fizzlayer plans: price, sensors, gateway counts, and the shared phone-call cap
Plan Price Sensors Gateway Phone calls
Hobbyist $0 3 devices, 10 Fizz credits 1 shared, 3 servers None. Dashboard and webhook alerts.
Pro $25 / month 50 devices, 1,000 credits 1 dedicated, 25 servers, stdio allowed in the API 100 / month
Enterprise Custom Custom Custom Unlimited unless a contract sets a cap

Alert calls and approval calls share one cap. It resets on the first of the month (UTC). Email alerts are on every plan, including Hobbyist, and the dashboard shows that choice only when mail is configured. On fizzlayer.com that choice is hidden. Hobbyist gets dashboard and webhook alerts. The hosted shared gateway and the Pro machine are not running. How the plans differ for the gateway.

Sensors

Sensors stay on this account, at /sensors.

Pair a Linux device, a phone, or Home Assistant. Ask Fizz about the readings. Set an alert. Phone-call alerts use the same monthly cap as gateway approvals.

Open Sensors

  • Hosted at fizzlayer.com/sensors, and self-hosted with the sensors images.
  • MCP for sensor data is a separate server at /api/mcp, with fizz_agent_ tokens.
  • The gateway does not replace that server. You can add it later as one upstream.

Hosted gateway

Join the list.

This is the same contact form as Enterprise. It stores an email. It does not create a gateway, mint a token, or reserve a plan.