CnosDB vs TDengine

CnosDB: Rust cloud-native time-series database with SQL on DataFusion and InfluxDB-style ingestion. TDengine: Industrial-IoT time-series database with a table-per-device model and built-in streaming and caching.

key differences

Only TDengine has secondary indexes, json, pub/sub.

choose cnosdb for

+Energy and utility telemetry
+IoT platforms needing multi-tenancy
+Replacing InfluxDB 1.x with a SQL-capable engine

best at · Time-series, IoT, Observability

choose tdengine for

+Industrial IoT and SCADA historian replacement
+Connected-vehicle telemetry
+Smart meters and energy grids
+Edge-to-cloud sensor data aggregation

best at · IoT, Time-series, Streaming

CnosDBRust cloud-native time-series database with SQL on DataFusion and InfluxDB-style ingestion.

TDengineIndustrial-IoT time-series database with a table-per-device model and built-in streaming and caching.

overview

Primary model

Time-Series

Also supports

Columnar / OLAP

Relational

Type

Database engine

Status

Active

Developer

CnosDB

TAOS Data

First release

2022

2019

Latest version

2.5.0 (Oct 23, 2026)

3.4.3.3 (Oct 19, 2026)

License

Open source (copyleft)GNU AGPL v3.0

Open source (copyleft)GNU AGPL v3.0 (open-source edition)

Free tier

✓

popularity

WhichDB Score

6.7

17.4

Rank

#354

#192

GitHub stars

1.8K

25.2K

Stack Overflow questions

–

225

scale & guarantees

Comfortable data size

Large (≤ 1 PB)

Horizontal scaling

Native

Multi-region

None

ACID

None

Consistency

Eventual

Strong

Schema

Flexible

Strict

Architecture

Single node, Distributed, Client server

Distributed, Single node, Client server

deployment

Self-hosted

✓

Vendor-managed cloud

—

✓

Serverless

—

Embedded

—

Edge

—

✓

Clouds

–

capabilities

Transactions

—

Joins

✓

Secondary indexes

—

✓

Full-text search

—

Vector search

—

Geospatial

—

JSON

—

✓

Change data capture

—

Triggers

—

Stored procedures

—

Materialized views

—

TTL / expiry

✓

Pub/Sub

—

✓

Columnar storage

✓

In-memory

—

Durable persistence

✓

Compression

✓

Encryption at rest

—

Role-based access

✓

Time travel

—

Branching

—

Online schema changes

—

Streaming ingest

✓

Offline sync

—

Runs in WebAssembly

—

interfaces

Query languages

SQL

Client languages

Go, Java, Python, Rust

C, Java, Python, Go, Rust, JavaScript, C#

Best for

Time-series, IoT, Observability

IoT, Time-series, Streaming, Real-time analytics

Add more to this comparison Not sure either fits? Try smart match

CnosDB vs TDengine: FAQ

What is the difference between CnosDB and TDengine?

CnosDB: Rust cloud-native time-series database with SQL on DataFusion and InfluxDB-style ingestion. TDengine: Industrial-IoT time-series database with a table-per-device model and built-in streaming and caching. Only TDengine has secondary indexes, json, pub/sub.

When should I choose CnosDB over TDengine?

Choose CnosDB for energy and utility telemetry; IoT platforms needing multi-tenancy; and replacing InfluxDB 1.x with a SQL-capable engine. Choose TDengine for industrial IoT and SCADA historian replacement; connected-vehicle telemetry; and smart meters and energy grids.

Is CnosDB or TDengine more popular?

TDengine ranks #192 on the WhichDB Score (17.4/100) and CnosDB ranks #354 (6.7/100). Popularity is not fit: check the requirements that matter for your project.

Are CnosDB and TDengine open source?

Yes. CnosDB is open source. License: GNU AGPL v3.0. Yes. TDengine is open source. License: GNU AGPL v3.0 (open-source edition).