We are at re:Invent 2026Book my merch

LiteLLM

LiteLLM spend, beside your cloud bill.

Cloud Intelligence™ brings in the spend your self-hosted LiteLLM proxy meters on every call, labeled by provider, model, virtual key, team, feature and end customer. Right next to the rest of your AI and cloud spend.

Open-source exporter · Never reads prompts or responses · Polls every 5 minutes

LiteLLM · October
$27,900
anthropic48%openai37%bedrock15%
Tokens
3.2B
Virtual keys
64
Customers
140
By model and provider
claude-sonnet-5 anthropic$9,800
gpt-5 openai$7,100
claude-haiku-4-5 bedrock$3,900
gpt-4.1-mini openai$2,600
text-embedding-3-small openai$600

Trusted by teams routing production LLM traffic through LiteLLM

Akamai
Blumira
Chess.com
Current
OneFootball
Promptly
Recurly
Lusha
Mux

what we import

LiteLLM data, in the dimensions you already use.

Every model call maps to standard Cloud Analytics dimensions, plus labels for provider, model, virtual key, team, feature, customer and tag.

Cloud AnalyticsLiteLLMExample
ProviderDataHub dataset nameLiteLLM
ServiceUpstream model provideranthropic
SKUModel name callers requestclaude-sonnet-5
Plus LiteLLM labels
providermodelvirtual_keyteamfeaturecustomertagcost_basis
Polled every 5 minutes · visible in about 15 minutes

what you can do with it

From gateway logs to a decision

Cost by feature

Slice by feature, customer, virtual key, team or tag.

Feature tag coverage

See how much spend carries a feature label.

Provider vs provider

Tokens and estimated cost per upstream provider, side by side.

GenAI Intelligence

LiteLLM next to your other AI providers in one dashboard.

Budgets and alerts

Guardrails on gateway spend before the provider invoices land.

Allocations

Put LiteLLM spend on teams and customers, by key or label.

live in minutes

Connect LiteLLM in three steps

1

Create an API token.

In your profile, with the DataHubAdmin scope. It's shown only once.

2

Run the exporter.

One small container beside your proxy. Your LiteLLM admin key stays local.

3

Spend in minutes.

Events appear in Cloud Analytics about 15 minutes after export.

Open source, Apache-2.0. Stop the exporter any time.

Start free

Frequently asked
questions

How does the LiteLLM integration work?

You run the open-source litellm-datahub-exporter next to your proxy. It polls your proxy's spend APIs and pushes events to the DataHub API, so we need no network access into your environment.

What do I need before I start?

A self-hosted LiteLLM proxy, version 1.65 or later, with spend logging enabled, a DataHub subscription in your tier, and an API token with the DataHubAdmin scope. On v1.65-era proxies, run the exporter in daily mode.

Is the cost an invoice figure?

No. LiteLLM estimates cost from its model price map and reported tokens, so treat it as showback. Every event carries a cost_basis: estimated label, and you can reconcile with our Anthropic and OpenAI integrations.

How fresh is the data, and how much history can I import?

The exporter polls every five minutes by default, and events show up about 15 minutes after they are sent. Set BACKFILL_DAYS on first run; history is bounded by your spend-log retention and DataHub's two-year window.

How do I attribute spend to features and customers?

Set the OpenAI user parameter for the customer and pass a feature in spend_logs_metadata. Team and virtual key come from the LiteLLM key, and tags come from LiteLLM request tags.

Does the exporter see my prompts?

No. The exporter never reads or transmits prompt or response content, and your LiteLLM admin key never leaves your network.

Connect LiteLLM. Know what every model call costs.

Open source exporter. Spend in minutes.