A
meilisearch
83.8
59,885 stars · license n/a
Databases
TDengine leads by 6.2 · narrow
A
83.8
59,885 stars · license n/a
B · leads
90.0
25,194 stars · AGPL-3.0
meilisearch versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. meilisearch is written mainly in Rust; TDengine is written mainly in C. The composite score is 83.8 for meilisearch and 90.0 for TDengine.
meilisearch has 59,885 GitHub stars to TDengine's 25,194, a gap of 34,691 (2.38×). Forks are 2,799 for meilisearch and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 93 versus 100.
Push history: meilisearch was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 318 for meilisearch (0.005 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
meilisearch is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for meilisearch and 52 for TDengine. This is a procurement signal, not legal advice.
Only TDengine is marked self-hostable here (25,194 stars, deploy score 100). meilisearch is not (59,885 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: meilisearch is unpriced in this catalog, TDengine is open source.
The lead is split. meilisearch is furthest ahead on adoption (100 to 92), while TDengine is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
TDengine finishes ahead at 90.0 against meilisearch at 83.8, a 6.2 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 | meilisearch | TDengine |
|---|---|---|
| GitHub stars | 59,885 | 25,194 |
| Forks | 2,799 | 5,011 |
| Open issues | 318 | 454 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 83.8 | 90.0 |
A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
meilisearch has more GitHub stars: 59,885 versus 25,194 for TDengine. The gap is 34,691 stars.
meilisearch was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Only TDengine is marked self-hostable. meilisearch is not.
meilisearch is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
TDengine scores 90.0 and meilisearch scores 83.8. This page calls that a narrow lead for TDengine.