---
title: Cloud
description: Tale Cloud is the managed edition. Tale runs the stack, your data is pinned to Switzerland or the EU, and your team's only operational task is using the product.
kind: index
---

Tale Cloud is the managed edition. Tale operates the infrastructure, your data is pinned to Switzerland or the EU, and your team's only operational concern is using the product. The codebase is identical to self-hosted; the difference is who keeps it running.

This section covers the concerns specific to running on Cloud — onboarding, regions and data residency, billing, the trust posture you can hand an auditor, and how to migrate to self-hosted if your needs change. Every other feature reference lives one tab over under Platform, identical regardless of edition.

## Pages in this section

**[Onboarding](/cloud/onboarding)** — sign up, verify the org, configure the first model provider, publish your first agent. About an hour for an Editor.

**[Data residency](/cloud/data-residency)** — where your data lives, which sub-processors touch it, and what changes when you switch region.

**[Billing](/cloud/billing)** — plans, seats, metered components, budgets, and where to find the invoice.

**[Trust and compliance](/cloud/trust-and-compliance)** — the certifications Tale ships with, the shared-responsibility split, and what evidence you can hand an auditor.

**[Migrate to self-hosted](/cloud/migrate-to-self-hosted)** — export from Cloud, stand up a self-hosted instance, import.

## Where this fits

Cloud is the convenient front door; Platform is where the real work lives. Once your org is signed in and the first agent is running, your team spends nearly all their time in Platform pages, not here. The one page worth re-reading whenever your operational posture changes is [Data residency](/cloud/data-residency) — it surfaces every external system your data crosses.
