questdbvstimeplus
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| questdb | timeplus | |
|---|---|---|
| Score | 76/100 | 61/100 |
| Rank in category | #4 of 5 in Time Series | #1 of 3 in Streaming |
| GitHub stars | 17 534 | 2 285 |
| Stars, last 30 days | +94 | +16 |
| Stable releases, 12 months | 14 | 18 |
| Latest release | 10.2.0 · 10 Nov 2026 | v3.0.33 · 10 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Java | C++ |
Which one should you pick?
questdb scores 76/100 against 61/100 for timeplus, so it is the safer default.
timeplus ships more often: 18 stable releases in the past year, against 14 for questdb.
If you want the quickest setup, questdb is easier to run; timeplus needs more configuration.
questdb is growing faster right now (+94 stars in 30 days).
Key differences
- Language: questdb is written mainly in Java, timeplus in C++.
- Platforms only questdb lists: Linux, Systemd.
- Platforms only timeplus lists: macOS.
- Features only questdb lists: Apache Arrow result streaming, Apache Parquet storage, High-throughput ingestion, InfluxDB Line Protocol support and 9 more.
- Features only timeplus lists: Change Data Capture (CDC), External Streams (Kafka/Redpanda/Pulsar), External Tables (ClickHouse), JDBC/ODBC Drivers and 5 more.
- Both offer: Materialized Views, REST API.
questdb details →timeplus details →
Swap a project
Keep questdb, compare it with
Keep timeplus, compare it with