Turso through Squiid

What Turso is

Turso is SQLite as a service, built on libSQL. Databases are small and cheap enough to create one per customer, which makes per-tenant isolation a schema decision rather than an architecture project. Embedded replicas sync a copy of the database into your application process so reads happen at memory speed and writes go to the primary, and multi-region placement puts data near the people querying it. Databases are created from an API in under a second, so provisioning one during a customer signup flow is a normal thing to do rather than an operations task.

In vibe-coded apps Turso fits two shapes well. The first is a multi-tenant B2B tool where every customer's data should be physically separate and nobody wants to write row-level filters everywhere. The second is an edge-deployed app where a round trip to a single region is the dominant latency and the working set is small. It is SQL you already know, and local development is a file on disk. Costs scale with rows read and written rather than with instance hours, which fits an application whose tenants are mostly idle.

Why connect it through Squiid

Turso is on the Squiid roadmap. When connected, Squiid will provision the organization, hold the database tokens and route access through https://api.squiid.io/v1/turso/... with Authorization: Bearer $SQUIID_API_KEY, with libSQL clients working by base URL swap (gateway convention). Storage, rows read and written, and plan cost will bill at Turso's listed prices on one Squiid invoice. Per-tenant databases multiply credentials quickly, which is exactly the situation where a single key in front of a provider is worth more than a slightly cheaper direct plan.

• One account, one key, one bill, one dashboard. Turso sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Turso credentials. Your code carries SQUIID_API_KEY, so TURSO_DATABASE_URL, TURSO_AUTH_TOKEN, TURSO_ORG never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Turso costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Provisioned libSQL databases with tokens held by Squiid
• Per-tenant database creation from the API
• Embedded replicas for local-speed reads
• Usage and plan on one Squiid invoice
• Turso list pricing, no markup

How to connect Turso

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces TURSO_DATABASE_URL, TURSO_AUTH_TOKEN, TURSO_ORG
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/turso/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Turso charges a plan fee plus storage and rows read or written above the included allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Turso usage, with no markup and no per-request margin.

Turso has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Turso usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: dump the database and restore it into a project in your own Turso account; Turso has no project transfer we are confident of. Squiid never owns your code, your schema or your domain, and the gateway speaks Turso's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Turso through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Turso usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.