Cloud · head to head
Encore vs Turso

Encore
Cloud
Automated infrastructure for humans and agents
- From
- Free
- Free plan
- Yes

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
- Free plans on both; paid from $49/mo and $4.99/mo.
- Only Encore lists local development environment; only Turso lists per-tenant databases.
- Where Encore falls short: limited language support (TypeScript and Go only).
- Prices and features on this page were last checked on 13 November 2026.
How do Encore and Turso differ?
Encore and Turso differ on platforms (Web, API against Web) and category (Cloud against Databases). Only the attributes on which Encore and Turso actually diverge.
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: pricing model for Encore.
Which features does each one have?
They share no listed features; 6 appear only for Encore 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 Encore
- Local development environment
- Preview environments
- Infrastructure automation
- Cloud deployment
- Self-service operations
- Distributed tracing
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?
Encore is most often brought in for building microservices with database provisioning. The jobs each tool is most often brought in to do.
Encore
- Building microservices with database provisioningnot Turso
- Creating feature branch preview environmentsnot Turso
- Deploying TypeScript and Go backends to AWS/GCPnot Turso
Turso
- Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Encore
- Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Encore
- Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Encore
- Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Encore
Where do Encore and Turso fall short?
Encore's most cited limit: limited language support (TypeScript and Go only). Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Encore
- Limited language support (TypeScript and Go only)
- Pro tier requires per-member subscription pricing
- Additional resource costs beyond subscription for AWS/GCP provisioning
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 Encore and Turso cost?
Encore has a free plan, with paid plans from $49/mo; Turso has a free plan, with paid plans from $4.99/mo. Plan by plan below, from each vendor's own pricing page.
Encore
Free- StarterFree
- 2 free dev environments
- 1M distributed tracing events/month
- 7-day log retention
- Pro$49/mo
- Unlimited free dev environments
- 20M tracing events/month
- 30-day log retention
- EnterpriseOn request
- Enterprise security and compliance
- SSO/SAML
- Custom RBAC
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 Encore if
- You need local development environment.
- You want to start without paying.
- You work on Web, API.
- 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 Encore or Turso better?
- Neither clearly leads. Encore starts at Free and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Encore or Turso?
- Encore starts at Free and Turso at Free.
- Does Encore or Turso run on more platforms?
- Encore runs on Web, API. Turso runs on Web.
- Can I use Encore for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Encore best used for?
- Encore is most often used for building microservices with database provisioning, creating feature branch preview environments, deploying typescript and go backends to aws/gcp. Of those, building microservices with database provisioning and creating feature branch preview environments are not what Turso is typically brought in for.
- What can Encore do that Turso cannot?
- Encore covers Local development environment, Preview environments, Infrastructure automation, Cloud deployment. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.
Answered from the vendors’ own pages
Encore: What happens after the free tier?
The Pro plan costs $49/member/month plus usage charges of $2.50 per resource and $99 per AWS/GCP environment.
SourceTurso: 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.
Encore: Do I own my infrastructure?
Yes, Encore deploys infrastructure in your own AWS or GCP cloud account, so you maintain complete control and avoid vendor lock-in.
SourceTurso: 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.
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.
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
- Encore vs Pulumi
- Encore vs Zeabur
- Encore vs Porter
- Encore vs AWS (Amazon Web Services)
- Encore vs Hetzner Cloud
- Encore vs Linode
- Encore vs Vultr
- Encore vs Google Cloud Platform
- Encore vs Microsoft Azure
- Encore vs Nitric
- Encore vs SST
- Encore vs Heroku
- Encore vs Caddy
- Encore vs Confluent Cloud
- Encore vs Neon
- Encore vs Podman
- Encore vs Railway
- Encore vs Wiz
- Encore vs SurrealDB
- Encore vs MotherDuck
- Encore vs EMQX
- Encore vs DuckDB
- Encore vs Trino
- Encore vs SQLite
- Encore vs Nile
- Encore vs Teradata
- Encore vs Apache Kafka
- Encore vs BigQuery
- Encore vs Typesense
- Encore vs Apache Spark
- Encore vs RavenDB
- Encore vs Readyset
- Encore vs Redpanda
- Encore vs RisingWave
- Encore vs ScyllaDB
- Encore vs Solace PubSub+
- Turso vs Pulumi
- Turso vs Zeabur
- Turso vs Porter
- Turso vs AWS (Amazon Web Services)
- Turso vs Hetzner Cloud
- Turso vs Linode
- Turso vs Vultr
- Turso vs Google Cloud Platform
- Turso vs Microsoft Azure
- Turso vs Nitric
- Turso vs SST
- Turso vs Heroku
- Turso vs Caddy
- Turso vs Confluent Cloud
- Turso vs Neon
- Turso vs Podman
- Turso vs Railway
- Turso vs Wiz
- 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+
