Softwr

Databases · head to head

Canary Labs vs Turso

Canary Labs logo

Canary Labs

Databases

Industrial process historian with published per-tag pricing and no client licence fees

From
$3000/year
Rated
-
Full reviewWebsite
Turso logo

Turso

Databases

SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Turso has a free tier, so it costs nothing to try first.
  • Each has a real cost: Canary Labs pricing steps by tag band rather than actual tags, so a site sitting just above a threshold pays the next band in full; growth from 3,400 to 3,600 tags is a licence purchase, not a rounding error.; 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.
  • They diverge on capability: Canary Labs covers Loss-less compression, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Canary Labs and Turso actually diverge.

Attributes where Canary Labs and Turso differ
AttributeCanary LabsTurso
Starting price$3000/yearFree
Pricing modelPer tag band per yearfreemium
Free tierNoYes
PlatformsWindows, WebWeb

Identical on both: user rating (Not yet rated), category (Databases).

What each one covers

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 Canary Labs

  • Loss-less compression
  • Unlimited clients
  • Store and forward
  • Views service
  • Sparkplug B
  • Calculation engine
  • Axiom
  • ODBC and REST

Only in Turso

  • Per-tenant databases
  • MIT licence
  • Embedded replicas
  • SQLite compatibility
  • HTTP access
  • Branching
  • Point-in-time restore
  • In-process engine

What people use each for

The jobs each tool is most often brought in to do.

Canary Labs

  • A manufacturer that needs a compliant historian but cannot justify a PI System enterprise agreementnot Turso
  • A water utility replacing SCADA-embedded logging with a historian that survives the next SCADA replacementnot Turso
  • An Ignition site that wants long-term storage and trending without paying per-client for dashboardsnot Turso
  • A plant with regulatory data-retention obligations where swinging-door compression would not survive an auditnot Turso

Turso

  • Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Canary Labs
  • Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Canary Labs
  • Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Canary Labs
  • Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Canary Labs

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Canary Labs

  • Pricing steps by tag band rather than actual tags, so a site sitting just above a threshold pays the next band in full; growth from 3,400 to 3,600 tags is a licence purchase, not a rounding error.
  • CustomerCare at 18 percent of licence cost is effectively mandatory on perpetual licences because lapsing it removes upgrades, so the perpetual option is not really a one-time cost.
  • The storage format is proprietary; getting data out at volume means the ODBC connector, an additional 2,500 USD one-time or 1,000 USD a year, or writing against the REST API.
  • Canary is a small vendor with a limited partner network outside North America, so support coverage and integrator availability in Europe and Asia are thinner than for AVEVA or Ignition.
  • It is a Windows-only server product with no Linux or container deployment, which complicates placing collectors in modern edge estates.

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.

Pricing, plan by plan

Canary Labs

$3000/year
  • Subscription, 3,500 tags$3000/year
    • Unlimited Axiom clients
    • Unlimited Excel clients
    • Support and upgrades included
  • Perpetual, 3,500 tags$8730/one-time
    • 7,400 USD licence plus 1,330 USD first-year CustomerCare
    • CustomerCare renews at 18 percent of licence cost per year
    • Unlimited clients
  • Private cloud, 3,500 tags$12320/year
    • Hosted by Canary
    • 1,500 USD one-time setup fee per system
    • Scales to around 58,684 USD per year at 60,000 tags
  • Enterprise unlimited$undefined/year
    • Unlimited tags
    • Negotiated licensing terms
    • Quoted pricing

Turso

Free
  • FreeFree
    • 100 databases
    • 5 GB storage
    • 500M monthly rows read
  • Developer$4.99/month
    • Unlimited databases
    • 9 GB storage
    • 2.5B monthly rows read
  • Scaler$24.92/month
    • Unlimited databases
    • 24 GB storage
    • 100B monthly rows read
  • Pro$416.58/month
    • Unlimited databases
    • 50 GB storage
    • 250B monthly rows read

Which should you pick?

Choose Canary Labs if

  • You need loss-less compression.
  • You work on Windows, Web.
  • You also want unlimited clients.
Canary Labs review

Choose Turso if

  • You need per-tenant databases.
  • You want to start without paying.
  • You also want mit licence.
Turso review

Questions people ask

Is Canary Labs or Turso better?
Neither clearly leads. Canary Labs starts at $3000/year and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Canary Labs or Turso?
Turso has a free tier; the other does not. Paid plans start at $3000/year for Canary Labs and Free for Turso.
Does Canary Labs or Turso run on more platforms?
Canary Labs runs on Windows, Web. Turso runs on Web.
Can I use Turso for free?
Yes. Turso has a free tier, so you can try it without paying. Canary Labs starts at $3000/year.
What is Canary Labs best used for?
Canary Labs is most often used for a manufacturer that needs a compliant historian but cannot justify a pi system enterprise agreement, a water utility replacing scada-embedded logging with a historian that survives the next scada replacement, an ignition site that wants long-term storage and trending without paying per-client for dashboards, a plant with regulatory data-retention obligations where swinging-door compression would not survive an audit. Of those, a manufacturer that needs a compliant historian but cannot justify a pi system enterprise agreement and a water utility replacing scada-embedded logging with a historian that survives the next scada replacement are not what Turso is typically brought in for.
What can Canary Labs do that Turso cannot?
Canary Labs covers Loss-less compression, Unlimited clients, Store and forward, Views service. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

Canary Labs: What does Canary cost?

8,730 USD for a 3,500 tag perpetual system including first-year CustomerCare, or 3,000 USD a year on subscription.

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.

Canary Labs: Are client licences extra?

No. Unlimited Axiom browser clients and unlimited Excel clients are included on every tier.

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.

Canary Labs: Is perpetual cheaper than subscription?

Canary states perpetual pays off after roughly three years, and after that you still pay 18 percent CustomerCare annually.

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.

Canary Labs: Does it use lossy compression?

No. Canary stores every collected value rather than approximating the trend, which matters for regulated data retention.

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.

Share

Related pages

More on Canary Labs

More on Turso

Keep looking

Other head to heads