A · leads
chroma
95.4
29,704 stars · Apache-2.0
Databases
chroma leads by 3.3 · narrow
A · leads
95.4
29,704 stars · Apache-2.0
B
92.1
25,194 stars · AGPL-3.0
chroma versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chroma is written mainly in Rust; TDengine is written mainly in C. The composite score is 95.4 for chroma and 92.1 for TDengine.
chroma has 29,704 GitHub stars to TDengine's 25,194, a gap of 4,510 (1.18×). Forks are 2,609 for chroma and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 92 versus 100.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 979 for chroma (0.033 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
chroma is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for chroma and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both chroma (29,704 stars) and TDengine (25,194 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: chroma is open source, TDengine is open source.
The lead is split. chroma is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
chroma finishes ahead at 95.4 against TDengine at 92.1, a 3.3 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | chroma | TDengine |
|---|---|---|
| GitHub stars | 29,704 | 25,194 |
| Forks | 2,609 | 5,011 |
| Open issues | 979 | 454 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.4 | 92.1 |
Search infrastructure for AI
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
chroma has more GitHub stars: 29,704 versus 25,194 for TDengine. The gap is 4,510 stars.
TDengine was pushed more recently: 15 November 2026 versus 13 November 2026 for chroma. That is 1 days apart.
Yes. This catalog marks both chroma and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
chroma is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
chroma scores 95.4 and TDengine scores 92.1. This page calls that a narrow lead for chroma.