IoTDB

IoTDB is a time-series database for collecting, storing, and analysing high-volume data from IoT devices and sensors.

  • Databases
  • Tools & Utilities
IoTDB is a time-series database for collecting, storing, and analysing high-volume data from IoT devices and sensors. It helps home-lab users monitor real-time device health and analyse long-term performance trends with a lightweight, high-performance system.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 15 days ago
Popular
766,428 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
6,428
Open issues
753
Last commit
2026-11-06
Latest release
v2.0.11
License
Apache-2.0
Activity
rising

Checked 15 days ago - source: GitHub (apache/iotdb)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start IoTDB before running client examples Before trying the C++ examples, make sure an IoTDB server is running and use the default local login (root/root) on port 6667. If the server isn't started, the examples will fail to connect. source
  • Let Linux find the C++ session library If a C++ example fails because a shared library is missing, place libiotdb_session.so next to the executable or run export LD_LIBRARY_PATH=. first. That tells Linux where to find the IoTDB runtime library so the program can start. source
  • Open OPC UA ports if you enable that pipe If you create the OPC UA sink with no message security, open TCP port 12686 for OPC UA and 8443 for HTTPS. Without those ports open, the sink can't talk to other systems, and 'no security' means the data is not encrypted. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What default local login and port do IoTDB C++ client examples use?

They expect an IoTDB server to be running and use the default local login root/root on port 6667.

Which ports are needed for an OPC UA sink without message security?

Open TCP port 12686 for OPC UA and 8443 for HTTPS. If the sink is configured without message security, the data is not encrypted.

What components are in a standalone IoTDB deployment?

A standalone instance has one ConfigNode and one DataNode, commonly called 1C1D.

Does IoTDB include MQTT functionality?

A community post describes IoTDB as having a client/server architecture and a built-in MQTT broker.

Answers sourced from github.com, github.com, iotdb.apache.org, www.reddit.com

Community

Collected 48 days ago - public community threads