On this page
Alternative to TrueFoundry

The TrueFoundry 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 TrueFoundry takes two values, base URL 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 TrueFoundry?

Verosek is for platform teams whose own agents write to production systems. TrueFoundry's gateway sits on a platform that also trains and deploys models on Kubernetes. Its three built-in checks for moderation, personal data and prompt injection are available only when TrueFoundry hosts the gateway. Where you host the control plane, its Global Authentication server remains within TrueFoundry. Verosek's rules and scanning run in the gateway, and the gateway holds no licence check or call to a Verosek host.

It parses the statement, not a pattern in the text.

Verosek reads the SQL statement itself, where TrueFoundry's SQL Sanitizer says “Pattern-based detection” and “Complex obfuscation may bypass detection”. Verosek parses seven SQL dialects, so you can give an agent a production system and say exactly what it may do to it. TrueFoundry's Cedar holds argument values as strings.

A record your security review can read.

Verosek seals one record for each request, model calls and tool calls together, with the reason for each decision, where TrueFoundry's home page says “Immutable Audit Logging” and its docs describe platform activity, as metadata. TrueFoundry's request logging can be switched off per subject, model or MCP server. 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. TrueFoundry's gateway never fails a request even if its log queue is down, and its output guardrails are not applied when a response is streamed.

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. TrueFoundry's Cedar and OPA policies, which you write, can read tool arguments. You can keep your proxy behind Verosek, which routes to any OpenAI-compatible server.

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

At a glance: Verosek and TrueFoundry
The pointVerosekTrueFoundry
Model routingOpenAI, Anthropic, Google, Azure, Bedrock, Ollama and any OpenAI-compatible server, with fallbackOver 1000 LLMs, with load balancing, failover and retries
Budgets and limitsAllowed models, budget, rate limits and expiry on each keyBudget rules by plan: one, up to 10, or unlimited
Tools and connectorsA catalogue of connectors, with OAuth where the server needs itAn MCP gateway by plan: 5 servers, or full from Pro
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 recipientCedar or OPA policies you write, and a SQL Sanitizer that matches patterns
ScanningPrompt injection, personal data and secrets in prompts, replies, tool arguments and tool results, on both plans, with no second vendor to buyBuilt-in guardrails from Pro; third-party and custom ones on Enterprise
The recordOne sealed record for each request, with the reason for each decisionMetadata audit logs of platform activity from Pro; request logs on an async queue
Where it runsEnterprise: private cloud, VPC or air-gapped, deployed with usHosted by TrueFoundry; Enterprise: VPC, on-prem and data residency, with a Helm chart

As of 5 Nov 2026.

What moving takes

Is Verosek a drop-in replacement for TrueFoundry?

An app on an SDK.

Your calls name a TrueFoundry model, such as openai-main/gpt-4o. You change the base URL and the key. Give your Verosek deployments the same names, and those calls stay as they are.

Models you serve.

Models you train or serve stay where they run. Verosek routes to any OpenAI-compatible server, so they stay in reach.

Virtual models.

A virtual model becomes a priority order among your deployments, with retries and cooldown.

Virtual servers.

A virtual server carves a tool subset for a team or app. Those lists become per-tool rules on each key.

Access by identity.

TrueFoundry's access follows user, team or virtual account. Verosek's rules live on the key, and a key can bind tool calls to the end user it names, so rules set per team or per user move onto the keys they hold.

Cedar or OPA policies.

OPA policies run on your own server. Policies you wrote become rules on each key, and we set that up with you.

Self-hosting.

Self-hosting TrueFoundry means Kubernetes and a Helm chart, and its authentication and analytics servers stay outside your infrastructure. On Verosek's Enterprise plan we deploy the gateway with you, in your private cloud, your VPC or air-gapped.

Checks when you self-host.

Where its hosted checks stop, TrueFoundry's docs name third-party checks in their place, some on your own key. Shield's checks ship in the gateway, so a detector you pay for separately can go.

When TrueFoundry is enough

If you want one vendor to train and deploy your models as well as route to them, TrueFoundry's platform covers that.

Frequently Asked Questions

Three things: whether the checks stay when you host it, what a rule reads beyond a pattern, and whether a missing record stops the call. Verosek answers all three.

Team is $999 a month, billed yearly. Enterprise has custom terms. Both plans start with a call. See the plans.

Verosek does not train or serve models. TrueFoundry trains and deploys models on Kubernetes. As of 5 Nov 2026.

Yes. On the Enterprise plan Verosek can run wholly in your environment, deployed with us: private cloud, VPC or air-gapped. Shield's rules run in the gateway itself, so an Enterprise deployment in your environment keeps them.

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.