Skip to main content
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. 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 pages — table access and guardrails, column masking — applies identically; the dashboard is just a different way to author the same policy model. See 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.
  • Each project holds one or more databases, each with its own encrypted credential and its own table access policy.
  • Agents connect over tokenless OAuth by default — no secret to copy — and machine tokens are the CI path. Multiple agents can share a project, each scoped to the databases you grant.
See projects and databases 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:

Europe

Data residency in the EU. Hosted in AWS eu-central-1.

United States

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), 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 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:
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, audit logging, and credential isolation are on every tier. SAML SSO 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 for current limits and prices, or manage your plan from Billing in the dashboard.

​
Get started

Sign up

Create an account, pick a region, and connect a database in minutes.

Create a project

Paste a Postgres URL and get a hosted MCP endpoint.

Write a policy

Grant access in the dashboard grid or YAML, with hot-reload to the running engine.