Cloud · head to head
Qovery vs Turso

Qovery
Cloud
Deployment platform that provisions and operates Kubernetes inside your own cloud account
- From
- On request
- Free plan
- No

Turso
Databases
SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.
- From
- Free
- Free plan
- Yes
The short version
- Turso starts at $4.99/mo; Qovery prices on request.
- Only Qovery lists bring your own cloud; only Turso lists per-tenant databases.
- Prices and features on this page were last checked on 13 November 2026.
How do Qovery and Turso differ?
Qovery and Turso differ on starting price (On request against Free), pricing model (Quote against Freemium) and free tier (No against Yes). Only the attributes on which Qovery and Turso actually diverge.
Which features does each one have?
They share no listed features; 6 appear only for Qovery and 10 only for Turso. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Qovery
- Bring your own cloud
- Preview environments
- Cluster lifecycle
- Terraform provider
- MCP server
- Policy as code
Only in Turso
- Per-tenant databases
- MIT licence
- Embedded replicas
- SQLite compatibility
- HTTP access
- Branching
- Point-in-time restore
- In-process engine
What is each one used for?
The jobs each tool is most often brought in to do.
Qovery
- A regulated business that must keep application data inside its own AWS account but has nobody to build a deployment platformnot Turso
- Giving twenty engineers preview environments per pull request without writing and maintaining Terraform and Helm by handnot Turso
- Standardising deployment across AWS and GCP when acquisitions have left the organisation on two cloudsnot Turso
- Replacing a managed platform when data residency rules put every hosted option out of reachnot Turso
Turso
- Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Qovery
- Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Qovery
- Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Qovery
- Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Qovery
Where do Qovery and Turso fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Qovery
- No plan publishes a price, deployment minute overage rates are not disclosed, and there is a 14 day trial rather than a free tier, so you cannot budget or compare against alternatives without going through sales
- The GPL-3.0 engine and console do not constitute a self-hostable product, because the control plane and API are closed and the self-hosted option is gated behind Enterprise, so the open licence gives you no exit if the company changes direction
- Qovery provisions managed Kubernetes into your account, which means the cloud bill sits on top of the licence and Qovery initiates control plane and ingress controller upgrades on infrastructure your team is accountable for
- The company repositioned to agentic infrastructure in June 2026 and now ships a deployment platform, a browser development portal and autonomous coding agents concurrently, so a buyer of the deployment product is not at the centre of the roadmap
- Team and Business are capped at two and three connected clusters with fixed 4 vCPU CI runners and no single sign-on on Team, which pushes teams of moderate size onto quoted Enterprise pricing earlier than the plan names imply
Turso
- SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option
- Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated
- There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate
- Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on
- Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only
How much do Qovery and Turso cost?
Qovery is priced on request; Turso has a free plan, with paid plans from $4.99/mo. Plan by plan below, from each vendor's own pricing page.
Qovery
On request- TeamOn request
- Billed on usage with no published rate card
- 10 users, up to 100 environments, 2 connected clusters
- 5,000 deployment minutes and 7 day audit logs
- BusinessOn request
- Billed on usage with no published rate card
- 20 users, up to 250 environments, 3 connected clusters
- 10,000 deployment minutes and 30 day audit logs
- EnterpriseOn request
- Custom users, environments and clusters
- Self-hosted or air-gapped control plane
- On-premises and bring-your-own-Kubernetes
Turso
Free- FreeFree
- 100 databases
- 5 GB storage
- 500M monthly rows read
- Developer$4.99/mo
- Unlimited databases
- 9 GB storage
- 2.5B monthly rows read
- Scaler$24.92/mo
- Unlimited databases
- 24 GB storage
- 100B monthly rows read
- Pro$416.58/mo
- Unlimited databases
- 50 GB storage
- 250B monthly rows read
Which should you pick?
Choose Qovery if
- You need bring your own cloud.
- You work on Web, API, Self-hosted.
- You also want preview environments.
Choose Turso if
- You need per-tenant databases.
- You want to start without paying.
- You also want mit licence.
Questions people ask
- Is Qovery or Turso better?
- Neither clearly leads. Qovery starts at On request and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Qovery or Turso?
- Turso has a free tier; the other does not. Paid plans start at On request for Qovery and Free for Turso.
- Does Qovery or Turso run on more platforms?
- Qovery runs on Web, API, Self-hosted. Turso runs on Web.
- Can I use Turso for free?
- Yes. Turso has a free tier, so you can try it without paying. Qovery starts at On request.
- What is Qovery best used for?
- Qovery is most often used for a regulated business that must keep application data inside its own aws account but has nobody to build a deployment platform, giving twenty engineers preview environments per pull request without writing and maintaining terraform and helm by hand, standardising deployment across aws and gcp when acquisitions have left the organisation on two clouds, replacing a managed platform when data residency rules put every hosted option out of reach. Of those, a regulated business that must keep application data inside its own aws account but has nobody to build a deployment platform and giving twenty engineers preview environments per pull request without writing and maintaining terraform and helm by hand are not what Turso is typically brought in for.
- What can Qovery do that Turso cannot?
- Qovery covers Bring your own cloud, Preview environments, Cluster lifecycle, Terraform provider. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.
Answered from the vendors’ own pages
Qovery: Does Qovery run my applications on its own servers?
No. It provisions and operates Kubernetes inside your AWS, GCP, Azure or Scaleway account, so compute and data stay with your cloud provider and that bill is entirely separate from the Qovery licence.
Turso: Is Turso just hosted SQLite?
Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.
Qovery: Can I self-host Qovery?
Only on Enterprise. The deployment engine and console are GPL-3.0, but the control plane is closed source and the self-hosted and air-gapped deployments are commercial Enterprise features.
Turso: Can I really run a million databases?
That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.
Qovery: What does it cost?
Qovery does not publish a rate card. Team and Business are billed on usage and quoted through sales, and Enterprise is fully custom. There is a 14 day trial with no card required.
Turso: How do embedded replicas handle read-after-write?
Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.
Qovery: What survives if I stop paying?
The Kubernetes cluster and the workloads keep running in your cloud account, but you lose the console, the deployment pipeline, preview environments and every process built on top of them.
Turso: What licence is it under?
libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.
Turso: Is Turso still an edge database?
No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.
Related pages
Other head to heads
- Qovery vs Render
- Qovery vs Porter
- Qovery vs Northflank
- Qovery vs CapRover
- Qovery vs Coolify
- Qovery vs Railway
- Qovery vs Dokku
- Qovery vs Scaleway
- Qovery vs Portworx
- Qovery vs Podman
- Qovery vs containerd
- Qovery vs Encore
- Qovery vs CloudAMQP
- Qovery vs Deno Deploy
- Qovery vs Go
- Qovery vs Hetzner Cloud
- Qovery vs Infracost
- Qovery vs Jaeger
- Qovery vs SurrealDB
- Qovery vs MotherDuck
- Qovery vs EMQX
- Qovery vs DuckDB
- Qovery vs Trino
- Qovery vs SQLite
- Qovery vs Nile
- Qovery vs Teradata
- Qovery vs Apache Kafka
- Qovery vs BigQuery
- Qovery vs Typesense
- Qovery vs Apache Spark
- Qovery vs RavenDB
- Qovery vs Readyset
- Qovery vs Redpanda
- Qovery vs RisingWave
- Qovery vs ScyllaDB
- Qovery vs Solace PubSub+
- Turso vs Render
- Turso vs Porter
- Turso vs Northflank
- Turso vs CapRover
- Turso vs Coolify
- Turso vs Railway
- Turso vs Dokku
- Turso vs Scaleway
- Turso vs Portworx
- Turso vs Podman
- Turso vs containerd
- Turso vs Encore
- Turso vs CloudAMQP
- Turso vs Deno Deploy
- Turso vs Go
- Turso vs Hetzner Cloud
- Turso vs Infracost
- Turso vs Jaeger
- Turso vs SurrealDB
- Turso vs MotherDuck
- Turso vs EMQX
- Turso vs DuckDB
- Turso vs Trino
- Turso vs SQLite
- Turso vs Nile
- Turso vs Teradata
- Turso vs Apache Kafka
- Turso vs BigQuery
- Turso vs Typesense
- Turso vs Apache Spark
- Turso vs RavenDB
- Turso vs Readyset
- Turso vs Redpanda
- Turso vs RisingWave
- Turso vs ScyllaDB
- Turso vs Solace PubSub+
