starter.wikiSearch⌘K

Managed AI gateway and control plane

Portkey

A managed AI control plane combining gateway routing, retries, fallbacks, keys, budgets, logs, observability, and governance.

Visit official site

Editorial verdict

Choose Portkey when a managed AI control plane removes meaningful routing and governance work, after modeling provider bills, gateway traffic, recorded logs, retention, privacy, and deployment.123

Best for

  • Managed multi-provider routing and fallbacks
  • Centralized keys, budgets, logs, and governance
  • Teams that value a hosted control plane
123

Not ideal for

  • Teams requiring a self-operated gateway by default
  • Buyers treating gateway fees as the entire model bill
  • Products unable to govern request and response logging
123
Main trade-off

A managed control plane centralizes reliability and governance while adding request, log, retention, data, deployment, and platform dependence on top of provider inference.123

Product boundary

Whether Portkey's managed gateway and control plane justify their request, logging, retention, deployment, and provider-billing boundaries.

Portkey's hosted control plane and open-source gateway are distinct deployment routes. Gateway traffic, recorded logs, retention, observability, provider inference, caching, privacy configuration, and enterprise deployment have separate cost and data boundaries.123

For: Teams wanting a managed AI gateway with centralized routing, observability, budgets, keys, and governance

  • The production workload, language, model, provider, or deployment boundary changes
  • Current pricing, retention, data use, policy, or regional support changes
  • Measured quality, latency, reliability, or operating cost no longer fits

Why teams consider Portkey

  • Gateway controlsRouting, retries, fallbacks, timeouts, caching, keys, and budgets share a control plane.123
  • Operational visibilityLogs, traces, metrics, and governance can use the same request path.123
  • Deployment choiceHosted and open-source gateway routes have different ownership and feature boundaries.123

Pricing

Hosted plans combine subscription, recorded-log allowance, retention, overages, and Enterprise terms; provider inference remains separately billed.1

Current official route

Developer, Production, or Enterprise

Verified 2026-07-27: Portkey publishes Developer and Production plan boundaries around recorded logs and retention, with usage overages and custom Enterprise terms. Underlying provider inference is separate.1

Gateway layer
Plan, recorded logs, retention, overage, and Enterprise features1
Provider layer
Model-provider input, output, cache, audio, image, or batch charges1
Data boundary
Logging configuration and privacy mode affect stored request data1
Pricing checked View official pricing

Portkey vs alternatives

LiteLLM

Choose when
Choose LiteLLM when a self-operated proxy boundary is a requirement and the platform team can own reliability, credentials, upgrades, telemetry, policy, and provider-specific compatibility.
Avoid when
Teams without a critical-proxy operator
Compared with Portkey
Open-source proxy control reduces application coupling while transferring availability, security, upgrades, logging, compatibility, and provider-change response to the platform team.45

OpenRouter

Choose when
Choose OpenRouter when hosted model and provider choice is more valuable than direct-provider control, after governing fees, credits or BYOK, routing, provider logging, retention, and fallback behavior.
Avoid when
Teams requiring self-hosted gateway control
Compared with Portkey
Broad hosted model access reduces integration work while adding aggregator fees, credits, provider-routing, privacy, availability, and another commercial dependency.67

Vercel AI Gateway

Choose when
Choose Vercel AI Gateway when its managed endpoint and provider operations reduce meaningful work, after verifying current pricing, credits, BYOK, failover, provider order, and ZDR eligibility.
Avoid when
Teams requiring a self-operated gateway
Compared with Portkey
A managed Vercel gateway simplifies provider access and failover while adding gateway, credit, catalog, routing, data-policy, and platform dependence.89

Resources and sources

Official product, documentation, pricing, and policy sources

  • Portkey pricing
    Open
  • Portkey AI Gateway documentation
    Open
  • Portkey request logging configuration
    Open
  • LiteLLM pricing
    Open
  • LiteLLM proxy documentation
    Open
  • OpenRouter pricing and billing FAQ
    Open
  • OpenRouter provider routing
    Open
  • Vercel AI Gateway product and pricing
    Open
  • Vercel AI Gateway documentation
    Open
  1. 1
    Portkey pricing

    Portkey · Accessed Official

  2. 2
    Portkey AI Gateway documentation

    Portkey · Accessed Official

  3. 3
    Portkey request logging configuration

    Portkey · Accessed Official

  4. 4
    LiteLLM pricing

    LiteLLM · Accessed Official

  5. 5
    LiteLLM proxy documentation

    LiteLLM · Accessed Official

  6. 6
    OpenRouter pricing and billing FAQ

    OpenRouter · Accessed Official

  7. 7
    OpenRouter provider routing

    OpenRouter · Accessed Official

  8. 8
    Vercel AI Gateway product and pricing

    Vercel · Accessed Official

  9. 9
    Vercel AI Gateway documentation

    Vercel · Accessed Official