CompanyFabric vs Portkey
Portkey sells the enterprise control plane: traces, guardrails, fallbacks, and governance over your own provider accounts. CompanyFabric sells the metered front door: one key, exact prices, prepaid balance, media models, and agents. They overlap at the proxy layer and diverge everywhere else.
The differences
Side by side
| CompanyFabric | Portkey | |
|---|---|---|
| Center of gravity | Billing-grade metering + one balance across modalities | Observability, guardrails, and routing policy |
| Setup | Change base URL, add key, done | Config-driven gateway with policy objects |
| Payment doors | Credits, or BYOK at 0% | Your provider accounts; Portkey bills for the platform |
| Media models | First-class, per-second/per-image metering | Pass-through where providers support it |
Verdict
Which should you pick?
Enterprises standardizing governance over existing provider contracts fit Portkey. Builders who want prices, one balance, and a playground-to-production loop fit CompanyFabric — and Portkey can front us as an upstream if you want both.
FAQ
Frequently asked questions
Can I use Portkey's guardrails with CompanyFabric?
Yes — register api.companyfabric.com/v1 as a custom OpenAI-compatible provider in Portkey and its policies apply on top of our routing.
One key. Every model. Exact prices.
Migrating from Portkey is a base-URL change. Free starter credits included — no subscription required.