> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/plans-and-contact/deployment-options.md).

# 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.

You choose where your Revenium data is hosted: Revenium's shared SaaS in the US, an EU data region, or a self-hosted deployment inside your own cloud account. Shared SaaS is the default. The EU region and self-hosting are Enterprise features. See [revenium.ai/pricing](https://revenium.ai/pricing) for plans.

| Option             | Available on | Where your data is stored                          |
| ------------------ | ------------ | -------------------------------------------------- |
| **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](/integrations/sdk-setup.md) or the [LiteLLM Proxy callback](/integrations/litellm-proxy-setup.md), inside your own application or proxy.
* Any [OTLP exporter](/integrations/otlp-integration.md) you point at Revenium, for example from Claude Code or your own agents.
* The [MCP Server](/integrations/mcp-server.md), if you choose to run it locally rather than use the hosted connection.

Most [Provider Integrations](/integrations/provider-integrations.md) 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.

{% hint style="info" %}
To discuss a self-hosted or EU deployment, including which clouds and locations are available, see [Talk to Sales](/plans-and-contact/talk-to-sales.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revenium.io/plans-and-contact/deployment-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.