fix(docs): make Lago Cloud a reference page and remove funnel pages

docs.json

@@ -74,10 +74,6 @@
             "group": "Get started",
             "pages": [
               "guide/lago-cloud",
-              "guide/lago-cloud/self-serve-billing",
-              "guide/lago-cloud/contract-billing",
-              "guide/lago-cloud/finance-workflow",
-              "guide/ai-agents/for-agents",
               {
                 "group": "Lago Self-hosted",
                 "pages": [
@@ -300,6 +296,7 @@
           {
             "group": "AI Agents and MCP",
             "pages": [
+              "guide/ai-agents/for-agents",
               {
                 "group": "Lago Agent SDK",
                 "pages": [
@@ -1254,6 +1251,9 @@
     { "source": "/docs/integrations/entitlements/oso", "destination": "/integrations/entitlements/osohq" },
     { "source": "/integrations/overview", "destination": "/integrations/introduction" },
     { "source": "/guide/self-hosted", "destination": "/guide/lago-self-hosted/overview" },
+    { "source": "/guide/lago-cloud/self-serve-billing", "destination": "/guide/introduction/welcome-to-lago" },
+    { "source": "/guide/lago-cloud/contract-billing", "destination": "/guide/plans/commitment" },
+    { "source": "/guide/lago-cloud/finance-workflow", "destination": "/guide/invoicing/export" },
     { "source": "/guide/payments/overview", "destination": "/guide/payments/payment-providers" },
     { "source": "/guide/credit-notes.mdx", "destination": "/guide/invoicing/credit-notes/overview" },
     { "source": "/guide/analytics/gross-revenue", "destination": "/guide/analytics/revenue/revenue-streams" },

docs/llms.txt

@@ -4,9 +4,6 @@
 
 - [Welcome to Lago](/guide/introduction/welcome-to-lago.md)
 - [Lago Cloud](/guide/lago-cloud.md)
-- [Self-serve billing](/guide/lago-cloud/self-serve-billing.md)
-- [Contract billing](/guide/lago-cloud/contract-billing.md)
-- [Finance invoice workflow](/guide/lago-cloud/finance-workflow.md)
 - [Ingest usage events](/guide/events/ingesting-usage.md)
 - [Billable metric aggregation](/guide/billable-metrics/aggregation-types/overview.md)
 - [Plan model](/guide/plans/plan-model.md)

faq/about-lago.mdx

@@ -4,7 +4,7 @@ title: "About Lago"
 
 ## 1. What is Lago?
 
-[Lago](https://getlago.com/) is a billing platform for subscriptions, usage-based pricing, invoicing, and connected payments. Teams can use [Lago Cloud](/guide/lago-cloud), the hosted Premium deployment, or [self-host Lago](/guide/lago-self-hosted/overview). The deployment choice does not determine whether Lago can support self-serve or negotiated billing; start with the [self-serve](/guide/lago-cloud/self-serve-billing) and [contract](/guide/lago-cloud/contract-billing) examples for those workflows.
+[Lago](https://getlago.com/) is a billing platform for subscriptions, usage-based pricing, invoicing, and connected payments. Teams can use [Lago Cloud](/guide/lago-cloud), the hosted Premium deployment, or [self-host Lago](/guide/lago-self-hosted/overview).
 
 <iframe
   src="https://ghbtns.com/github-btn.html?user=getlago&amp;repo=lago&amp;type=star&amp;count=true&amp;size=large"

faq/pricing.mdx

@@ -23,5 +23,3 @@ Please reach out via [Slack](https://getlago.com/slack) or hello@getlago.com for
 ## 4. How can I evaluate Lago Premium?
 
 [Contact Lago](https://getlago.com/book-a-demo) to discuss access to Lago Cloud and an evaluation of your pricing and billing workflow. Ask the team what trial or proof-of-concept options are available for your use case.
-
-Before a proof of concept, use the [self-serve](/guide/lago-cloud/self-serve-billing), [contract](/guide/lago-cloud/contract-billing), or [Finance](/guide/lago-cloud/finance-workflow) example to define the expected invoice and integration checks. The open-source self-hosted edition is available for teams who want to test that deployment.

guide/ai-agents/for-agents.mdx

@@ -18,22 +18,7 @@ Help me design and implement a billing integration. Ask before live access.
 
 Describe what your customers pay for. Your agent can use public documentation to propose the customer identifiers, billable metrics, plans, and subscription lifecycle before connecting to a live environment.
 
-## Get a first result
-
-Ask your agent to calculate an expected bill before writing the integration. This example follows one customer action through usage, pricing, included credits, and overage, using fictional prices:
-
-| Step | Example result |
-| --- | --- |
-| Customer agreement | \$99 subscription with \$10 of included AI usage |
-| Credit remaining before the action | \$0.20, after \$9.80 has already been used |
-| New usage charge | $0.37 from input and output token records |
-| Identical event replay | No additional charge when `transaction_id` and `timestamp` match |
-| Credit applied to this action | $0.20 |
-| Overage from this action | $0.17 |
-
-This is an offline calculation, not proof that your environment is configured correctly. Live validation checks actual Lago results separately. Amounts exclude tax and payment processing. Automated monthly wallet renewal is edition-dependent.
-
-### Apply it to your product
+## Model your pricing
 
 Give the agent a product description or pricing page:
 
@@ -49,7 +34,7 @@ Other starting points:
 - **Prepaid credits:** "Help me model prepaid usage, wallet consumption, and what my application should do when credit runs out."
 - **Existing billing:** "Help me add Lago usage billing to my existing architecture. Identify which system owns subscriptions, invoicing, and payments."
 
-### Implement in your application
+## Implement in your application
 
 Open the application repository and ask:
 
@@ -78,43 +63,9 @@ Choose the interface your agent supports. The API, CLI, and MCP work independent
 
 Start with the [API reference](/api-reference/intro) and [developer resources](/developers) for supported SDKs. Give your agent the [complete OpenAPI specification](https://swagger.getlago.com/openapi.yaml) for exact fields. Keep credentials server-side and confirm the US, EU, or self-hosted API URL before sending requests.
 
-### Use the CLI
-
-Install with Homebrew on macOS or Linux:
-
-```bash
-brew install getlago/tap/lago
-```
-
-For Go installation and Windows releases, see the [CLI setup guide](/guide/lago-cli/overview).
-
-Inspect the installed version and available commands before building a script:
-
-```bash
-lago version
-lago --help
-```
-
-Follow the [configuration guide](/guide/lago-cli/overview) to select the environment and store credentials. After authorizing live access, verify the resolved target:
+### Use the CLI or the product MCP
 
-```bash
-lago whoami --output json
-lago doctor --output json
-```
-
-These commands contact the configured Lago environment. Review each command's help for JSON output and dry-run support. A CLI mode named `test` is not an isolated Lago sandbox.
-
-### Connect the product MCP
-
-Follow the [MCP server setup guide](/guide/ai-agents/mcp-server) for the Docker configuration. Set `LAGO_API_URL` explicitly to the US, EU, or self-hosted API endpoint and provide `LAGO_API_KEY` through your client's secret configuration.
-
-Start with an authorized read, such as:
-
-```text
-List the invoices for this customer. Do not change billing data.
-```
-
-Available operations are listed in the [Lago Agent Toolkit](https://github.com/getlago/lago-agent-toolkit). The product MCP accesses live billing data; it is separate from the public documentation MCP.
+The [Lago CLI](/guide/lago-cli/overview) covers terminal workflows, diagnostics, and scripts. The [product MCP server](/guide/ai-agents/mcp-server) gives an MCP client access to live billing data. Both contact a real Lago organization: set the US, EU, or self-hosted API URL explicitly and keep the API key in your client's secret configuration. Start with a read-only request, such as listing a customer's invoices.
 
 ## Give your agent the documentation
 
@@ -131,7 +82,7 @@ Configure the documentation MCP as a remote HTTP server in a compatible client.
 
 Keep API keys out of prompts, source control, and browser code. Confirm the organization, API URL, affected records, and expected billing impact before live work. Ask your agent to show the proposed changes before executing financial or destructive operations.
 
-Use an isolated self-hosted instance for synthetic demos. Lago has no built-in sandbox, and calling a Cloud organization "test" does not isolate it. Follow the [integration testing guide](/guide/integration-testing) when validating your own application.
+Lago has no built-in sandbox, and naming an organization "test" does not isolate it. Run synthetic tests in a separate Lago Cloud organization or an isolated self-hosted instance. Follow the [integration testing guide](/guide/integration-testing) when validating your own application.
 
 ## Optional: install the Lago plugin
 
@@ -169,8 +120,3 @@ The plugin supports Claude Code and Codex. Exploring its offline example and des
     ```
   </Tab>
 </Tabs>
-
-The plugin is distributed from Lago's repository. This installation path does not imply an official OpenAI or Anthropic marketplace listing.
-
-
-[Explore Lago's tools for AI agents](https://getlago.com/for-agents)

guide/introduction/welcome-to-lago.mdx

@@ -5,8 +5,6 @@ description: "Get started with Lago Cloud for subscriptions, usage billing, invo
 
 Lago calculates subscription and usage charges, generates invoices, and connects billing to payment providers and finance tools. [Lago Cloud](/guide/lago-cloud) is the hosted option: Lago runs and updates the billing service while your team configures its pricing and connects customer and usage data. You can also [self-host Lago](/guide/lago-self-hosted/overview) when your team needs to operate the deployment.
 
-Start with a [self-serve subscription and usage example](/guide/lago-cloud/self-serve-billing), a [negotiated contract example](/guide/lago-cloud/contract-billing), or the [Finance workflow](/guide/lago-cloud/finance-workflow). Each follows the charges through to an invoice.
-
 ## Five-step billing workflow
 
 ### 1. Usage ingestion

guide/invoicing/overview.mdx

@@ -27,5 +27,3 @@ You can [download invoices](/guide/invoicing/download-invoices) or use the
 template.
 
 For payment collection, connect a [native payment provider](/guide/payments/payment-providers). For accounting, compare the [NetSuite](/integrations/accounting/netsuite) and [Xero](/integrations/accounting/xero) integrations, which are available on request, with the [community-maintained QuickBooks integration](/integrations/accounting/quickbooks). You can also use invoice webhooks and the API for a custom workflow.
-
-If you are evaluating the full process, follow the [Finance invoice workflow](/guide/lago-cloud/finance-workflow) from invoice review through payment status, export, and accounting handoff.

guide/lago-cloud.mdx

@@ -1,32 +1,88 @@
 ---
 title: "Lago Cloud"
-description: "Run subscriptions, usage billing, invoicing, and connected payments on Lago's hosted Premium deployment."
+description: "Lago Cloud is the fully managed Lago billing platform, hosted in the US or EU. Regions, API URLs, usage ingestion, security, and how to start."
+keywords: ["Lago Cloud", "hosted billing", "managed usage-based billing", "Lago EU region"]
 ---
 
-Lago Cloud is the hosted deployment of Lago Premium. Lago runs, maintains, and updates the billing service. Your team configures what customers pay for, connects its product data, and chooses the payment and finance systems that fit its workflow. [Self-hosting](/guide/lago-self-hosted/overview) is also available when your team needs to operate the service itself.
+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.
 
-## What your team owns
+To operate Lago on your own infrastructure instead, see [self-hosting](/guide/lago-self-hosted/overview).
 
-| Part of the workflow | In Lago Cloud |
+## Regions and endpoints
+
+Lago Cloud runs in two regions. Your organization lives in one of them, and API requests must target that region.
+
+| Region | API base URL |
 | --- | --- |
-| Hosting and application updates | Lago operates the hosted billing service and delivers updates. |
-| Pricing and customer data | Your team configures plans, billable metrics, customers, and subscriptions in Lago. Your application or an integration sends the customer and usage data needed for billing. |
-| Payment processing | Lago can trigger collection and update invoice status through [supported payment providers](/guide/payments/payment-providers). Your chosen provider processes the payment. |
-| Finance systems | Your team selects and configures the accounting integration or export it needs. Lago has documented [NetSuite](/integrations/accounting/netsuite) and [Xero](/integrations/accounting/xero) integrations available on request; [QuickBooks](/integrations/accounting/quickbooks) uses a community-maintained n8n workflow. |
+| US | `https://api.getlago.com/api/v1` |
+| EU | `https://api.eu.getlago.com/api/v1` |
+
+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](/api-reference/intro) and [developer resources](/developers) for each SDK.
+
+## What Lago runs and what you configure
+
+| Area | Lago Cloud |
+| --- | --- |
+| Hosting, scaling, and upgrades | Lago operates the application, databases, and event pipeline, and ships updates. |
+| Pricing and customer data | Your team configures [billable metrics](/guide/billable-metrics/create-billable-metrics), [plans](/guide/plans/overview), customers, and subscriptions. Your application sends customer and usage data. |
+| Payment processing | Lago triggers collection and tracks invoice status through [payment providers](/guide/payments/payment-providers). The provider processes the payment. |
+| Finance systems | Your team connects an accounting integration or uses [invoice exports](/guide/invoicing/export). [NetSuite](/integrations/accounting/netsuite) and [Xero](/integrations/accounting/xero) are available on request. |
+
+## 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](/guide/events/usage-performances) for benchmarks and connector throughput.
+
+| Connector | Public internet | Private connectivity |
+| --- | --- | --- |
+| [REST API](/guide/events/ingesting-usage) | Yes | No |
+| Kafka / Redpanda | Yes | Yes, through VPC peering |
+| Amazon Kinesis | Yes | No |
+| Amazon S3 | Yes | No |
+
+Event data is retained for 90 days after a subscription terminates. Contact the Lago team to set up VPC peering or a [metering source](/guide/events/metering-source) connector.
+
+## Security and compliance
+
+- **SOC 2 Type 2** covers the hosted version. Email hello@getlago.com to request the report. See [SOC 2](/guide/security/soc).
+- **Infrastructure** runs on AWS with Kubernetes on managed services. Data is encrypted at rest and in transit, with keys managed in AWS KMS. GuardDuty monitors the environment.
+- **Access control:** [API keys](/guide/security/api-keys), [SSO](/guide/security/sso), [role-based access control](/guide/security/rbac), and [audit logs](/guide/security/audit-logs). SSO and RBAC are premium add-ons.
+- **Trust resources:** [status page](https://status.getlago.com/), [security portal](https://security.getlago.com), [Cloud terms of service](https://getlago.com/company/terms-of-service-cloud), and [privacy](/privacy).
+
+## Features and plans
+
+Lago Cloud includes the open-source billing engine plus Premium features such as [invoice previews](/guide/invoicing/previews). Some capabilities, like the AI assistants and certain integrations, are add-ons available on request. Check the [pricing page](https://getlago.com/pricing) for the current feature list.
 
-Cloud removes the work of running Lago's application infrastructure. It does not remove the work of defining your billing rules or connecting Lago to your product, payment provider, and accounting system.
+## Get started
 
-## Choose a workflow to evaluate
+<Steps>
+  <Step title="Request an account">
+    Cloud accounts are set up by [Lago's team](https://getlago.com/book-a-demo). Confirm the region, features, and integrations you need.
+  </Step>
+  <Step title="Create an API key">
+    Sign in to the web app for your region and [create an API key](/guide/security/api-keys). Keep it server-side.
+  </Step>
+  <Step title="Model your pricing">
+    Create a [billable metric](/guide/billable-metrics/create-billable-metrics), a [plan](/guide/plans/overview), and a [customer](/guide/customers/customer-management), then [assign the plan](/guide/subscriptions/assign-plan).
+  </Step>
+  <Step title="Send usage">
+    [Ingest events](/guide/events/ingesting-usage) from your application and check them against the subscription.
+  </Step>
+  <Step title="Connect payments">
+    Connect a [payment provider](/guide/payments/payment-providers) to collect invoices.
+  </Step>
+</Steps>
 
-- [Self-serve subscription plus usage](/guide/lago-cloud/self-serve-billing): configure a recurring fee and metered charge, connect Stripe Payments, and check the resulting invoice.
-- [Negotiated contract plus usage](/guide/lago-cloud/contract-billing): set customer-specific terms and a minimum commitment, then inspect the invoice and true-up.
-- [Finance invoice workflow](/guide/lago-cloud/finance-workflow): review invoices and payments, export data, and connect accounting and AI analysis.
+Lago Cloud has no built-in sandbox inside an organization. Use a separate organization for tests and follow the [integration testing guide](/guide/integration-testing).
 
-## Start with Lago Cloud
+## Cloud or self-hosted
 
-1. [Contact Lago's sales team](https://getlago.com/book-a-demo) for a Cloud account. Cloud access currently runs through sales. Confirm the edition, region, integrations, and support package you need; [pricing](https://getlago.com/pricing) lists Premium features and deployment options.
-2. [Create a billable metric](/guide/billable-metrics/create-billable-metrics), [plan](/guide/plans/overview), and [customer](/guide/customers/customer-management). Assign the plan to the customer and, if applicable, [send usage events](/guide/events/ingesting-usage).
-3. [Connect a payment provider](/guide/payments/payment-providers) and decide how the customer will receive a checkout or payment link. A payment provider is still required to process payments.
-4. Inspect an [invoice preview](/guide/invoicing/previews) before live billing, then verify the finalized invoice, payment status, and finance export against your expected charges. Invoice previews are a Premium capability; they use configured billing data, not a free-form mock-invoice generator.
+| | Lago Cloud | Self-hosted |
+| --- | --- | --- |
+| Who operates it | Lago | Your team |
+| Upgrades | Delivered by Lago | You run [updates](/guide/lago-self-hosted/update-instance) |
+| Event pipeline | Managed ClickHouse and Kafka | You run ClickHouse and Redpanda, or Postgres only |
+| SOC 2 Type 2 | Covers the hosted service | Your infrastructure, your controls |
+| Network | Public internet, or VPC peering for Kafka | Fully inside your network |
+| Editions | Premium | Open source (free) or Premium |
 
-Lago does not provide a built-in sandbox within a Cloud account. Use a separate organization for integration testing and follow the [testing guide](/guide/integration-testing) before sending synthetic events or real payment requests. For a deployment comparison, include the Lago plan, provider fees, and integration work; self-hosting also adds infrastructure, upgrades, monitoring, and incident response.
+See the [deployment FAQ](/faq/deployment) for more detail.