Every other AI gateway, measured against the whole package
Provider-bundled gateways
Actualyze and Cloudflare AI Gateway
Actualyze. Keep Cloudflare AI Gateway, and give every AI dollar an owner from day one.
Actualyze and OpenRouter
Actualyze. Govern AI wherever you buy inference. Keep OpenRouter as one source among many.
Actualyze and Vercel AI Gateway
Actualyze. Keep Vercel AI Gateway. Governance shouldn't depend on whose inference you buy.
Platform-adjacent gateways
Actualyze vs Kong AI Gateway
Actualyze. Approvals that scale to thousands of people, and personal data masked from the first request.
Actualyze vs LiteLLM
Actualyze. The whole package for governing AI, with masking from the first request and no unknown cost as $0.
Actualyze vs Portkey
Actualyze. Personal data masked from the first request, inside the most complete AI governance platform.
Actualyze vs TrueFoundry
Actualyze. Every model and every budget gets its own approver, and finance closes the month on one statement.
Row by row, against the field
| Provider-bundled gateways | Platform-adjacent gateways | |||||||
|---|---|---|---|---|---|---|---|---|
| Actualyze | Cloudflare AI Gateway | OpenRouter | Vercel AI Gateway | Kong AI Gateway | LiteLLM | Portkey | TrueFoundry | |
| Routing and reach | ||||||||
| Routing reads the request | A routing model we train | Task quality and cost | Auto Router task types | Rules on the model name | Semantic balancer | Heuristics or LLM (beta) | Metadata and parameters | Heuristics or an LLM |
| Prompt cache and routing | Across models | Across models | Across providers | Across providers | Sticky sessions | Opt-in sticky sessions | Not documented | Sticky routing |
| Routing across models | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| One model, many providers | Yes | Configured fallbacks | Yes | Yes | Yes | Yes | Yes | Yes |
| Reaches private servers | Yes | Custom HTTPS endpoints | OpenRouter's providers | Catalog providers | Yes | Yes | Public URLs on SaaS | Enterprise plans |
| Cost and budgets | ||||||||
| Your own rate per provider | Yes | Yes | On Private Endpoints | Provider list price | Yes | Yes | Yes | Yes |
| When cost is unknown | Marked unpriced, not $0 | Not documented | Recorded cost | Market cost shown | Not documented | $0, with a warning | Shows $0.00 | Not documented |
| Budgets that stop requests | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Per-key spend limits | Yes | Metadata budgets | Yes | Yes | Per consumer | Yes | Yes | Per virtual account |
| Children sum within parent | Budget hierarchy | Independent rule buckets | Layered budgets | Stacked, each must pass | Most specific wins | Org budget caps teams | Workspace and key limits | Every rule must pass |
| Month-end chargeback | Monthly statement | Usage dashboards | Cost reports | Cost reports | Cost reports | Spend reports | Cost reports | Cost reports |
| Approvals and protection | ||||||||
| Who approves model access | Each model's own rule | Gateway access policies | Org admin allowlists | Vercel team owners | Admin-configured | Proxy admins grant | Admin-configured | Model Account Managers |
| Spend approved separately | Yes | Gateway write permission | Same org admins | Yes | Same admins | Team admins, if allowed | Delegated to workspaces | Yes |
| PII masked by default | On from the first call | Opt-in flag or block | Opt-in | Not documented | Opt-in | Opt-in | Opt-in | Opt-in |
| Deployment | ||||||||
| Deployment | Hosted, on-prem coming 2027 | Hosted | Hosted | Hosted | Konnect or self-hosted | Self-hosted | SaaS or hybrid | SaaS, hybrid, or self-hosted |
Not documented means the vendor's current documentation covers this area but doesn't describe the feature.
Sources for this table
Cloudflare AI Gateway
- Cloudflare AI Gateway Auto Router
- Routing reads the request
- Prompt cache and routing
- Routing across models
- Cloudflare AI Gateway dynamic routing
- One model, many providers
- Cloudflare AI Gateway custom providers
- Reaches private servers
- Cloudflare AI Gateway custom costs
- Your own rate per provider
- When cost is unknown
- Cloudflare AI Gateway costs
- When cost is unknown
- Cloudflare AI Gateway spend limits
- Budgets that stop requests
- Per-key spend limits
- Children sum within parent
- Cloudflare AI Gateway User Insights
- Month-end chargeback
- Cloudflare Access for AI Gateway
- Who approves model access
- Cloudflare API, update a gateway
- Spend approved separately
- Cloudflare AI Gateway DLP setup
- PII masked by default
- Cloudflare AI Gateway REST API
- Deployment
OpenRouter
- OpenRouter Auto Router
- Routing reads the request
- OpenRouter prompt caching
- Prompt cache and routing
- OpenRouter model fallbacks
- Routing across models
- OpenRouter provider selection
- One model, many providers
- OpenRouter private models
- Reaches private servers
- Your own rate per provider
- OpenRouter spend controls
- When cost is unknown
- Per-key spend limits
- Children sum within parent
- OpenRouter guardrails
- Budgets that stop requests
- Who approves model access
- Spend approved separately
- OpenRouter activity
- Month-end chargeback
- OpenRouter Sensitive Info guardrail
- PII masked by default
- OpenRouter quickstart
- Deployment
Vercel AI Gateway
- Vercel routing rules
- Routing reads the request
- Vercel session affinity
- Prompt cache and routing
- Vercel model fallbacks
- Routing across models
- Vercel provider filtering, ordering, and sorting
- One model, many providers
- Vercel AI Gateway pricing
- Reaches private servers
- Your own rate per provider
- Vercel Custom Reporting API
- When cost is unknown
- Month-end chargeback
- Vercel budgets and spend limits
- Budgets that stop requests
- Per-key spend limits
- Children sum within parent
- Spend approved separately
- Vercel model allowlist
- Who approves model access
- Vercel AI Gateway security and compliance
- PII masked by default
- Vercel AI Gateway docs
- Deployment
Kong AI Gateway
- Kong load balancing
- Routing reads the request
- Prompt cache and routing
- Kong AI Model Providers
- Routing across models
- Reaches private servers
- Kong AI Models
- One model, many providers
- Who approves model access
- Kong AI Gateway
- Reaches private servers
- Deployment
- Kong model cost management
- Your own rate per provider
- When cost is unknown
- Month-end chargeback
- Kong AI Rate Limiting Advanced policy
- Budgets that stop requests
- Per-key spend limits
- Kong AI Policies
- Children sum within parent
- PII masked by default
- Kong Konnect teams and roles
- Spend approved separately
LiteLLM
- LiteLLM Auto Routing (beta)
- Routing reads the request
- LiteLLM router, routing groups, and session affinity
- Prompt cache and routing
- One model, many providers
- LiteLLM fallbacks
- Routing across models
- LiteLLM vLLM provider
- Reaches private servers
- LiteLLM production deployment
- Reaches private servers
- Deployment
- LiteLLM custom model cost map
- Your own rate per provider
- LiteLLM troubleshooting for an unmapped model
- When cost is unknown
- LiteLLM budgets and rate limits
- Budgets that stop requests
- Per-key spend limits
- LiteLLM role-based access control
- Children sum within parent
- Who approves model access
- Spend approved separately
- LiteLLM spend tracking
- Month-end chargeback
- LiteLLM security and the OWASP LLM Top 10
- PII masked by default
Portkey
- Prisma AIRS AI Gateway conditional routing
- Routing reads the request
- Prisma AIRS AI Gateway load balancing
- Prompt cache and routing
- Prisma AIRS AI Gateway fallbacks
- Routing across models
- Portkey combining routing strategies
- One model, many providers
- Prisma AIRS AI Gateway custom hosts
- Reaches private servers
- Prisma AIRS AI Gateway overriding model details
- Your own rate per provider
- Prisma AIRS AI Gateway model pricing and cost management
- When cost is unknown
- Deployment
- Prisma AIRS AI Gateway budget limits
- Budgets that stop requests
- Per-key spend limits
- Children sum within parent
- Prisma AIRS AI Gateway analytics
- Month-end chargeback
- Prisma AIRS AI Gateway integrations
- Who approves model access
- Prisma AIRS AI Gateway workspace budget and rate limits
- Spend approved separately
- Prisma AIRS AI Gateway guardrails
- PII masked by default
TrueFoundry
- TrueFoundry Auto Routing by request complexity
- Routing reads the request
- TrueFoundry virtual models
- Prompt cache and routing
- Routing across models
- One model, many providers
- TrueFoundry connect private models and MCP servers
- Reaches private servers
- TrueFoundry cost tracking
- Your own rate per provider
- When cost is unknown
- TrueFoundry budget limiting
- Budgets that stop requests
- Per-key spend limits
- Children sum within parent
- Spend approved separately
- TrueFoundry access control
- Per-key spend limits
- Who approves model access
- Spend approved separately
- TrueFoundry metrics dashboard
- Month-end chargeback
- TrueFoundry guardrail policies
- PII masked by default
- TrueFoundry deployment overview
- Deployment
Six questions every AI gateway should answer live
If your AI gateway can't tell you who approved a model or what last month cost each team, it's just moving traffic. Put these questions to every vendor on your list, and ask to see each answer working in the product. Actualyze answers every one today, and each comes with a check you can run in your own trial.
Who approves a team's access to each model?
The leading delegation and approval system for AI spend starts here. In Actualyze, each model names its own approver.
Request a model that needs approval as a team member, and check who receives the request and where the decision is recorded.
What decides which model answers each request?
In Actualyze, a routing model we train sizes each request and picks the cheapest model strong enough, the best model routing in the field.
Send an easy question and a hard one to one Virtual Model, then see which model each was routed to, and why.
What happens to a call when its budget runs out?
Actualyze rejects it before any model is contacted, so a budget is a real limit and never a surprise on the bill.
Set a small test budget and confirm the next request is rejected once it reaches its limit.
Does an unknown cost ever show up as $0?
An unknown cost is never $0 in Actualyze, which marks it unpriced and flags it for FinOps, so no spend hides behind a zero.
Connect a third-party endpoint with no catalog price, call it, and check the call reads unpriced, not $0.
What is protected before anyone writes a policy?
Personal data is masked from the first request in Actualyze, in prompts and responses, by a default guardrail nobody can delete.
Open a new workspace's guardrails before writing any policy, and confirm the default guardrail is already enforcing.
Can finance close the month on AI spend?
Finance closes the month on AI spend with one Actualyze statement, a row for each budget, reviewed and then settled.
Generate a statement for a month with traffic, then move it from draft to reviewed to settled.
Common questions
What is the difference between an AI gateway and an AI governance platform?
Who approves model access and spend in Actualyze?
How does Actualyze bill?
Give every model an approver and every call a budget.
Connect the providers you already use and test every claim on this page against your own traffic. Or book a demo. We'll walk you through it, and send the Virtual Model engine whitepaper if routing is on your list.