---
title: "Portkey vs LiteLLM (2026): AI Gateways Compared - API7.ai"
description: "Portkey vs LiteLLM compared in depth: architecture, routing, caching, guardrails, observability, governance, self-hosting, and pricing — and how to choose."
url: "https://api7.ai/portkey-vs-litellm"
---

# Portkey vs LiteLLM: Which AI Gateway in 2026?

By API7.ai Team

Last updated: June 2026

Portkey and LiteLLM take different shapes: Portkey pairs an open-source gateway with a hosted observability and governance platform, while LiteLLM is a Python-based proxy and SDK with budgets and virtual keys in the open-source core. This guide compares them on architecture, routing, caching, guardrails, observability, governance, self-hosting, and pricing so you can choose the right fit.

TL;DR

Portkey pairs an MIT TypeScript gateway with a paid hosted control plane for observability and governance; LiteLLM is a Python SDK and proxy with broad provider coverage and OSS budgets. Both are MIT at the core, and neither does semantic routing or ensemble — so the choice comes down to provider breadth and a hosted governance UI versus a Python SDK and open-source budgets.

- Teams wanting hosted observability + governance: Portkey
- Python teams wanting an SDK + OSS budgets: LiteLLM

<!---->

- [At a glance](#at-a-glance)
- [What is Portkey?](#what-is-portkey)
- [What is LiteLLM?](#what-is-litellm)
- [Feature comparison](#feature-comparison)
- [Pricing](#pricing)
- [When to use each](#choose)
- [Bottom line](#bottom-line)
- [FAQ](#faq)

## Portkey vs LiteLLM at a glance

Portkey leads on provider breadth and a hosted governance UI; LiteLLM keeps more governance in open source. Neither offers semantic routing or ensemble.

| Dimension           | Portkey                                   | LiteLLM                          |
| ------------------- | ----------------------------------------- | -------------------------------- |
| Best for            | Hosted observability + governance         | Python SDK + OSS budgets         |
| Core & runtime      | TypeScript gateway + hosted control plane | Python (SDK + proxy)             |
| Open-source license | MIT gateway; platform commercial          | MIT core; enterprise/ commercial |
| Provider coverage   | 1,600+ models / 45+ providers             | 100+ providers                   |
| Semantic routing    | — Rule-based only                         | — Not documented                 |
| Ensemble / fusion   | — Not documented                          | — Not documented                 |
| Caching             | ✓ Simple + semantic                       | ✓ Exact + semantic               |
| MCP gateway         | ✓ Documented                              | ✓ In open source                 |
| Self-host / VPC     | OSS self-host; VPC = Enterprise           | Docker/K8s; no managed VPC       |
| SSO / SCIM          | Enterprise-only                           | Enterprise-only                  |

## What is Portkey?

Portkey is an AI gateway pairing an open-source TypeScript gateway with a paid hosted control plane for observability, prompt management, and governance.

Portkey is an AI gateway that pairs an open-source TypeScript gateway (MIT) with a hosted control plane for observability, prompt management, and governance. It advertises 1,600+ models across 45+ providers.

Language

TypeScript (Node.js)

License

MIT gateway + commercial platform

Form factor

OSS gateway + hosted SaaS

Best for

Hosted observability & governance

### Pros

- 1,600+ models across 45+ providers
- Simple and semantic caching
- Documented MCP gateway
- Mature observability, analytics, and prompt management

### Cons

- RBAC (Production tier), SSO/SCIM, VPC deploy, granular budgets are paid
- Conditional routing is rule/parameter-based, not semantic
- No documented ensemble; log/metric retention is tiered by plan

## What is LiteLLM?

LiteLLM is an open-source Python SDK and proxy that exposes 100+ LLM providers through one OpenAI-compatible API, with budgets and virtual keys in open source.

LiteLLM is an open-source Python SDK and proxy server that exposes 100+ LLM providers through one OpenAI-compatible API. Its core is MIT-licensed, with a paid Enterprise tier for identity, audit, and advanced guardrail features.

Language

Python

License

MIT (core) + commercial enterprise/

Form factor

SDK + proxy server

Best for

Python teams, broad provider access

### Pros

- Broadest provider coverage (100+) in OpenAI format
- Ships as both an SDK and a proxy
- Virtual keys, budgets, and spend tracking in open source
- Semantic caching and an MCP gateway in open source today

### Cons

- Python/Uvicorn runtime; key & budget features require PostgreSQL
- No semantic routing or ensemble per its own routing docs
- SSO/SAML, RBAC, SCIM, and audit logs are paid Enterprise

## Portkey vs LiteLLM: feature comparison

The two converge on routing basics, caching, and an MCP gateway, then diverge on form factor (hosted platform vs Python SDK) and where each draws the free/paid line.

| Feature              | Portkey                                                                                         | LiteLLM                                                                                        |
| -------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Core & runtime       | Open-source TypeScript gateway (Node.js) + a separate hosted control plane                      | Python; SDK + proxy on Uvicorn; key & budget features need PostgreSQL                          |
| Provider coverage    | 1,600+ models across 45+ providers                                                              | 100+ providers in OpenAI format                                                                |
| Routing              | Load balancing, fallbacks, retries, conditional routing (metadata/params/path), circuit breaker | Simple-shuffle, latency, least-busy, rate-limit-aware, cost-based, custom; fallbacks & retries |
| Semantic routing     | — Rule/parameter-based only                                                                     | — Not documented                                                                               |
| Ensemble / fusion    | — Not documented                                                                                | — Not documented                                                                               |
| Caching              | Simple + semantic caching (Redis)                                                               | Exact + semantic (Qdrant, Redis, Valkey, S3, GCS)                                              |
| Guardrails           | 20+ deterministic + LLM-based + partner checks; tiered Basic/Partner/Pro/custom                 | Presidio PII + hooks in OSS; moderation & per-key scoping are Enterprise                       |
| Observability        | Logging, tracing, 21+ metric dashboard, OpenTelemetry-compliant; retention tiered               | Prometheus in OSS, Langfuse, OpenTelemetry, Datadog; some team export Enterprise               |
| Budgets & governance | Model Catalog: cost/token budgets, rate limits, workspaces — granular budgets Enterprise        | Virtual keys, per-key/user/team budgets, spend tracking in OSS (needs PostgreSQL)              |
| MCP gateway          | ✓ Documented (auth + access control for remote MCP)                                             | ✓ In OSS (access control by key/team)                                                          |
| Self-host / VPC      | OSS self-hosts; managed VPC/hybrid is Enterprise                                                | Docker/K8s (Helm beta); no managed-VPC product                                                 |
| Enterprise identity  | RBAC from Production tier; SSO/SAML/OIDC & SCIM Enterprise                                      | Global roles in OSS; SSO/RBAC/SCIM/audit Enterprise                                            |

## Pricing comparison

Both have a free open-source core and paywall advanced governance — but along different lines.

Portkey's gateway is free (MIT); the hosted platform is tiered — a free Developer tier with capped logs, a paid Production tier (from about $49/month) that unlocks RBAC and service accounts, and an Enterprise tier for SSO/SCIM, VPC/hybrid deployment, granular budgets, and custom retention. LiteLLM's core is free (MIT) including budgets and virtual keys; its Enterprise license (custom-priced) adds SSO/SAML, org and team RBAC, SCIM, audit logs, and enterprise guardrails. In short, Portkey gates breadth-of-platform features by tier, while LiteLLM gates enterprise identity and audit.

## When to use Portkey vs LiteLLM

Choose Portkey for breadth and a hosted governance UI; choose LiteLLM for a Python SDK and open-source budgets.

### Choose Portkey if you…

- Want the widest provider catalog behind one API
- Want a hosted observability, analytics, and prompt-management UI
- Are comfortable with tiered pricing and tiered log retention

### Choose LiteLLM if you…

- Want a Python SDK as well as a proxy
- Want OSS budgets and virtual keys without a managed service
- Want semantic caching and an MCP gateway in the open-source build

## Bottom line

Choose Portkey for the widest catalog and a hosted governance UI; choose LiteLLM for a Python SDK plus open-source budgets and virtual keys.

For the broadest provider catalog and a hosted observability-and-governance UI, Portkey is the stronger pick; for a Python SDK with OSS budgets and virtual keys — plus semantic caching and an MCP gateway in the open-source build — LiteLLM fits better. If you're evaluating open-source AI gateways more broadly, AISIX is another option worth a look: a Rust, Apache-2.0 gateway with semantic routing and ensemble built in. See [AISIX vs LiteLLM](https://api7.ai/aisix-vs-litellm).

## Frequently asked questions

### Is Portkey or LiteLLM better?

It depends on your priorities. Portkey offers the widest provider catalog (1,600+ models across 45+ providers) and a polished hosted control plane for observability and governance. LiteLLM is Python-first (an SDK plus a proxy) and keeps more governance in open source, including virtual keys, budgets, semantic caching, and an MCP gateway. Both are MIT-licensed at the core.

### Is Portkey open source?

Partly. Portkey's AI Gateway is open source under the MIT license and is written in TypeScript. The hosted platform that adds observability, prompt management, RBAC, SSO/SCIM, and VPC deployment is commercial and tiered.

### Is LiteLLM free?

The LiteLLM core is free and MIT-licensed, including the proxy with virtual keys, budgets, spend tracking, semantic caching, and an MCP gateway (some require a PostgreSQL database). Enterprise identity — SSO/SAML, org and team RBAC, SCIM, audit logs — and several enterprise guardrails require a paid license.

### Do Portkey or LiteLLM support semantic routing?

Neither routes by the meaning of a request. Portkey offers rule- and parameter-based conditional routing (its "Smart Routing" is rule-based failover), and LiteLLM offers price-, latency-, and load-based strategies. Routing by request meaning, or ensemble (fan-out and synthesize), is not a documented feature of either.

### Can I self-host both Portkey and LiteLLM?

Yes. Portkey's OSS gateway and LiteLLM's proxy can both be self-hosted via Docker/Kubernetes. Note that Portkey's managed VPC/private-cloud (hybrid) deployment is an Enterprise-tier offering, while LiteLLM does not document a packaged managed-VPC product (you run its proxy in your own infrastructure).

### What are some alternatives to Portkey and LiteLLM?

The open-source AI gateway space also includes AISIX, Kong AI Gateway, and OpenRouter, among others. AISIX, for example, is a Rust-native gateway whose entire data plane is Apache-2.0, with semantic routing and ensemble built in. Which one fits depends on whether you want a hosted platform, a Python SDK, or a fully open self-hosted data plane.

## Related comparisons

[AISIX vs LiteLLM](https://api7.ai/aisix-vs-litellm) · [LiteLLM alternatives](https://api7.ai/litellm-alternative) · [All AI gateway comparisons](https://api7.ai/ai-gateway-comparison)

## Ready to get started?

For more information about full API lifecycle management, please contact us to Meet with our API Experts.

[Contact Us](https://api7.ai/contact)
