Provider · Database

Turso — Ashlr Stack Provider

Turso: Edge SQLite (libSQL). Creates a database in your default org. Wire it into your project with one command via Ashlr Stack.

Database · PAT

Turso — Edge SQLite (libSQL). Creates a database in your default org.

Dashboard ↗

One command

Add Turso 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 turso

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 personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Paste a platform token from https://app.turso.tech/account/api-tokens.

Secret slots

stack add turso writes these 3 secret slots into your Phantom vault:

TURSO_DATABASE_URL
TURSO_AUTH_TOKEN
TURSO_PLATFORM_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.

Starter templates that include Turso

Apply a pre-wired stack with one command:

stack init --template cloudflare-turso-clerk

Supabase — Postgres + Auth + Storage. Full upstream provisioning via the Management API.
Neon — Serverless Postgres. Creates a project and pools the connection string.
Convex — Reactive backend-as-a-service. Deploy key stored in Phantom.
Upstash — Serverless Redis + Kafka. Management token stored in Phantom.
Firebase — Realtime DB + Auth. Service-account JSON stored verbatim in Phantom.

FAQ

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

Yes — Stack provisions Turso on your behalf, but it authenticates as you. Paste a personal access token (PAT) 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://app.turso.tech and paste it once.

Where does Stack store my Turso credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (TURSO_DATABASE_URL, TURSO_AUTH_TOKEN, TURSO_PLATFORM_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 turso` to pull the Turso service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Turso credentials in their dashboard — https://app.turso.tech — and Stack's next `doctor --fix` will pick up the new values.