Integration · Database
Upstash + OrchestrAI
Catalog exported 2026-09-02 · Upstash website
Create and delete Upstash Redis databases from chat with approval, and list what your Upstash account holds.
OrchestrAI exposes 5 Upstash operations: 3 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
Developers spinning up a new service ask OrchestrAI for an Upstash Redis database in the region closest to their Vercel deployment, and later ask it to remove the database once the service is retired, with creation waiting for approval and deletion requiring explicit confirmation. Listing databases across the account is the usual first step when tidying up unused instances. The operations are limited to Redis: Upstash Kafka, QStash, and Vector are not covered, and OrchestrAI cannot read or write keys inside an Upstash database, so use the Upstash console or a Redis client for that.
Every Upstash 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 |
Validate Managed Platform Connection |
Validate configured credentials for a supported PaaS or managed database provider | Low risk | No |
Create Upstash Redis Database |
Create an approval-gated Upstash Redis database | Creates resources | Yes |
Delete Upstash Redis Database |
Delete an Upstash Redis database 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 Upstash 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 an Upstash Redis database named ratelimit-prod in us-east-1
- List all the Redis databases in our Upstash account
- Delete the Upstash Redis database called demo-cache, the demo is over
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 an Upstash Redis database?
- Yes, upstash_create_redis_database is medium risk and approval-gated, so it states the name and region and waits for your approval before the database is provisioned.
- Does OrchestrAI support Upstash Kafka or QStash?
- No, Current coverage is Redis databases only: create, delete, list, and validate the connection.
- How does OrchestrAI authenticate to Upstash?
- You add a Upstash 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.