On this page
Alternative to Docker MCP Gateway

The Docker MCP Gateway alternative
for agents that touch real systems.

Verosek is an AI and MCP gateway: keep your SDK, route model calls with fallback, set budgets and rate limits per key, connect your tools, and have each tool call decided by the key's rules before it runs. Moving from Docker takes two values, endpoint and key.

The gateway

A full gateway on one key

What you expect from a gateway: routing, budgets, connectors and traces.

Route with fallback.

Verosek routes to OpenAI, Anthropic, Google, Azure, Bedrock, Ollama and any OpenAI-compatible server. Calls fall back in priority order.

Budgets and limits on the key.

Each key carries its allowed models, budget, rate limits, expiry and per-tool rules.

Connect your tools.

Connectors for databases, code hosts, ticketing, chat, payments and cloud, behind one MCP endpoint.

Run agents on it too.

Versioned agents, with their own key and limits.

Scanning comes with it.

Shield's checks ship in the gateway, with no second vendor to buy.

Why Verosek

Why Verosek over Docker MCP Gateway?

Verosek is for platform teams whose own agents write to production systems. Docker's open-source gateway runs and proxies MCP servers in containers. Organization-wide control comes with its AI Governance plan, through sales, and its MCP Enterprise Gateway is sold the same way. Verosek puts model calls and tool calls on one key.

It reads the statement, on a plan with a published price.

Verosek reads the SQL statement itself, where Docker's allow lists go by profile, and Cedar rules on values come with AI Governance, through sales. Verosek parses seven SQL dialects, so you can give an agent a production system and say exactly what it may do to it.

One key and one record for model and tool calls.

Verosek seals one record for each request, model calls and tool calls together, with the reason for each decision, where Docker's open-source call logs hold the tool name and argument shape, and AI Governance records leave argument values out, by design. Give a regulator your public keys, and they can check each decision themselves.

Refuses by default. You choose the exceptions.

A blocking rule that cannot run refuses, and so does a request the record cannot hold. You can set one rule on a key to let calls through when the check itself breaks. Under Docker's AI Governance, a failed evaluation fails closed, and with no enforced policy, Cedar does not run and everything is allowed.

The proof

Attacks become findings, and findings become rules on the key.

Assay, an open MCP security benchmark we maintain, was presented at Black Hat India Arsenal. Our red-team framework holds 205 attack techniques, 68 for MCP, with findings anyone can recompute.

Does my proxy already do this?

Part of it, perhaps. Allow lists per key and deny by default are common. On one key, Verosek also routes your model calls, sets budgets, scans with no second vendor, reads the SQL statement down to its tables and row bounds, and seals the reason for each decision. Docker's gateway runs each server in a restricted container. Verosek puts your model calls on the same key as your tool calls.

Start on the gateway you will keep.

There is no reason to stand up one gateway now and move your keys, budgets and rules later. The record of calls made before Verosek was in the path cannot be written afterwards, and a call that already ran cannot be taken back. Watch mode shows what a rule would have blocked before it enforces, so nothing stops until you say.

Side by side

At a glance

Docker's name covers three products, and each row below says which one it means.

At a glance: Verosek and Docker MCP Gateway
The pointVerosekDocker MCP Gateway
Model calls and budgetsRoutes model calls, with fallback, and sets a budget and rate limits on each keyOpen source: Running and proxying MCP servers in containers.
Tools and connectorsA catalogue of connectors, with OAuth where the server needs itOpen source: A proxy between clients and servers.Enterprise Gateway: Private catalogs from your own registries.
Tool rulesPer key and per tool, before each call runs: a SQL statement's operation, tables and row bounds, a payment's amount, a file path, a namespace, a recipientOpen source: Allow lists by profile, a secrets scan and interceptors you write.AI Governance: Cedar rules that read values.Enterprise Gateway: Rules by server, tool, transport and call.
ScanningPrompt injection, personal data and secrets in prompts, replies, tool arguments and tool results, on both plans, with no second vendor to buyOpen source: A scan for secret-like values, on by default, and interceptors you write.
The recordOne sealed record for each request, with the reason for each decisionOpen source: Tool names and argument shape.AI Governance: Metadata records, without parameter values.Enterprise Gateway: An event per evaluation, sent to your SIEM.
Human approval on a tool callA named person decides the calls you chooseAI Governance: A confirmation from the person in the session.
On a published planTeam at a published $999 a month, with every Shield profile, sealed records and SSOAI Governance: By licence, through sales.Enterprise Gateway: Through sales, with no price on the page.
Where it runsEnterprise: private cloud, VPC or air-gapped, deployed with usOpen source: Any Docker Engine, under MIT.Enterprise Gateway: Your own account, or air-gapped.

As of 5 Nov 2026.

What moving takes

Is Verosek a drop-in replacement for Docker MCP Gateway?

An MCP client.

Your MCP client changes two values: the endpoint, which points at your gateway, and the key, which becomes a Verosek key.

Your servers.

Your tools connect to Verosek, and we set that up with you.

Profiles.

Docker allows tools per profile. Those lists become per-tool rules on each key.

Model calls.

Your model calls can move onto the same key by changing the SDK's base URL and API key.

A developer's laptop.

The open-source gateway is the CLI plugin behind the MCP Toolkit in Docker Desktop. Verosek runs as one gateway for the team, so each developer's client points at the same endpoint under its own key.

The secrets scan.

Docker's open-source gateway scans arguments and text responses for secret-like values. Shield's checks read for those, and for prompt injection and personal data.

Private catalogs.

Docker's MCP Enterprise Gateway publishes private catalogs from your own registries. Verosek's catalogue of connectors takes the servers you run, with OAuth where the server needs it.

Cedar policies.

Docker's Cedar policies are scoped to an organization or team. Policies you wrote become rules on each key, and we set that up with you.

When Docker MCP Gateway is enough

If you manage MCP servers on a workstation, Docker's open-source gateway is built into its MCP Toolkit.

Frequently Asked Questions

Three things: one key for model and tool calls, rules that read values on a plan with a published price, and a record that keeps the reason for each decision. Verosek answers all three on the Team plan, at a published $999 a month. It can also hold the calls you choose for a named person.

Verosek decides what each tool call may do, and it records the decision. A tool Verosek runs is held back if its definition changes. With Shield on, tool results are checked for hidden instructions. A rule limits what a server is asked to do. Run the MCP servers Verosek launches under your own isolation, as you would any third-party code.

Verosek is closed source. The gateway and its admin console hold no licence check, telemetry, analytics or call to a Verosek host.

Team is $999 a month, billed yearly. Enterprise has custom terms. Both plans start with a call. See the plans. Organization-wide control in Docker's gateway comes with its AI Governance plan, through sales. As of 5 Nov 2026.

Verosek is the gateway as well: one key routes your model calls, Bedrock among them, sets budgets and scans with no second vendor, and it reads the SQL statement and seals the reason for each decision. AgentCore Policy goes by user identity, a tool call's input parameters, earlier steps in the session and signals such as a guardrail's score; its docs do not say a policy reads a SQL statement. As of 5 Nov 2026.

An app leaves by changing the same two values. On a self-hosted deployment, on the Enterprise plan, the gateway, its signing key and your records stay with you.

Bring one real agent to a call, and we stand up a gateway for it.

Sources

Your agents touch real systems. Bring them to a call.

Still curious? Ask your favourite AI about Verosek.