Database
Turso
Build with a SQLite-compatible database and options for local data synchronization.
Sources checked
Our recommendation
When to choose it
Choose Turso when SQLite compatibility and local data behavior are part of your architecture. Use PostgreSQL for a conventional relational server backend.
A good fit for
- SQLite-compatible applications
- Projects with a deliberate local-first data design
Choose something else when
Prefer Neon when your backend or SQL tooling expects PostgreSQL.
Watch out for
- SQLite-compatible does not mean interchangeable with PostgreSQL SQL, extensions or drivers.
- Local synchronization needs a plan for authorization, conflicts and reconnecting.
How costs work
Hosted database plans and usage
Separate the local engine from hosted service billing, and check current limits for your deployment.
Check current official terms and pricing ↗This is a pricing model, not a monthly quote. Check your region, intended usage and current plan before buying.
What connects to it
- SQLite-compatible tooling
- Local and hosted database workflows
These are technical connections you can configure. Selecting a card creates no accounts or resources.
Compare the alternatives
Learn the boundary before you connect it
Lessons open through your account and the kits you own.
Check the evidence
Feature sources were reviewed on 4 Oct 2026. Plans and availability can change.
- Database model ↗
SQLite compatibility and local synchronization capabilities.
- Hosted plans ↗
Hosted service pricing and plan boundaries.