vs

Machbase vs TDengine

Machbase: Korean time-series database for sensor data, bundled with MQTT, HTTP and dashboards in one binary. TDengine: Industrial-IoT time-series database with a table-per-device model and built-in streaming and caching.

key differences

  • Licensing: Machbase is proprietary (Machbase License (free for non-commercial use; UI is open source)); TDengine is open source (copyleft) (GNU AGPL v3.0 (open-source edition)).
  • TDengine is built for larger datasets (≤ 1 PB) than Machbase (≤ 10 TB).
  • Only TDengine has joins, json, role-based access.

choose machbase for

  • +Factory sensor data collection at the edge
  • +Equipment vibration and condition monitoring
  • +Self-contained IoT gateways with dashboards

best at · IoT, Time-series, Edge

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

overview
Primary model
Time-Series
Time-Series
Also supports
Relational
Relational
Type
Database engine
Database engine
Status
Active
Active
Developer
Machbase Inc.
TAOS Data
First release
2013
2019
Latest version
Neo 8.7.2 (Oct 20, 2026)
3.4.3.3 (Oct 19, 2026)
License
ProprietaryMachbase License (free for non-commercial use; UI is open source)
Open source (copyleft)GNU AGPL v3.0 (open-source edition)
Free tier
✓
✓
popularity
WhichDB Score
3.1
17.4
Rank
#447
#192
GitHub stars
205
25.2K
Stack Overflow questions
–
225
scale & guarantees
Comfortable data size
Medium (≤ 10 TB)
Large (≤ 1 PB)
Horizontal scaling
Native
Native
Multi-region
None
None
ACID
None
None
Consistency
Strong
Strong
Schema
Strict
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, TQL
SQL
Client languages
Go, Python, Java, C
C, Java, Python, Go, Rust, JavaScript, C#
Best for
IoT, Time-series, Edge
IoT, Time-series, Streaming, Real-time analytics

Machbase vs TDengine: FAQ

What is the difference between Machbase and TDengine?

Machbase: Korean time-series database for sensor data, bundled with MQTT, HTTP and dashboards in one binary. TDengine: Industrial-IoT time-series database with a table-per-device model and built-in streaming and caching. Licensing: Machbase is proprietary (Machbase License (free for non-commercial use; UI is open source)); TDengine is open source (copyleft) (GNU AGPL v3.0 (open-source edition)). TDengine is built for larger datasets (≤ 1 PB) than Machbase (≤ 10 TB). Only TDengine has joins, json, role-based access.

When should I choose Machbase over TDengine?

Choose Machbase for factory sensor data collection at the edge; equipment vibration and condition monitoring; and self-contained IoT gateways with dashboards. Choose TDengine for industrial IoT and SCADA historian replacement; connected-vehicle telemetry; and smart meters and energy grids.

Is Machbase or TDengine more popular?

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

Are Machbase and TDengine open source?

No. Machbase is proprietary, closed-source software. License: Machbase License (free for non-commercial use; UI is open source). Yes. TDengine is open source. License: GNU AGPL v3.0 (open-source edition).