A · leads
postgrest
95.6
27,763 stars · MIT
Databases
postgrest leads by 3.3 · narrow
A · leads
95.6
27,763 stars · MIT
B
92.3
25,194 stars · AGPL-3.0
postgrest versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. postgrest is written mainly in Haskell; TDengine is written mainly in C. The composite score is 95.6 for postgrest and 92.3 for TDengine.
postgrest has 27,763 GitHub stars to TDengine's 25,194, a gap of 2,569 (1.10×). Forks are 1,238 for postgrest and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 84 versus 100.
Push history: postgrest 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 407 for postgrest (0.015 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
postgrest is listed as MIT, 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 postgrest and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both postgrest (27,763 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: postgrest is open source, TDengine is open source.
The lead is split. postgrest is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on fork community (100 to 84). Choose the dimension a rollout cannot compromise on.
postgrest finishes ahead at 95.6 against TDengine at 92.3, 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 | postgrest | TDengine |
|---|---|---|
| GitHub stars | 27,763 | 25,194 |
| Forks | 1,238 | 5,011 |
| Open issues | 407 | 454 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.6 | 92.3 |
REST API for any Postgres database
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
postgrest has more GitHub stars: 27,763 versus 25,194 for TDengine. The gap is 2,569 stars.
postgrest was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both postgrest and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
postgrest is listed as MIT, 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.
postgrest scores 95.6 and TDengine scores 92.3. This page calls that a narrow lead for postgrest.