Skip to content
stack
Get started
Provider · Database

Turso — Ashlr Stack Provider

Turso: Edge SQLite (libSQL). Creates a database in your default org. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Database · PAT
Turso — Edge SQLite (libSQL). Creates a database in your default org.
Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results. 

stack add turso

Or retrieve catalog matches for what you're building via stack recommend: 

stack recommend "serverless postgres for a B2B SaaS"

Auth flow

Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource.

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

Secret slots

stack add turso has these 3 catalog secret slots; verify which values its adapter actually materializes through Phantom:

  • TURSO_DATABASE_URL
  • TURSO_AUTH_TOKEN
  • TURSO_PLATFORM_TOKEN

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

Starter templates that include Turso

Selected template init attempts provider setup by default; add --noProvision to inspect config first:

  • 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?

Use an existing Turso account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource. If you don't have a credential yet, create one at https://app.turso.tech and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Turso credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (TURSO_DATABASE_URL, TURSO_AUTH_TOKEN, TURSO_PLATFORM_TOKEN); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove turso` for local Turso configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Turso credentials through https://app.turso.tech, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.

Outbound