A · leads
OpenSearch
91.1
14,016 stars · Apache-2.0
Analytics
OpenSearch leads by 8.0 · clear
A · leads
91.1
14,016 stars · Apache-2.0
B
83.1
23,865 stars · license n/a
OpenSearch versus timescaledb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. OpenSearch is written mainly in Java; timescaledb is written mainly in C. The composite score is 91.1 for OpenSearch and 83.1 for timescaledb.
timescaledb has 23,865 GitHub stars to OpenSearch's 14,016, a gap of 9,849 (1.70×). Forks are 3,088 for OpenSearch and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 100 versus 88.
Push history: OpenSearch was last pushed on 17 November 2026 (0 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,385 for OpenSearch (0.242 per star) and 476 for timescaledb (0.020 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
OpenSearch 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. timescaledb 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. License scores in this pair are 96 for OpenSearch and 30 for timescaledb. This is a procurement signal, not legal advice.
Only OpenSearch is marked self-hostable here (14,016 stars, deploy score 100). timescaledb is not (23,865 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: OpenSearch is open source, timescaledb is unpriced in this catalog.
The lead is split. OpenSearch is furthest ahead on license flexibility (96 to 30), while timescaledb is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
OpenSearch finishes ahead at 91.1 against timescaledb at 83.1, a 8.0 point clear 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 | OpenSearch | timescaledb |
|---|---|---|
| GitHub stars | 14,016 | 23,865 |
| Forks | 3,088 | 1,188 |
| Open issues | 3,385 | 476 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 34 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 91.1 | 83.1 |
🔎 Open source distributed and RESTful search engine.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
timescaledb has more GitHub stars: 23,865 versus 14,016 for OpenSearch. The gap is 9,849 stars.
Both were last pushed on 17 November 2026.
Only OpenSearch is marked self-hostable. timescaledb is not.
OpenSearch 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. timescaledb 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
OpenSearch scores 91.1 and timescaledb scores 83.1. This page calls that a clear lead for OpenSearch.