Skip to content
inetGeek

TigerData vs Turso

SEPT 2026 audit

A comparison of TigerData and Turso built from values read directly from each provider's own documentation, with the source recorded against every figure.

Reviewed by Palash BagchiUpdated 30 criteria comparedSources last checked

The short answer

Choose TigerData if…

Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.

Editorial · Palash Bagchi · approved

Choose Turso if…

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.

Editorial · Palash Bagchi · approved

Consider something else if…

  • TigerData: The advertised storage price assumes 5x compression, so a workload that does not compress that well pays materially more than the figure suggests.
  • Turso: 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.

Neither quite fits? Every other option, ranked by iScore: TigerData alternatives · Turso alternatives

17 sourced criteria separate them — see where, with sources, below.

Visit TigerData documentationVisit Turso documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionTigerDataTurso
Pricing
Free tierYes — Free services are in beta, us-east-1 only, and go read-only at the storage limit.Yes
Kind of free offerFree tierFree tier
Credit card to startNoNo
Entry paid plan
Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month.
$4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58.
Pricing modelCompute and storage are billed separately and hourly rather than as one plan price — compute from $30 a month, storage at $0.177 per GB-month, with the headline storage figure resting on an assumed 5x compression ratio.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.
Limits
Storage (entry plan)Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise9 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.
Infrastructure
Regions13 AWS regions (US, Canada, Sao Paulo, Ireland, London, Frankfurt, Zurich, Mumbai, Singapore, Sydney, Tokyo) and 4 Azure regions for Tiger Cloud servicesSix 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.
Data
EnginePostgreSQL with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud.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.
When idleBilled while running: all active standard services are charged even when not in use, and unused ones must be paused or deleted manuallyDatabases 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.
Database branchingSupported — Service forks, created at current state, last snapshot, or a timestamp in the plan recovery window.Supported
Point-in-time recovery
3 days on Performance, with cross-region backups available for disaster recovery on higher tiers.
10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro.
Read replicas
Supported
Limited — Embedded replicas run inside your app; managed multi-region Data Edge replica locations are deprecated for new users.
Backup retentionOne full backup weekly plus daily incrementals, kept for the plan recovery period; Enterprise can set 14-180 days; cross-region copies always kept 14 daysContinuous 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.
Rewind in placeNot supported — Recovery is to a PITR fork you point the app at; the original service stays untouched.Not supported — PITR restores forward into a fresh database; the existing database cannot be rewound in place.
Support
Support on entry paid plan
Basic support, 9-5 ET, on the entry plan. Enterprise adds production support at 24x7.
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.
Compliance
SOC 2
SOC 2 Type 2 compliant; the annual report is available to customers on the Scale or Enterprise pricing plans by support ticket.
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.
HIPAAThe Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant. Enterprise plan only.Turso states it is HIPAA compliant and will provide a HIPAA compliance BAA letter to Pro plan and Enterprise users on request.
GDPR / data residencyComplies with EU GDPR; all customer data is processed under Tiger Data's GDPR-compliant Data Processor Addendum, which applies to all customers.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.
Encryption at restBoth active databases and backups are encrypted at rest (and in transit) with the industry-standard AES-256 algorithm.All databases in Turso Cloud are encrypted at rest at the volume level, which Turso describes as part of its SOC 2 standards.
Role-based access controlProject-level role-based access with Owner, Admin, Developer and Viewer roles; database-level roles are managed separately per service.Organization members hold one of three roles - admin, member or viewer - and only an admin or owner can change a member's role.
Private networking / VPCVPC peering leaves no public internet access to the service; AWS PrivateLink private endpoints route traffic over the AWS network.AWS PrivateLink VPC endpoints keep traffic to Turso databases inside AWS's private network; offered in six AWS regions.
Dedicated infrastructureManaged Service for TimescaleDB (TimescaleDB hosted with Aiven): each service virtual machine is dedicated to a single customer, never multi-tenanted. Read on the MST security docs; scope is MST, not the Tiger Cloud platform.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.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

Entry paid plan

TigerData
Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month.
Turso
$4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58.
Sources (2) →

Pricing model

TigerData
Compute and storage are billed separately and hourly rather than as one plan price — compute from $30 a month, storage at $0.177 per GB-month, with the headline storage figure resting on an assumed 5x compression ratio.
Turso
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.
Sources (2) →
  • Pricing — TigerData ↗

    “Pay as you go hourly Compute starts at $30/month Storage priced at $0.177/GB-month [...] Effective storage price is based on 5x compression (average customer savings).”

    Read 2026-09-06 · official pricing · Report a correction

  • Pricing — Turso ↗

    “Monthly Rows Read Free 500 Million Developer 2.5 Billion + $1 / Billion Scaler 100 Billion + $0.80 / Billion [...] Monthly Rows Written Free 10 Million Developer 25 Million + $1 / Million”

    Read 2026-09-06 · official pricing · Report a correction

Storage (entry plan)

TigerData
Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise
Turso
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.
Sources (2) →

Regions

TigerData
13 AWS regions (US, Canada, Sao Paulo, Ireland, London, Frankfurt, Zurich, Mumbai, Singapore, Sydney, Tokyo) and 4 Azure regions for Tiger Cloud services
Turso
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.
Sources (2) →
  • Supported regions | Tiger Data Docs ↗

    “Tiger Cloud services run in the following Amazon Web Services (AWS) regions: [...] Tiger Cloud services run in the following Microsoft Azure regions:”

    Read 2026-09-13 · official docs · Report a correction

  • List Locations - Turso Platform API ↗

    “"aws-ap-northeast-1" : "AWS AP NorthEast (Tokyo)" , "aws-ap-south-1" : "AWS AP South (Mumbai)" , "aws-eu-west-1" : "AWS EU West (Ireland)" , "aws-us-east-1" : "AWS US East (Virginia)" , "aws-us-east-2" : "AWS US East (Ohio)" , "aws-us-west-2" : "AWS US West (Oregon)"”

    Read 2026-09-13 · official docs · Report a correction

Engine

TigerData
PostgreSQL with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud.
Turso
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.
Sources (2) →

When idle

TigerData
Billed while running: all active standard services are charged even when not in use, and unused ones must be paused or deleted manually
Turso
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.
Sources (2) →

Point-in-time recovery

TigerData

3 days on Performance, with cross-region backups available for disaster recovery on higher tiers.

Turso

10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro.

Sources (2) →

Read replicas

TigerData
Supported
Turso
Limited — Embedded replicas run inside your app; managed multi-region Data Edge replica locations are deprecated for new users.
Sources (2) →

Backup retention

TigerData
One full backup weekly plus daily incrementals, kept for the plan recovery period; Enterprise can set 14-180 days; cross-region copies always kept 14 days
Turso
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.
Sources (2) →
  • Back up and recover services | Tiger Data Docs ↗

    “Tiger Cloud automatically creates one full backup every week, and incremental backups every day in the same region as your service. [...] on Enterprise you can set a retention period of up to 180 days for each service. [...] Cross-region backups are always kept for 14 days.”

    Read 2026-09-13 · official docs · Report a correction

  • Point-in-Time Recovery - Turso Documentation ↗

    “Free plan users can restore to any point in time within the last 24 hours. Developer, Scaler, and Pro users can restore to any point in time within the last 10, 30, or 90 days, respectively.”

    Read 2026-09-13 · official docs · Report a correction

Support on entry paid plan

TigerData
Basic support, 9-5 ET, on the entry plan. Enterprise adds production support at 24x7.
Turso
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.
Sources (2) →
  • Tiger Data Pricing ↗

    “point-in-time-recovery to 3 days performance insights basic support (9-5 ET) [...] production support (24x7, 1 hour response time for sev 1 issues)”

    Read 2026-09-14 · official pricing · Report a correction

  • Turso Pricing ↗

    “1 day community sign up developer $4.99/month [...] 30 day retention priority email + support get pro enterprise custom pricing [...] 24x7 priority email + support”

    Read 2026-09-14 · official pricing · Report a correction

SOC 2

TigerData
SOC 2 Type 2 compliant; the annual report is available to customers on the Scale or Enterprise pricing plans by support ticket.
Turso
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.
Sources (2) →

HIPAA

TigerData
The Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant. Enterprise plan only.
Turso
Turso states it is HIPAA compliant and will provide a HIPAA compliance BAA letter to Pro plan and Enterprise users on request.
Sources (2) →

GDPR / data residency

TigerData
Complies with EU GDPR; all customer data is processed under Tiger Data's GDPR-compliant Data Processor Addendum, which applies to all customers.
Turso
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.
Sources (2) →

Encryption at rest

TigerData
Both active databases and backups are encrypted at rest (and in transit) with the industry-standard AES-256 algorithm.
Turso
All databases in Turso Cloud are encrypted at rest at the volume level, which Turso describes as part of its SOC 2 standards.
Sources (2) →

Role-based access control

TigerData
Project-level role-based access with Owner, Admin, Developer and Viewer roles; database-level roles are managed separately per service.
Turso
Organization members hold one of three roles - admin, member or viewer - and only an admin or owner can change a member's role.
Sources (2) →

Private networking / VPC

TigerData
VPC peering leaves no public internet access to the service; AWS PrivateLink private endpoints route traffic over the AWS network.
Turso
AWS PrivateLink VPC endpoints keep traffic to Turso databases inside AWS's private network; offered in six AWS regions.
Sources (2) →
  • About security in Tiger Cloud | Tiger Data Docs ↗

    “When using VPC peering, no public Internet-based access is provided to the service. [...] Tiger Cloud enables you to connect to your services through a private endpoint in AWS using AWS PrivateLink.”

    Read 2026-09-13 · official docs · Report a correction

  • Turso Cloud Private Endpoints ↗

    “Set up an AWS VPC endpoint to securely access Turso databases through AWS PrivateLink, keeping all traffic within AWS's private network. [...] us-east-1 us-east-2 us-west-2 eu-west-1 ap-south-1 ap-northeast-1”

    Read 2026-09-13 · official docs · Report a correction

Dedicated infrastructure

TigerData
Managed Service for TimescaleDB (TimescaleDB hosted with Aiven): each service virtual machine is dedicated to a single customer, never multi-tenanted. Read on the MST security docs; scope is MST, not the Tiger Cloud platform.
Turso
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.
Sources (2) →

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

Documented by only one.

These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing — except where we say we read the other provider's own page on a given date and it does not state it. Those rows lean, and the provider can correct them with a link.

Memory (entry plan)TigerData: Up to 32 GB per service on the Performance (entry) plan; 128 GB on Scale and 256 GB on Enterprise
Managed connection poolingTigerData: Supported — pgBouncer pooler added per service in Console, in session or transaction mode.
Uptime SLATigerData: Enterprise SLAs, with no percentage published on the pricing page.
Connection limitTigerData: max_connections settable 25-500 on services from 0.5 CPU / 2 GiB to 4 CPU / 16 GiB, and 25-2000 from 8 CPU / 32 GiB up; fixed at 25 on shared CPU
Storage priceTigerData: $0.177 per GB-month on Performance and $0.212 on Scale. TigerData notes the effective price assumes 5x compression, which is an average rather than a guarantee.
Max vector dimensionsTurso: 65536 dimensions maximum per vector, listed under "Vector Limitations" for libSQL native vector search on Turso Cloud
Response time commitmentTigerData: 1 hour for Sev 1, on Enterprise only. The entry plan publishes opening hours, 9-5 ET, which is not a response commitment.
Customer-managed keysTurso: BYOK on Pro and Enterprise: each database can be encrypted with a key you supply, and Turso never sees or stores the keys.
04.

Questions this comparison answers.

Entry paid plan: TigerData or Turso?

TigerData: Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month.

Turso: $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58.

Storage (entry plan): TigerData or Turso?

TigerData: Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise

Turso: 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.

Should I choose TigerData or Turso?

Pick TigerData if Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.

Pick Turso if 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.

Provider pages

TigerDataManaged TimescaleDB — Postgres for time-series and real-time analytics — priced with compute and storage billed separately.TursoManaged SQLite built on libSQL, priced per database with rows read and written as the metered units.

Related comparisons

Aiven vs TigerDataAiven vs TursoAmazon Aurora vs TigerDataAmazon Aurora vs TursoAmazon RDS vs TigerDataNeo4j vs TigerDataNeo4j vs TursoNeon vs TigerData

Comments

Every page here is sourced and dated.