Deployment Options
Where Revenium runs: shared SaaS by default, an EU data region, and a self-hosted deployment in your own cloud account on the Enterprise tier.
Revenium runs as shared SaaS by default. On the Enterprise tier you can also keep your data in an EU region, or have Revenium build a self-hosted deployment inside your own cloud account.
Shared SaaS
All plans
US-based cloud infrastructure operated by Revenium
EU data region
Enterprise
EU-based cloud infrastructure operated by Revenium
Self-hosted
Enterprise
Your own cloud account (VPC)
Shared SaaS (default)
Every plan starts here. Revenium hosts and operates the platform, and your data is processed and stored in US-based cloud infrastructure.
You run only the integration that sends data to Revenium:
The SDKs or the LiteLLM Proxy callback, inside your own application or proxy.
Any OTLP exporter you point at Revenium, for example from Claude Code or your own agents.
The MCP Server, if you choose to run it locally rather than use the hosted connection.
Most Provider Integrations need nothing running on your side. You enter the provider credentials in Revenium, and Revenium reads the billing data from the provider. The LiteLLM provider integration is the exception: Revenium reads from a LiteLLM proxy that you run.
Revenium operates everything else: the web app, the ingestion and metering endpoints, cost calculation, storage, analytics, and alerts.
EU data region
On Enterprise plans, your data can be processed and stored in the EU instead of the US. The product is the same. Because the platform runs in a separate region, the addresses your integrations send data to differ from the US ones, and the SDKs need a base URL override to point at them. Your Revenium contact provides the addresses for your region.
Self-hosted
On the Enterprise tier, Revenium can build a fully self-hosted Revenium stack inside your own cloud account (VPC), so your usage data stays in your environment. The details are agreed with each customer.
Last updated
Was this helpful?