# Turso alternative on real Postgres, not SQLite

> Turso runs libSQL, a SQLite-compatible engine, not Postgres. Scribase is Postgres 17 per project with row level security, joins, extensions, auth, storage and realtime included.

Source: https://scribase.com/turso-alternative

Turso's own docs describe it as "fully backwards compatible with SQLite" via libSQL — a genuinely different engine and wire protocol from Postgres, read through Turso's own SDKs rather than a standard postgres:// connection string. If the reason to look at Turso was edge-replica speed, Scribase does not try to match that; if the reason was a free tier with a real relational database and auth/storage already attached, that is the comparison this page makes.

## Turso and Scribase, side by side

_Turso facts read on turso.tech/pricing and docs.turso.tech 2026-11-18_

|  | Turso | Scribase |
| --- | --- | --- |
| Database engine | libSQL (SQLite-compatible), read via Turso's SDKs | Postgres 17, read via standard Postgres clients and SQL |
| Free plan | 100 databases, 5 GB storage, 500 million rows read/month, 10 million rows written/month | 1 project free with no time limit (0.5 GB database, 1 GB files, no card) |
| Entry paid plan | Developer, $4.99/month | Hobby $5 a project a month |
| Row level security | No equivalent built in | Postgres row level security, enforced by default on new tables |
| Joins and SQL extensions | SQLite dialect, no pgvector/pg_cron/pgmq-style extensions | Full Postgres SQL plus pgvector, pg_cron, pgmq and more |
| Auth, Storage, Realtime | Not included; a database product only | Included in every project |

## Sources

- [Turso: Pricing](https://turso.tech/pricing)
- [Turso: Introduction](https://docs.turso.tech/introduction)
- [Scribase pricing](https://scribase.com/pricing)

## When Turso is still the right call

- You want SQLite semantics with edge replicas close to users for read-heavy, latency-sensitive workloads.
- Your app is already built against SQLite's dialect and you do not want to adopt Postgres's type system or SQL extensions.
- You need the very generous free row-read allowance (500 million rows/month) for a read-heavy workload that fits in 5 GB.

## Sources

- [Turso: Pricing](https://turso.tech/pricing)

## Moving from Turso

There is no Turso importer, and libSQL's wire protocol is not Postgres, so scribase-migrate's generic Postgres import cannot connect to it directly. A move is a real rewrite: export rows (Turso's CLI can dump a database), adjust SQLite-specific syntax (INTEGER PRIMARY KEY AUTOINCREMENT, no native boolean/array types) for Postgres, and reload through a migration.

1. **Create the project** — One command creates Postgres, Auth and Storage and writes the URL and anon key into your .env file.

```sh
npx scribase init
```

2. **Translate the schema** — Rewrite table definitions for Postgres types; most ORMs that already target SQLite (Drizzle, Prisma) can point the same model at Postgres with a dialect change.

3. **Export and reload the data** — Dump rows with the Turso CLI, then load them through a migration; row level security decides who can read them afterward.

## FAQ

**Is Turso Postgres-compatible?**

No. Turso runs libSQL, a SQLite-compatible fork, reached through Turso's own SDKs rather than a standard Postgres connection string. It is a different engine and wire protocol from Postgres.

**Can I migrate a Turso database to Scribase in one command?**

No. scribase-migrate's generic Postgres import needs a Postgres connection, which libSQL does not speak. Moving means exporting rows and rewriting the schema for Postgres by hand.

**How do the free plans compare?**

Turso's free plan gives 100 databases, 5 GB of storage and 500 million row reads a month. Scribase's free plan is 1 project free with no time limit, with 0.5 GB database and 1 GB of files, and includes auth, storage and realtime; Turso's free plan is a database product only.

**Does Scribase have edge replicas like Turso?**

No. Scribase runs in one region today. Turso's edge-replica model for low-latency reads near users is a real reason to stay on it.

## Related

- [Supabase alternative](https://scribase.com/supabase-alternative)
- [PocketBase alternative](https://scribase.com/pocketbase-alternative)
- [Backend as a service compared](https://scribase.com/backend-as-a-service)
- [Postgres extensions](https://scribase.com/extensions)
- [Pricing](https://scribase.com/pricing)