Skip to content

Compare

Intended Gateway vs the alternatives.

Honest comparison of the tool-call-governance and AI-ops products that share the base-URL-swap integration shape. We're calling the differentiators clearly: where we win, where they win, where the categories simply don't overlap.

Cells are kept current as competitor capabilities ship. If you spot an inaccuracy, email facts@intended.so and we'll correct it. Source links and product version snapshots are tracked in our public comparison sources doc.

FeatureIntendedCloudflare AI GatewayLakeraPortkeyWiz Runtime
Base-URL-swap integration
YesYesYesYeseBPF (host-level)
Authority decision per tool call (allow / deny / escalate)
YesNoYes (prompt level)LimitedNo
Human-in-the-loop escalation queue
Built inNoVia webhookNoNo
Cryptographic Authority Token issued on approval
Lets the action's downstream verifier prove the authority chain without re-checking with the gateway.
Yes (RS256 + JWKS)NoNoNoNo
Hash-chained immutable audit
YesLogs onlyLogs onlyLogs onlyLogs only
Physical-AI / robotics support
Includes a Python verifier that runs on the robot to gate actuation on a fresh authority token before motors move.
Yes (NVIDIA NIM + ROS2 token verifier)NoNoNoNo
AWS Bedrock binary event-stream support
YesPartialNoPartialNo
Self-hostable (your VPC, your image)
Yes (Apache-2.0 source)NoEnterprise tierEnterprise tierYes (agent install)
Customer keeps the model API key
AlwaysAlwaysAlwaysConfigurableN/A (host-level)
Primary trust anchor
Tenant key + JWKS public keysCloudflare accountLakera accountPortkey accountWiz agent identity
Provider coverage at GA
Anthropic, OpenAI, NIM, Bedrock-Anthropic, Vertex-GeminiAnthropic, OpenAI, Bedrock, Vertex, othersAnthropic, OpenAI, BedrockAnthropic, OpenAI, 100+Host-level (any binary)

Where the others win

We're honest about what we don't do.

Cloudflare AI Gateway

If your need is hit-rate caching, anonymized analytics, and rate limiting across 100+ providers — Cloudflare ships those today, free at edge scale. We don't compete on caching. Our wedge is decision-per-tool-call with audit chain + human escalation, which Cloudflare doesn't offer.

Lakera Guard

Lakera is the leader in prompt-injection and content moderation classifiers. If your threat model is “a user is trying to jailbreak my chatbot,” Lakera's classifiers are trained on more attack data than anyone else. Our differentiation is downstream — what to do once the model wants to take a tool action.

Portkey

Portkey is the AI-ops Swiss Army knife — observability, prompt versioning, retries, fallback, fan-out. If you need that breadth, you pick Portkey. If you need a hard authority decision per tool call with cryptographic evidence, you pick us. They can coexist.

Wiz Runtime

Wiz operates at the host eBPF layer — they see syscalls, not LLM tool calls. Their runtime category is cloud-native security broadly. Different category; we're complementary, not substitutes.

When to pick Intended

  • When agent tool calls take real-world actions — payments, emails, deploys, robot actuation — and you need to prove the action was authorized, not just hope.
  • When your buyer's security team will demand a hash-chained audit trail and a cryptographic authority token they can verify offline.
  • When you're running NVIDIA-stack physical AI (NIM, NeoClaw, Isaac Sim, ROS2) and you need a verifier that gates actuation on a fresh authority token, not just a cloud-side approval that never reaches the robot.
Intended Gateway vs Cloudflare AI Gateway / Lakera / Portkey / Wiz | Intended