Google Cloud · Cloud service
Google Cloud SQL with OrchestrAI
Catalog exported 2026-09-02
Create Cloud SQL instances and databases from chat, with deletion gated behind a typed risk phrase.
OrchestrAI exposes 3 Cloud SQL operations: 2 create or modify resources and run only after you confirm the plan, and 1 is destructive and requires a typed risk phrase. 1 of them also carries a step-level approval gate.
What teams use it for
Startups use OrchestrAI to provision a Postgres or MySQL Cloud SQL instance for a new environment and add the application database to it in one conversation. The instance lands in the managed-resource ledger, so the team can later ask what was created and whether anything changed. There is no list, backup, or modify operation for Cloud SQL yet, so resizing an instance or restoring from a backup still happens in the console.
Every Cloud SQL operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create Cloud SQL Database |
Create a database within a Cloud SQL instance | Creates resources | No |
Create Cloud SQL Instance |
Create a GCP Cloud SQL database instance | Creates resources | No |
Delete Cloud SQL Instance |
Delete a GCP Cloud SQL database instance | Destructive | 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.
Prompts that work
- Create a Postgres 16 Cloud SQL instance called orders-db in us-east1 with a db-custom-2-8192 tier
- Create a database named orders on the orders-db instance
- Delete the Cloud SQL instance scratch-test in us-central1
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
- What happens when I ask OrchestrAI to delete a Cloud SQL instance?
- Instance deletion is a critical operation. OrchestrAI shows the plan and blast radius, then requires you to type a risk phrase before it proceeds, because the data on the instance is lost.
- Does OrchestrAI need long-lived GCP keys to manage Cloud SQL?
- No. Access to the GCP project comes from a role you grant plus a short-lived federated token minted for each run, so there are no cloud keys to upload or rotate.
- Which Cloud SQL operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete Cloud SQL Instance. It is classed destructive and cannot run without a typed risk phrase.
Other Google Cloud services
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.