# Turso

Canonical: https://inetgeek.com/databases/turso/

Managed SQLite built on libSQL, priced per database with rows read and written as the metered units.

## Who it suits

Applications that want a database per tenant or per user — 100 databases on the free plan and unlimited above it make that a shape you can actually build.

Consider something else if It is SQLite, not Postgres: the metered units are rows read and written rather than compute, and the extension ecosystem you may be relying on is not there.

## Adoption signals

- Open source: tursodatabase/turso — 24,247 stars, 1,336 forks (GitHub, checked 2026-09-12)

## iScore

69 / 100 (80% interval 65–72), rank 5 of 14 in databases — interval overlaps the next rank, so this is an ordering, not a finding.

inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known.
Read this score with care:
- Capacity and limits is thin: 3 of 7 criteria are scored, so it sits near the category middle with a wide interval (41–54). Read the interval, not the point.
- Documented but not scored, because the page states it as text with no comparable number or a yes/limited/no (a one-time, usage-based or other-vendor price, or a per-site choice): backup_retention, read_replicas. Read them on the provider page; the score neither rewards nor penalises what it could not compare.

Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every databases peer ranked: https://inetgeek.com/databases/turso/alternatives/

- Price: 73 (62–85), weight 25%, 4 of 6 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: egress_overage_price, free_expires
- Capacity and limits: 47 (41–54), weight 20%, 3 of 7 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: backup_retention, entry_plan_memory, max_connections, read_replicas
- Capabilities: 75 (68–81), weight 20%, 3 of 5 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: connection_pooling, scale_to_zero
- Trust and compliance: 79 (73–85), weight 15%, 9 of 13 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: audit_logs, iso27001, pci_dss, uptime_sla
- Evidence: 93 (93–93), weight 10%, 4 of 4 criteria scored
- Adoption: 50 (40–60), weight 10%, 1 of 1 criteria scored

## What the documentation says

### Pricing

- Free tier: Yes ([source](https://turso.tech/pricing), read 2026-09-13)
- Kind of free offer: Free tier ([source](https://turso.tech/pricing), read 2026-09-13)
- Credit card to start: No ([source](https://turso.tech/pricing), read 2026-09-13)
- Entry paid plan: $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58. ([source](https://turso.tech/pricing), read 2026-09-06)
- Pricing model: Per database, metered on rows rather than compute time: 500 million rows read and 10 million written a month on the free plan, 2.5 billion and 25 million on Developer, with overage at $1 per billion rows read and $1 per million written. ([source](https://turso.tech/pricing), read 2026-09-06)

### Limits

- Storage (entry plan): 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45. ([source](https://turso.tech/pricing), read 2026-09-06)

### Infrastructure

- Regions: Six AWS locations in the Platform API's location list: Tokyo (ap-northeast-1), Mumbai (ap-south-1), Ireland (eu-west-1), N. Virginia (us-east-1), Ohio (us-east-2) and Oregon (us-west-2). Read from the documented GET /v1/locations sample response; the same six AWS regions are offered for PrivateLink. ([source](https://docs.turso.tech/api-reference/locations/list), read 2026-09-13)

### Data

- Engine: SQLite, via libSQL — Turso's own fork. Not Postgres or MySQL, so the query surface and the client libraries differ from every other database on this site. ([source](https://turso.tech/pricing), read 2026-09-06)
- When idle: Databases are archived after 10 days of inactivity on the free plan; an unarchive call through the CLI or Platform API brings the group back. Turso publishes no archival window for paid plans. ([source](https://docs.turso.tech/api-reference/groups/unarchive), read 2026-09-13)
- Database branching: Supported ([source](https://turso.tech/pricing), read 2026-09-06)
- Point-in-time recovery: 10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro. ([source](https://turso.tech/pricing), read 2026-09-06)
- Read replicas: Limited — Embedded replicas run inside your app; managed multi-region Data Edge replica locations are deprecated for new users. ([source](https://docs.turso.tech/features/embedded-replicas/introduction), read 2026-09-13)
- Backup retention: Continuous rather than scheduled: backups are taken at every COMMIT and kept for the plan's restore window — 24 hours on Free, 10 days on Developer, 30 on Scaler, 90 on Pro. Turso publishes no separate backup retention setting. ([source](https://docs.turso.tech/features/point-in-time-recovery), read 2026-09-13)
- Rewind in place: Not supported — PITR restores forward into a fresh database; the existing database cannot be rewound in place. ([source](https://docs.turso.tech/features/point-in-time-recovery), read 2026-09-13)

### Vector

- Max vector dimensions: 65536 dimensions maximum per vector, listed under "Vector Limitations" for libSQL native vector search on Turso Cloud ([source](https://docs.turso.tech/features/ai-and-embeddings), read 2026-09-13)

### Support

- Support on entry paid plan: Community support on Free and on Developer ($4.99/month), the entry paid plan. Priority email support starts at Pro ($416.58/month); Enterprise adds 24x7. ([source](https://turso.tech/pricing), read 2026-09-14)

### Compliance

- SOC 2: Volume-level encryption at rest is described as part of Turso's SOC 2 standards; the docs point to Turso's trust center for details. ([source](https://docs.turso.tech/cloud/encryption), read 2026-09-13)
- HIPAA: Turso states it is HIPAA compliant and will provide a HIPAA compliance BAA letter to Pro plan and Enterprise users on request. ([source](https://turso.tech/healthcare), read 2026-09-13)
- GDPR / data residency: A database confined to EU locations never leaves the EU; the exception is backups, which are stored in S3 in the us-east-2 region. ([source](https://trust.turso.tech/faq), read 2026-09-13)
- Encryption at rest: All databases in Turso Cloud are encrypted at rest at the volume level, which Turso describes as part of its SOC 2 standards. ([source](https://docs.turso.tech/cloud/encryption), read 2026-09-13)
- Customer-managed keys: BYOK on Pro and Enterprise: each database can be encrypted with a key you supply, and Turso never sees or stores the keys. ([source](https://docs.turso.tech/cloud/encryption), read 2026-09-13)
- Role-based access control: Organization members hold one of three roles - admin, member or viewer - and only an admin or owner can change a member's role. ([source](https://docs.turso.tech/api-reference/organizations/members/update), read 2026-09-13)
- Private networking / VPC: AWS PrivateLink VPC endpoints keep traffic to Turso databases inside AWS's private network; offered in six AWS regions. ([source](https://docs.turso.tech/cloud/private-endpoints), read 2026-09-13)
- Dedicated infrastructure: Pro and Enterprise can use their own S3 / S3-Express buckets so data lives in their infrastructure; compute in your own account is roadmap, not shipped. ([source](https://docs.turso.tech/cloud/durability), read 2026-09-13)

## Compared with

- [Turso vs Neon](https://inetgeek.com/compare/neon-vs-turso/)
- [Turso vs PlanetScale](https://inetgeek.com/compare/turso-vs-planetscale/)
- [Turso vs Prisma Postgres](https://inetgeek.com/compare/prisma-postgres-vs-turso/)
- [Turso vs Aiven](https://inetgeek.com/compare/aiven-vs-turso/)
- [Turso vs Amazon Aurora](https://inetgeek.com/compare/amazon-aurora-vs-turso/)
- [Turso vs Amazon RDS](https://inetgeek.com/compare/amazon-rds-vs-turso/)
- [Turso vs Crunchy Bridge](https://inetgeek.com/compare/crunchy-bridge-vs-turso/)
- [Turso vs Neo4j](https://inetgeek.com/compare/neo4j-vs-turso/)
- [Turso vs Nile](https://inetgeek.com/compare/nile-vs-turso/)
- [Turso vs ScaleGrid](https://inetgeek.com/compare/scalegrid-vs-turso/)
- [Turso vs Supabase](https://inetgeek.com/compare/supabase-vs-turso/)
- [Turso vs TigerData](https://inetgeek.com/compare/tigerdata-vs-turso/)