Serverless libSQL
SQLite-compatible, edge-friendly, with HTTP and WebSocket drivers. Free tier, the same SQL you already know, cloud or self-host with SpinDB.
Tables
- users
- events
- orders
- sessions
| id | name | created_at |
|---|---|---|
| 1247 | signup | 2026-03-12 14:21 |
| 1246 | purchase | 2026-03-12 14:08 |
| 1245 | login | 2026-03-12 13:55 |
| 1244 | signup | 2026-03-12 13:44 |
| 1243 | purchase | 2026-03-12 13:30 |
Where to run it
Cloud, desktop, or self-host
One database, three places it can live. Pick the speed you want and move between them when you outgrow it.
What you get
Production features, free tier included
Every libSQL database ships with the same primitives: TLS, web console, hibernation, and a real dashboard. No tiered features hidden behind a sales call.
Web IDE
Query console in the dashboard, no extra client to install.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Optional keep-alive add-on prevents hibernation.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
HTTPS access
HTTP-native engines reachable over port 443.
Serverless driver
Upstash REST or PlanetScale serverless drivers supported.
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled point-in-time backups with one-click restore.
Quick start
Connect with any libSQL client
Edge and serverless apps that want SQLite semantics, multi-region replication patterns, and projects already on Turso that want a portable alternative.
- Spin up a libSQL for an edge or Cloudflare Workers app via the HTTP driver
- Run SQLite-compatible schema with an HTTP-friendly client where the file-based mode does not fit
- Per-tenant libSQL databases that hibernate between bursts
- Local-first development on Layerbase Desktop, deploy the same schema to cloud
- Self-host on your own hardware with SpinDB
const db = createClient({ url: 'https://your-host.cloud.layerbase.dev', authToken: process.env.LIBSQL_AUTH_TOKEN })Sibling engine
Want the upstream SQLite specifically?
If you do not need the HTTP or WebSocket driver and want the bare upstream engine, point your client at SQLite on Layerbase instead. Both run on the same platform.
Questions
Common libSQL questions
libSQL vs upstream SQLite on Layerbase?+
libSQL is the Turso-backed fork that adds HTTP and WebSocket drivers and remote-friendly features. Pick libSQL when you want edge-runtime access; pick SQLite for the bare upstream engine.
Is it Turso-compatible?+
Yes. libSQL on Layerbase speaks the same protocol and ships with the same client library Turso users already have.
How does the HTTP driver work?+
The libSQL client wraps SQL queries in HTTPS calls so edge and serverless runtimes (Cloudflare Workers, Vercel Edge) can talk to a libSQL endpoint without a TCP socket.
Free tier limits?+
libSQL is in the Free tier. Your database hibernates after an hour of inactivity and wakes on the next connection; upgrade if you need always-on or larger storage.
Can I run libSQL locally?+
Yes. SpinDB and Layerbase Desktop both run libSQL with the same install workflow.