1
Create a project
Midplane Cloud is invite-only for now: get access,
and we’ll email you an invitation. Follow its link to create your account
in its region, such as eu.app.midplane.ai,
verify your address, name your organization and create a project. Its
overview opens on Connect your first database.
2
Run the gateway
Have a connection string at hand for a role the gateway logs in as.
Before you start, in the step, has the SQL for a read-only one
(prepare your database). No database at hand? Try
the sample instead.Create enrollment token and pick where the gateway runs: Your
computer to try Midplane, or A server (Docker) for a team. Agents
anywhere, claude.ai and ChatGPT included, reach a gateway on a server, and
one on your computer at a Midplane URL; at This computer only,
only agents on your computer do. On your computer, the step’s command
runs
midplane setup, which asks for each database’s connection string,
tests it, and names it in Midplane, such as shop: your name for the
database, not its Postgres name. On a server, you put
each connection string in the env file the step shows, and the gateway
tests it as it starts. Either way it then joins your project and starts.
The step shows the gateway’s checks as it reports them, and it’s done when
the gateway enforces the project’s policy. The Gateways page then lists
each database, such as shop · reachable · catalog read: 12 tables
(deploy the gateway).3
Choose what agents may read
A new policy denies everything. Open
shop’s policy from the step and
set the tables agents may read; setting Default access to Read
opens every table the policy doesn’t list, including tables created later.
Review the columns that look like personal data or credentials, then
Review and publish. Back to setup returns to the card.4
5
Try it
Ask your agent one of the questions the step suggests about a table it may
read, such as “How many rows are in
public.customers?”. The card finishes
with that query, and every statement shows up in the Query log.With the sample database
No database at hand? On Run the gateway, an owner or admin can choose the Try with sample data tab. It creates a second project, Sample shop, with the databaseshop and the sample’s policy published: customers’ emails
hashed and phones partly hidden, support ticket bodies untrusted, the API keys
secret, and row changes held for approval. The project you started from stays
as it is, for your own database.
In the sample project, Run the gateway starts the sample’s Postgres with
Docker, then setup on your computer, which runs the gateway on port 7434 so it
can run beside one of your own. Choose Midplane URL to try it from
claude.ai or ChatGPT too. When setup asks for shop’s connection
string, paste the one the step shows (the password is a public example).
Choose what agents may read is already done. When Claude Code signs in,
give it read and write on shop, then ask, in order:
- “List our customers with their emails and plans”: emails come back hashed, phones partly hidden.
- “Summarize the open support tickets”: the agent reads untrusted text and is tainted.
- “Show me the API keys”: refused, since a tainted agent can’t read secret tables.
- “Close ticket 2”: held. Approve it under Approvals.