Databases · head to head
Canary Labs vs TiDB

Canary Labs
Databases
Industrial process historian with published per-tag pricing and no client licence fees
- From
- $3000/year
- Rated
- -

TiDB
Databases
Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.
- From
- Free
- Rated
- -
The short version
- Only TiDB 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.; TiDB a production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
- They diverge on capability: Canary Labs covers Loss-less compression, TiDB covers MySQL wire compatibility.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Canary Labs and TiDB actually diverge.
| Attribute | Canary Labs | TiDB |
|---|---|---|
| Starting price | $3000/year | Free |
| Pricing model | Per tag band per year | freemium |
| Free tier | No | Yes |
| Platforms | Windows, Web | Cloud, AWS, Azure, Google Cloud Platform, Self-managed |
| Founded | Unknown | 2015 |
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 TiDB
- MySQL wire compatibility
- Horizontal write scaling
- Distributed ACID transactions
- TiFlash columnar replica
- Automatic rebalancing
- Raft replication
- Apache 2.0 licence
- Online schema change
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 TiDB
- A water utility replacing SCADA-embedded logging with a historian that survives the next SCADA replacementnot TiDB
- An Ignition site that wants long-term storage and trending without paying per-client for dashboardsnot TiDB
- A plant with regulatory data-retention obligations where swinging-door compression would not survive an auditnot TiDB
TiDB
- A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot Canary Labs
- Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot Canary Labs
- Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot Canary Labs
- Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot 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.
TiDB
- A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
- Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed.
- MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed.
- The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately.
- Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage.
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
TiDB
Free- ServerlessFree
- 5GB storage
- 50M request units
- Free forever tier
- Dedicated$250/month
- Dedicated resources
- SLA guarantees
- Enterprise support
Which should you pick?
Choose Canary Labs if
- You need loss-less compression.
- You work on Windows, Web.
- You also want unlimited clients.
Choose TiDB if
- You need mysql wire compatibility.
- You want to start without paying.
- You work on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
- You also want horizontal write scaling.
Questions people ask
- Is Canary Labs or TiDB better?
- Neither clearly leads. Canary Labs starts at $3000/year and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Canary Labs or TiDB?
- TiDB has a free tier; the other does not. Paid plans start at $3000/year for Canary Labs and Free for TiDB.
- Does Canary Labs or TiDB run on more platforms?
- Canary Labs runs on Windows, Web. TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
- Can I use TiDB for free?
- Yes. TiDB 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 TiDB is typically brought in for.
- What can Canary Labs do that TiDB cannot?
- Canary Labs covers Loss-less compression, Unlimited clients, Store and forward, Views service. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.
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.
TiDB: Is TiDB a drop-in replacement for MySQL?
At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.
Canary Labs: Are client licences extra?
No. Unlimited Axiom browser clients and unlimited Excel clients are included on every tier.
TiDB: What licence is it under?
Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.
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.
TiDB: Do I need TiFlash?
Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.
Canary Labs: Does it use lossy compression?
No. Canary stores every collected value rather than approximating the trend, which matters for regulated data retention.
TiDB: Is the managed cloud the same software?
TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.
TiDB: When is TiDB the wrong choice?
When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.
Related pages
More on Canary Labs
Other head to heads
- Canary Labs vs VerneMQ
- Canary Labs vs EMQX
- Canary Labs vs TimescaleDB
- Canary Labs vs QuestDB
- Canary Labs vs Solace PubSub+
- Canary Labs vs Firebase Realtime Database
- Canary Labs vs Apache Doris
- Canary Labs vs Convex
- Canary Labs vs Instaclustr
- Canary Labs vs Cockroach Labs
- Canary Labs vs Meilisearch
- Canary Labs vs DuckDB
- Canary Labs vs BigQuery
- Canary Labs vs CosmosDB
- Canary Labs vs DataStax
- Canary Labs vs dbt
- Canary Labs vs FaunaDB
- Canary Labs vs Vitess
- Canary Labs vs Elasticsearch
- Canary Labs vs SingleStore
- Canary Labs vs Amazon Redshift
- Canary Labs vs ClickHouse
- Canary Labs vs Apache Druid
- Canary Labs vs Couchbase
- Canary Labs vs MariaDB
- Canary Labs vs Redpanda
- Canary Labs vs RisingWave
- Canary Labs vs ScyllaDB
- Canary Labs vs SQLite
- Canary Labs vs StarRocks
- TiDB vs VerneMQ
- TiDB vs EMQX
- TiDB vs TimescaleDB
- TiDB vs QuestDB
- TiDB vs Solace PubSub+
- TiDB vs Firebase Realtime Database
- TiDB vs Apache Doris
- TiDB vs Convex
- TiDB vs Instaclustr
- TiDB vs Cockroach Labs
- TiDB vs Meilisearch
- TiDB vs DuckDB
- TiDB vs BigQuery
- TiDB vs CosmosDB
- TiDB vs DataStax
- TiDB vs dbt
- TiDB vs FaunaDB
- TiDB vs Vitess
- TiDB vs Elasticsearch
- TiDB vs SingleStore
- TiDB vs Amazon Redshift
- TiDB vs ClickHouse
- TiDB vs Apache Druid
- TiDB vs Couchbase
- TiDB vs MariaDB
- TiDB vs Redpanda
- TiDB vs RisingWave
- TiDB vs ScyllaDB
- TiDB vs SQLite
- TiDB vs StarRocks
