Skip to main content
Lago Cloud is the fully managed deployment of Lago Premium. Lago runs the application, the database, the ClickHouse and Kafka event pipeline, upgrades, and monitoring. Your team configures pricing, sends usage, and connects its payment and finance tools through the same API, SDKs, and app used everywhere in these docs. To operate Lago on your own infrastructure instead, see self-hosting.

​
Regions and endpoints

Lago Cloud runs in two regions. Your organization lives in one of them, and API requests must target that region. SDKs connect to the US region by default. Set the API URL for EU organizations. The CLI takes --region us or --region eu. See the API reference and developer resources for each SDK.

​
What Lago runs and what you configure

​
Usage ingestion

Lago Cloud manages the high-volume pipeline: Kafka or Redpanda for streaming, ClickHouse for storage and aggregation. You send events. Lago’s load tests measure this architecture at 1 to 3 million events per second sustained. See performance and optimization for benchmarks and connector throughput. Event data is retained for 90 days after a subscription terminates. Contact the Lago team to set up VPC peering or a metering source connector.

​
Security and compliance

​
Features and plans

Lago Cloud includes the open-source billing engine plus Premium features such as invoice previews. Some capabilities, like the AI assistants and certain integrations, are add-ons available on request. Check the pricing page for the current feature list.

​
Get started

1

Request an account

Cloud accounts are set up by Lago’s team. Confirm the region, features, and integrations you need.
2

Create an API key

Sign in to the web app for your region and create an API key. Keep it server-side.
3

Model your pricing

Create a billable metric, a plan, and a customer, then assign the plan.
4

Send usage

Ingest events from your application and check them against the subscription.
5

Connect payments

Connect a payment provider to collect invoices.
Lago Cloud has no built-in sandbox inside an organization. Use a separate organization for tests and follow the integration testing guide.

​
Cloud or self-hosted

See the deployment FAQ for more detail.