Databases · head to head
Canary Labs vs turbopuffer

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

turbopuffer
Databases
Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.
- From
- $16/month
- Rated
- -
The short version
- 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.; turbopuffer a cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second.
- They diverge on capability: Canary Labs covers Loss-less compression, turbopuffer covers Object storage architecture.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Canary Labs and turbopuffer actually diverge.
| Attribute | Canary Labs | turbopuffer |
|---|---|---|
| Starting price | $3000/year | $16/month |
| Pricing model | Per tag band per year | subscription |
| Platforms | Windows, Web | Web |
Identical on both: free tier (No), 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 turbopuffer
- Object storage architecture
- Namespaces
- Vector search
- Full-text search
- Attribute filtering
- Documented limits
- Configurable consistency
- Durable writes
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 turbopuffer
- A water utility replacing SCADA-embedded logging with a historian that survives the next SCADA replacementnot turbopuffer
- An Ignition site that wants long-term storage and trending without paying per-client for dashboardsnot turbopuffer
- A plant with regulatory data-retention obligations where swinging-door compression would not survive an auditnot turbopuffer
turbopuffer
- A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot Canary Labs
- Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot Canary Labs
- Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot Canary Labs
- Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot 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.
turbopuffer
- A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second.
- Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable.
- It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends.
- Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service.
- It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you.
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
turbopuffer
$16/month- Launch$16/month
- All database features
- Multi-tenancy deployment
- SOC2 & GDPR-ready DPA
- Scale$256/month
- Everything in Launch
- HIPAA-ready BAA
- Single Sign-On (SSO)
- Enterprise$4096/month
- Everything in Scale
- Single-tenancy & BYOC deployment options
- Private networking
Which should you pick?
Choose Canary Labs if
- You need loss-less compression.
- You work on Windows, Web.
- You also want unlimited clients.
Choose turbopuffer if
- You need object storage architecture.
- You also want namespaces.
Questions people ask
- Is Canary Labs or turbopuffer better?
- Neither clearly leads. Canary Labs starts at $3000/year and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Canary Labs or turbopuffer?
- Canary Labs starts at $3000/year and turbopuffer at $16/month.
- Does Canary Labs or turbopuffer run on more platforms?
- Canary Labs runs on Windows, Web. turbopuffer runs on Web.
- 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 turbopuffer is typically brought in for.
- What can Canary Labs do that turbopuffer cannot?
- Canary Labs covers Loss-less compression, Unlimited clients, Store and forward, Views service. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.
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.
turbopuffer: Can I self-host turbopuffer?
There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.
Canary Labs: Are client licences extra?
No. Unlimited Axiom browser clients and unlimited Excel clients are included on every tier.
turbopuffer: How fast is it really?
Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.
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.
turbopuffer: Is it consistent?
Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.
Canary Labs: Does it use lossy compression?
No. Canary stores every collected value rather than approximating the trend, which matters for regulated data retention.
turbopuffer: What is it best at?
Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.
turbopuffer: What are the hard limits?
Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.
Related pages
More on Canary Labs
More on turbopuffer
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 PostgreSQL
- Canary Labs vs Airtable
- Canary Labs vs Amazon Aurora
- Canary Labs vs Chroma
- Canary Labs vs Dremio
- Canary Labs vs Typesense
- Canary Labs vs Dragonfly
- Canary Labs vs LanceDB
- Canary Labs vs Readyset
- Canary Labs vs Valkey
- Canary Labs vs ArangoDB
- Canary Labs vs Apache Solr
- turbopuffer vs VerneMQ
- turbopuffer vs EMQX
- turbopuffer vs TimescaleDB
- turbopuffer vs QuestDB
- turbopuffer vs Solace PubSub+
- turbopuffer vs Firebase Realtime Database
- turbopuffer vs Apache Doris
- turbopuffer vs Convex
- turbopuffer vs Instaclustr
- turbopuffer vs Cockroach Labs
- turbopuffer vs Meilisearch
- turbopuffer vs DuckDB
- turbopuffer vs BigQuery
- turbopuffer vs CosmosDB
- turbopuffer vs DataStax
- turbopuffer vs dbt
- turbopuffer vs FaunaDB
- turbopuffer vs PostgreSQL
- turbopuffer vs Airtable
- turbopuffer vs Amazon Aurora
- turbopuffer vs Chroma
- turbopuffer vs Dremio
- turbopuffer vs Typesense
- turbopuffer vs Dragonfly
- turbopuffer vs LanceDB
- turbopuffer vs Readyset
- turbopuffer vs Valkey
- turbopuffer vs ArangoDB
- turbopuffer vs Apache Solr
