Database branch provisioning

Neon runs Postgres on a serverless platform where databases branch like code. A Beam agent reads a request for a branch, applies your rules about size and purpose, and provisions or notifies an owner when a request needs approval. Routine branches for testing spin up on their own. A branch touching production data, an unusually large request, or one outside policy routes to an engineer, who keeps the decision. The agent notes what it created and why, so the team sees which branches exist and can retire the ones no longer in use.

Approved query execution

Neon serves Postgres data that applications and teams query for records and reports. A Beam agent reads a request, runs an approved read query, and updates a report or notifies the requester with the result. Reads within the approved set answer on their own. A write, a query that would touch many rows, or one outside the allowed patterns goes to an engineer before it runs. The agent keeps each result tied to the query behind it, so a person can check the logic instead of trusting a number with no visible source or path.

Schema change handling

Neon holds the schema that defines each Postgres database's tables and columns. A Beam agent reads a proposed change, checks it against your rules, and applies a low-risk change or notifies an engineer about anything larger. A new nullable column on a test branch it can handle under policy. A change dropping a column, altering a type, or touching production goes to an engineer, who keeps the judgment. The agent notes what changed and where, so the team follows the history of the schema rather than piecing it together from scattered notes after the fact.