Integration · Database
Neon + OrchestrAI
Catalog exported 2026-09-02 · Neon website
Neon branching from chat: list projects, create a preview branch, delete it with confirmation.
OrchestrAI exposes 6 Neon operations: 4 are low-risk (read-only or low-impact), and 2 create or modify resources and run only after you confirm the plan. 2 of them also carry a step-level approval gate.
What teams use it for
The common workflow is a developer asking for a branch off main in the storefront project so a pull request gets its own copy of the schema and data, then asking for it to be removed once the review is done. Branch creation waits for approval and deletion requires explicit confirmation because it discards the branch's data. Listing projects and branches is read-only and useful for finding stale branches that are still accruing storage. OrchestrAI does not run SQL against a Neon branch and cannot manage compute endpoints or roles, so schema changes and connection strings are still handled through the Neon console or your migration tool.
Every Neon operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
List Managed Platform Deployments |
List deployments, machines, or runtime resources for providers that expose deployment inventory | Low risk | No |
List Managed Platform Projects |
List projects, apps, sites, databases, or clusters for supported PaaS and managed database providers | Low risk | No |
List Neon Branches |
List Neon branches for a serverless Postgres project | Low risk | No |
Validate Managed Platform Connection |
Validate configured credentials for a supported PaaS or managed database provider | Low risk | No |
Create Neon Branch |
Create an approval-gated Neon Postgres branch | Creates resources | Yes |
Delete Neon Branch |
Delete a Neon Postgres branch with approval and explicit confirmation | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
A Neon credential (stored as vercel, fly, railway, netlify, render, neon, supabase, planetscale, upstash, aiven, cockroachdb_cloud).
Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Create a branch called pr-482 from main in the storefront Neon project
- List every branch in the analytics-db project so I can see which ones are older than a month
- Delete the pr-417 branch in storefront, the PR was merged last week
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI create a Neon branch for each pull request?
- It can create a branch on request through neon_create_branch, which is medium risk and waits for your approval before the branch exists. Tying that to a PR event is something you would drive from your CI or by asking in chat.
- What happens when I ask OrchestrAI to delete a Neon branch?
- neon_delete_branch is a high-risk operation that shows the target project and branch and requires explicit confirmation before it runs, since the branch's data is gone once it completes.
- How does OrchestrAI authenticate to Neon?
- You add a Neon credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.