> ## Documentation Index
> Fetch the complete documentation index at: https://midplane.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Midplane Cloud
> Hosted Midplane: the same open-source engine, plus managed credentials, a searchable audit log, and a dashboard for policy.
Midplane Cloud is the hosted way to run Midplane. You sign up, paste a Postgres URL, and get an MCP endpoint your agent can use — with credentials managed for you, a searchable audit log, and a dashboard for editing policy. No Docker, no YAML, no infrastructure to run.
Cloud is built on the [open-source engine](/docs/cloud-vs-self-host#licensing). You sign in with email and password or Google, and the dashboard is organized around **Projects**, an **Audit log**, **Billing**, and **Settings**.
## Parity with self-host
Cloud runs the same open-source engine self-hosters do, so everything on the [core concepts](/docs/how-it-works) pages — [table access and guardrails](/docs/concepts/table-access), [column masking](/docs/concepts/masking) — applies identically; the dashboard is just a different way to author the same policy model. See [Cloud vs self-host](/docs/cloud-vs-self-host).
## The project model
In Cloud, a **project** is one hosted MCP endpoint that fronts one or more databases. You point your agent at the project's URL; Midplane proxies each call to the right database under that database's access policy.
* A project has a stable URL and lives in your account's [region](#regions-and-data-residency).
* Each project holds one or more databases, each with its own encrypted credential and its own [table access](/docs/concepts/table-access) policy.
* Agents connect over tokenless OAuth by default — no secret to copy — and [machine tokens](/docs/cloud/projects#machine-tokens) are the CI path. Multiple agents can share a project, each scoped to the databases you grant.
See [projects and databases](/docs/cloud/projects) for the full lifecycle.
## Regions and data residency
Right after sign-up you pick a **data region**. The picker suggests one from your location, but you choose — both regions run the same engine and offer the same features. The difference is where your data physically lives:
Data residency in the EU. Hosted in AWS `eu-central-1`.
Hosted in AWS `us-east-2`.
Your region determines where **all** of your data resides — your encrypted credentials (under that region's [AWS KMS key](/docs/cloud/security)), every audit row, the dashboard you sign in to (`eu.app.midplane.ai` or `us.app.midplane.ai`), and the MCP endpoints themselves (`https://eu.midplane.ai/mcp` or `https://us.midplane.ai/mcp`). See [how Cloud secures your data](/docs/cloud/security) for the isolation model.
**The region choice is permanent.** An account cannot be moved between regions after sign-up, and every project inherits its account's region immutably. Pick the region that matches your data residency requirements before you continue.
## What Cloud adds over self-host
Self-host gives you the engine and full control. Cloud adds the operational layer on top of the same engine:
| Capability | What Cloud gives you |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Managed hosting | Projects run the OSS engine on Midplane's infrastructure — no Docker to operate |
| Managed credentials | Database DSNs encrypted with AES-256-GCM under a per-region AWS KMS key; plaintext is never persisted |
| Hosted audit log | The audit trail indexed into Postgres with search, filters, and CSV/JSON export, instead of local SQLite |
| Multi-region & residency | Pick EU or US at signup; your credentials and audit rows stay in that region |
| Dashboard policy editing | Edit [table access](/docs/concepts/table-access), [guardrails](/docs/policies/overview#guardrails), and [column masking](/docs/concepts/masking) in the dashboard, with hot-reload to the running engine |
| Tokenless agent access | Agents connect over OAuth with no secret to copy; [machine tokens](/docs/cloud/projects#machine-tokens) cover CI |
| Roles & SSO | [Owner, admin, and member roles](/docs/cloud/projects#team-roles) gate sensitive actions; shared-org seats today and [SAML SSO](/docs/cloud/plans#single-sign-on) on the [Team plan](#plans-and-pricing) |
**Approval workflows are on the roadmap, not shipping.** A human-in-the-loop queue for risky queries is planned; today policy is declarative — the engine decides allow or deny with no manual gate.
## Plans and pricing
Midplane Cloud has three plans — **Free**, **Pro**, and **Team**. They gate on projects, machine tokens, seats, and audit retention, never on query volume, and the [policy engine](/docs/how-it-works), audit logging, and credential isolation are on every tier. [SAML SSO](/docs/cloud/plans#single-sign-on) is on the Team plan.
Custom needs — BYOK, a dedicated region, longer retention, or SOC 2 / HIPAA artifacts — go through a "talk to us" path. See [plans](/docs/cloud/plans) for current limits and prices, or manage your plan from **Billing** in the dashboard.
## Get started
Create an account, pick a region, and connect a database in minutes.
Paste a Postgres URL and get a hosted MCP endpoint.
Grant access in the dashboard grid or YAML, with hot-reload to the running engine.