Skip to main content
An AI agent sends five statements, and Midplane, drawn as a plane between the agent and Postgres, checks each one against your policy and records it before it runs. Two reads pass through to Postgres: one is answered, the other answered with its emails hashed. Three stop at Midplane: a read of the api_keys table is blocked because the table is not open to agents, a delete waits for your approval, and dropping the orders table is blocked because schema changes are denied. The gateway runs in your network, next to your databases. In Midplane Cloud you write the policy, approve held writes and read the Query log. Agents reach the gateway through Midplane’s relay, which passes their encrypted traffic without reading it, or at a URL of your own. Midplane never sees your query results or connection strings.

Get started

From a new project to your agent’s first query.

How it works

The parts, how agents reach the gateway, and what stays in your network.

Deploy the gateway

On your computer, a server, or a platform.

​
What it enforces

Table access

Denied by default. You open tables one by one, or all for reading.

Masking

Emails hashed, phones shortened, dates generalized, inside the query.

Approvals

A write can wait for a person to approve the exact statement.

Containment

An agent that reads untrusted text loses access to secret tables.
Every statement is also recorded in an audit log on the gateway’s own disk. The gateway is MIT licensed, with its source on GitHub.