Visionality vs Portkey
Portkey routes. Visionality reconciles.
Same wire-level position. Same swap-the-base-URL deploy. Different question on the homepage — and a different room in the building where the decision gets made.
What to say in the room
The question comes from a specific seat. The answer should too.
Portkey's answer is technically true and strategically thin. Here's how the same question lands with a CFO, a CHRO, a PMO, and a CISO.
CFO
"Show me what we spent on AI last month, by project, by team — joinable to our GL."
CHRO
"Who has access to AI, and what happens when someone leaves?"
PMO
"How much did the redesign sprint actually cost us in AI tokens?"
CISO
"How do we keep the bill from running over, even if a key leaks?"
The details
Capability-by-capability, where the postures diverge.
Use this when engineering needs to validate that the wire-level promise actually holds up.
Posture
| Capability | Portkey | Visionality |
|---|---|---|
| Primary buyer | VP Engineering | CFO — pulls in CIO / CHRO / PMO |
| Frame | AI gateway — routing, caching, fallbacks | AI commit ledger — reconciliation to person × project × task × token |
| What changes Monday morning | Faster, more reliable inference | Four awkward stakeholder questions stop being awkward |
Attribution
| Capability | Portkey | Visionality |
|---|---|---|
| Per-request user identity | Metadata field (set by app code, trust-the-caller) | SSO sub claim signed into the token envelope; verified offline |
| Per-request project / task | Custom metadata you write | First-class --task / --memo / --url flags on key issuance; denormalized onto every commit row |
| HRIS-aware revocation | Manual | BambooHR / Workday / Rippling joiners-movers-leavers feed → auto-revoke |
Spend control
| Capability | Portkey | Visionality |
|---|---|---|
| Hard budget cap | Policy at the gateway | Budget binding signed into the token; gateway fast-fails 402 before any LLM call |
| Real-time burn-down per project | Dashboards | Hard counter — UI + ledger row + 402 response in one trip |
| Chargeback export | Logs export | CSV with GL codes + cost centers, joinable to Workday cost-center mapping |
Audit & compliance
| Capability | Portkey | Visionality |
|---|---|---|
| Audit row mutability | Application-level append | Append-only at the SQL role; the app role cannot UPDATE or DELETE |
| PII pre-flight | Guardrail plugin | 12 detectors, fail-closed, runs before the call leaves your network |
| SOC 2 evidence | Custom queries | Two-click evidence pack mapped to CC controls |
Honest take
When Portkey is the right answer.
If the buyer is a VP Engineering optimizing for routing strategy, cost-of-inference ergonomics, caching ratios, and SDK convenience — and the company doesn't need to defend its AI bill to a CFO yet — Portkey is the cleaner fit. We don't compete on prompt-caching tactics or model-routing heuristics. We compete on whether the bill reconciles to people, projects, and tasks against a row that can't be quietly rewritten. If that question hasn't been asked at your company yet, it will be.
See it live, in your stack.
30-minute deploy. Bring your own LLM keys. Same wire-level surface area as Portkey — your existing SDK code works unchanged.