Skip to content
stack
Get started
Provider · Database

Upstash — Ashlr Stack Provider

Upstash: Serverless Redis + Kafka. Management token stored in Phantom. Wire it into your project with one command via Ashlr Stack.

Database · API key KEY-ONLY · v0.2 adds provisioning
Upstash — Serverless Redis + Kafka. Management token stored in Phantom.
Dashboard ↗

One command

Add Upstash to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom. 

stack add upstash

Or describe what you're building and let Claude pick it up via stack recommend: 

stack recommend "serverless postgres for a B2B SaaS"

Auth flow

Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Generate a management token from the Upstash console.

Secret slots

stack add upstash writes these 1 secret slot into your Phantom vault:

  • UPSTASH_MANAGEMENT_TOKEN

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

  • Supabase — Postgres + Auth + Storage. Full upstream provisioning via the Management API.
  • Neon — Serverless Postgres. Creates a project and pools the connection string.
  • Turso — Edge SQLite (libSQL). Creates a database in your default org.
  • Convex — Reactive backend-as-a-service. Deploy key stored in Phantom.
  • Firebase — Realtime DB + Auth. Service-account JSON stored verbatim in Phantom.

FAQ

Do I need a Upstash account to use it with Stack?

Yes — Stack provisions Upstash on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://console.upstash.com and paste it once.

Where does Stack store my Upstash credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (UPSTASH_MANAGEMENT_TOKEN) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove upstash` to pull the Upstash service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Upstash credentials in their dashboard — https://console.upstash.com — and Stack's next `doctor --fix` will pick up the new values.

Outbound