On this page
Alternative to Portkey

The Portkey 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 Portkey 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 Portkey?

Verosek is for platform teams whose own agents write to production systems. Palo Alto Networks closed its purchase of Portkey on 29 May 2026, and its docs now say “Portkey is now PRISMA AIRS AI Gateway”. New access policies for MCP servers are on the Prisma AIRS track only, and air-gapped deployment is closed to new customers.

It reads the statement, not regex over its text.

Verosek reads the SQL statement itself, where Portkey's checks on tool calls are text and structure checks, such as regex and JSON schema, with a webhook for your own. Verosek parses seven SQL dialects. Portkey's personal-data, moderation and partner checks are not available for MCP tool calls, and its claim-based rules per tool are listed as not yet available.

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 Portkey logs each MCP request, and its Audit Logs cover admin actions on Enterprise. 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. On model calls, Portkey's guardrails run in the background and log by default, and a check that errors does not block unless you set it to. On streaming responses, its output guardrails are informational only.

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. Portkey's MCP gateway is a proxy between clients and servers, handling authentication, access control and logging. 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 Portkey
The pointVerosekPortkey
Model routingOpenAI, Anthropic, Google, Azure, Bedrock, Ollama and any OpenAI-compatible server, with fallbackOne interface to over 3,000 models, with fallback and caching
Budgets and limitsAllowed models, budget, rate limits and expiry on each keyGranular budget and rate limits on Enterprise
Tools and connectorsA catalogue of connectors, with OAuth where the server needs itA proxy between MCP clients and servers, with authentication and access control
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 recipientTools switched on or off by organization or workspace, text and structure checks, and access policies new on Prisma AIRS
What makes a blockA named rule. By default, a model's score alone only flags.On model calls, a check set to deny: by default a failed check still sends the request
ScanningPrompt injection, personal data and secrets in prompts, replies, tool arguments and tool results, on both plans, with no second vendor to buyDeterministic checks on Developer, LLM and partner checks on Production
The recordOne sealed record for each request, with the reason for each decisionLogs of each MCP request; Audit Logs of admin actions on Enterprise
On a published planTeam at a published $999 a month, with every Shield profile, sealed records and SSOAudit Logs, SSO and granular budgets on Enterprise, at a custom price
Where it runsEnterprise: private cloud, VPC or air-gapped, deployed with usEnterprise: managed SaaS or hybrid; air-gapped is closed to new customers. Open source: a self-hosted MIT gateway

As of 5 Nov 2026.

What moving takes

Is Verosek a drop-in replacement for Portkey?

An app on an OpenAI SDK.

It reaches Portkey through its gateway URL and Portkey's headers. You change the base URL and the key, and those headers go.

A saved prompt.

A prompt saved in Portkey is called at runtime by its id. Keep the prompt in your own code, and the SDK call carries it.

Fallback chains.

Portkey's fallback chains are a prioritized list of providers and models. A fallback chain becomes a priority order among your deployments.

API keys.

On Portkey, the API key determines which servers and tools are accessible. Each key becomes a Verosek key, with its rules, tool by tool.

Partner guardrails.

Portkey's catalogue of partner checks runs on model traffic. Shield's checks ship in the gateway, so a detector you pay for separately can go.

The open-source gateway.

MCP gateway code is on a pre-release branch, not on Portkey's open-source main. Verosek gives you one gateway and one key for model calls and MCP tool calls, with one sealed record per request.

Webhook checks you wrote.

Portkey's webhook check sends tool call data to your own service. Policies you wrote become rules on each key, and we set that up with you.

A hybrid deployment.

In hybrid, your data plane runs in your VPC, and Portkey hosts the control plane. On Verosek's Enterprise plan, the whole gateway and its admin console run in your environment, deployed with us.

MCP servers.

Portkey's MCP gateway needs a local server exposed over HTTP first. Verosek reaches remote servers and runs local ones itself, under the key's rules.

When Portkey is enough

If your agents only call models and never change anything, a router may be enough.

Frequently Asked Questions

Three things: what a check can read on a tool call, whether a check that errors blocks, and whether anyone outside can check the record. Verosek answers all three.

Verosek routes to OpenAI, Anthropic, Google, Azure, Bedrock and Ollama by name, and to any other provider through an OpenAI-compatible server.

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.

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.