The top features that matter in each category, why a buyer cares, and an honest check-box map against the largest name in that space. Split into the three surfaces Smartflow governs: LLM, MCP, and Agent.
Who else: Portkey (VPC / airgap), AWS Bedrock (region lock), TrueFoundry.
Regulated buyers can't let prompts, completions, or evidence leave a boundary they control. Sovereignty here means the inference path and the audit trail stay in the customer's tenant, region, and object store — not just "we're SOC 2."
Runs inside your cloud or fully disconnected. FedRAMP / IL5 / GAIA-X SKUs, not a shared multi-tenant SaaS.
Sovereignty tab shows where data sits and what's stripped before it moves. Posture you can hand an examiner.
Evidence lands in your S3 / Azure / GCS / SnapLock with object-lock retention. Residency of the audit trail, not just live logs in our DB.
Pull enterprise content without routing file bodies through a third SaaS middleman.
Route sensitive traffic to weights on your own hardware so inference never has to leave the box.
| Capability | Smartflow | Portkey | AWS Bedrock | TrueFoundry |
|---|---|---|---|---|
| VPC / airgap deploy | ||||
| Region + FIPS + minimisation posture view | ||||
| WORM evidence in customer object lock | ||||
| First-party content connectors (no 3rd SaaS) | ||||
| Local / self-hosted model path |
Who else: Portkey (virtual keys), Okta / Entra (SSO only), Cloudflare Access.
Provider API keys are the crown jewels, and "who called the model" has to survive an audit. Smartflow puts identity on the wire for humans, agents, and the device — not just an SSO login at the edge.
Provider secrets never leave the gateway. Rotate or revoke without touching app code.
AD group maps to team, budget, and policy. Access changes flow from the directory, not a spreadsheet.
Force verified-identity re-auth on high-risk actions and seal it into the audit chain.
Establishes who the agent is, not just the human who launched it — carried on egress.
Ties a request to the laptop and the coding agent at the intercept point.
| Capability | Smartflow | Portkey | Okta / Entra | Cloudflare Access |
|---|---|---|---|---|
| Virtual keys (secrets stay in gateway) | ||||
| SSO with group → budget / policy sync | ||||
| Verified-identity step-up on risky actions | ||||
| Agent identity credentials (AIDA) | ||||
| Device / coding-agent identity at intercept |
Who else: Portkey (audit DB), Langfuse, Datadog.
Most tools log requests to a database. An examiner asks a harder question: can you prove the record wasn't edited after the fact, and when exactly did it happen? Smartflow's trail is tamper-evident and independently verifiable, then fans out to the systems auditors already trust.
Every call carries user, model, cost, and risk tier. One record, not a metric and a log to reconcile.
Records are hash-chained, and an open-source verifier lets a third party check the chain independently.
Trusted-time proof plus write-once storage. Examiner-grade, not "we keep logs indefinitely."
1.10 stamps the control and policy that fired onto the record, so a finding maps straight to a rule.
The same record exports to Splunk, OTel, and ServiceNow without re-deriving it per tool.
| Capability | Smartflow | Portkey | Langfuse | Datadog |
|---|---|---|---|---|
| Per-request trace with cost + risk tier | ||||
| Tamper-evident chain + independent verifier | ||||
| RFC 3161 trusted timestamps + WORM | ||||
| Control / policy IDs on the record | ||||
| Same record to Splunk / OTel / ServiceNow |
Who else: Portkey / Prisma AIRS, Enkrypt, Prompt Security.
Compliance can't be a nightly scan — it has to happen on the request, before the data moves. Smartflow inspects content inline, ties it to the framework that governs that team, and turns policy documents into checkable rules.
PII, secrets, and regulated patterns caught on the request path — not flagged after the fact.
HIPAA, GDPR, PCI and more attach by directory group, so the right rules apply to the right team automatically.
Opt-in tokenization keeps workflows usable so teams don't route around the gateway to get their data back.
Paste an acceptable-use doc and get discrete, checkable rules out — not a PDF nobody enforces.
Article-by-article evidence binder for a Notified Body — concrete conformity, not "audit-ready" blog copy.
| Capability | Smartflow | Prisma AIRS | Enkrypt | Prompt Security |
|---|---|---|---|---|
| Inline PII / secret / regulated-pattern detect | ||||
| Framework assignment by directory group | ||||
| Reversible PII tokenization | ||||
| Policy doc → checkable rules (atomizer) | ||||
| EU AI Act article-level conformity binder |
Who else: Prisma AIRS (network / CISO channel), LiteLLM (thin policy), Portkey.
Governance is only real if it's enforced on the request and it closes the loop back to the system of record. Smartflow attaches policy inline, gives risk a stop button, and pushes findings into the GRC tools the second and third lines already run.
Bind policy to a virtual key, AD group, team, or model. Enforced on the call, not documented in a wiki.
Hold risky actions for human sign-off, or flip to read-only / halt when something's wrong.
Scores your own traffic and suggests rules. Nothing leaves the box to a third-party test service.
Finding flows into ServiceNow / Archer / OneTrust and the closure flows back — not a one-way alert.
Unsigned or unapproved MCP servers don't get a tool call. Supply-chain control for agent tools.
| Capability | Smartflow | Prisma AIRS | LiteLLM | Portkey |
|---|---|---|---|---|
| Inline policy by key / group / team / model | ||||
| Approval queue + emergency stop | ||||
| In-process red-team harness | ||||
| Closed-loop GRC (finding in, closure back) | ||||
| MCP trust registry gating tool calls |
Who else: Helicone, CloudZero / Flexera, LiteLLM spend dashboards.
Cost tools show you the bill after it's spent. Because Smartflow is on the request path, the same trace that enforces policy also meters spend — so a budget breach can become a route change or a cap, not just another dashboard.
Cost by provider, model, user, and group from the record the gateway already enforces. No second pipeline.
Forecast the overrun and stage a policy in response — not an email that lands after the money's gone.
Surfaces ungoverned spend — traffic that bypassed the gateway — by comparing provider bills to what we metered.
A spend spike turns into a proposed rule you can review and enforce, closing the loop on runaway cost.
Cache and token savings shown against actual spend — enforcement plus visibility, not invoice-only.
| Capability | Smartflow | Helicone | CloudZero / Flexera | LiteLLM |
|---|---|---|---|---|
| Spend by provider / model / user / group | ||||
| Budget breach → enforced policy / reroute | ||||
| Billed-vs-metered bypass reconciliation | ||||
| Anomaly → draft policy from the spike | ||||
| Cache / token savings next to the bill |
Who else: LiteLLM, Portkey, Kong AI Gateway.
Routing is table stakes, so the question is what it's tied to. Smartflow's routing is drop-in for the SDKs teams already use, and every route decision can be driven by the same policy and identity the rest of the platform enforces.
Point the base URL at the gateway. No app rewrite for either endpoint style.
Retryable vs non-retryable failures handled distinctly, so a provider blip doesn't take the app down.
Send group X to a cheaper model, or a regulated team to a compliant one — as a rule, not a code branch.
Self-hosted and cloud targets are first-class, so sovereignty routing is a config choice.
Scope which models a key can reach, so access control and routing are the same control.
Easy turns go cheap, hard turns stay on the model you asked for. Same scorer in Smartflow and Halo. Install notes.
| Capability | Smartflow | LiteLLM | Portkey | Kong AI GW |
|---|---|---|---|---|
| Drop-in OpenAI + native Anthropic | ||||
| Fallback chains (retryable vs not) | ||||
| Policy / identity-driven routing | ||||
| Local / self-hosted as first-class target | ||||
| Virtual-key model allow-lists | ||||
| Lowest-cost / effort router (prompt-scored cheap lane) |
Who else: LiteLLM (exact + Qdrant semantic), Portkey (semantic cache), Helicone.
Caching cuts cost and latency, but most semantic caches need a vector DB bolted on. Smartflow does semantic caching in-process and extends it past the LLM into MCP tool calls and multi-step agent runs.
Semantic hits without a sidecar vector DB to run and secure. One less dependency in the boundary.
Compress context on the way through, with an optional faithfulness check so you don't cache a hallucination.
Uses the provider's own prompt-cache when it's cheaper, so you don't pay twice for the same prefix.
Caches tool discovery and repeat calls, and reports the measured percentage of calls avoided.
Reuses results across repeated multi-step agent tasks so the same plan doesn't re-run from scratch.
| Capability | Smartflow | LiteLLM | Portkey | Helicone |
|---|---|---|---|---|
| Semantic cache without sidecar vector DB | ||||
| In-flight compression + faithfulness check | ||||
| Provider prompt-cache injection | ||||
| MCP discovery + tool-call cache | ||||
| Trajectory cache for agent tasks |
Who else: LiteLLM, Portkey, Cloudflare AI Gateway.
On the model surface Smartflow is a drop-in gateway that also enforces policy on the completion. You get the routing and cache incumbents offer, plus inline governance on the same request.
| Protocol-native capability | Smartflow | LiteLLM | Portkey | Cloudflare AI GW |
|---|---|---|---|---|
Drop-in /v1 + Anthropic /messages | ||||
| Streaming | ||||
| Virtual keys | ||||
| Semantic cache (no sidecar) | ||||
| Inline policy on completions |
Who else: LiteLLM MCP, generic MCP hosts (Claude Desktop / Cursor), Cloudflare.
MCP hosts connect tools; they don't govern them. Smartflow sits in front of the tool call — gating which servers are trusted, which groups reach which tools, and holding destructive calls for approval.
| Protocol-native capability | Smartflow | LiteLLM MCP | MCP hosts | Cloudflare |
|---|---|---|---|---|
| Trust registry (signed / approved servers) | ||||
| AD-gated tools by group | ||||
| Discovery cache | ||||
| Trajectory cache | ||||
| Shield on destructive tool calls | ||||
| Per-server cost attribution |
Who else: Google A2A (protocol), LangGraph / CrewAI (orchestration), Portkey.
Orchestration frameworks build agents; they don't sit on the wire when the agent acts. Smartflow is the enforcement point for agent-to-agent traffic — identity, risk tiers, approval, and a signed identity on egress.
| Protocol-native capability | Smartflow | Google A2A | LangGraph / CrewAI | Portkey |
|---|---|---|---|---|
| A2A gateway + Agent Cards | ||||
| AIDA agent credentials | ||||
| Action-risk tiers (T1–T3) | ||||
| Human approval on high-risk actions | ||||
| Signed identity on egress (Web Bot Auth) |
Don't get blindsided on a call. Say this before the prospect does.
APERION Smartflow · Feature Guide 1.10 · Capability claims reflect shipped product; competitor cells are value-level and current at time of writing.