A · level
OpenSearch
92.9
14,016 stars · Apache-2.0
Analytics
Too close to call · 92.9 to 93.7
A · level
92.9
14,016 stars · Apache-2.0
B · level
93.7
10,650 stars · MIT
OpenSearch versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 92.9 for OpenSearch and 93.7 for uPlot.
OpenSearch has 14,016 GitHub stars to uPlot's 10,650, a gap of 3,366 (1.32×). Forks are 3,088 for OpenSearch and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 77.
Push history: OpenSearch was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,385 for OpenSearch (0.242 per star) and 132 for uPlot (0.012 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. uPlot 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. License scores in this pair are 96 for OpenSearch and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both OpenSearch (14,016 stars) and uPlot (10,650 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: OpenSearch is open source, uPlot is open source.
The lead is split. OpenSearch is furthest ahead on fork community (100 to 77), while uPlot is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
Composite score: OpenSearch 92.9, uPlot 93.7. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | uPlot |
|---|---|---|
| GitHub stars | 14,016 | 10,650 |
| Forks | 3,088 | 472 |
| Open issues | 3,385 | 132 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 77 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 93.7 |
🔎 Open source distributed and RESTful search engine.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
OpenSearch has more GitHub stars: 14,016 versus 10,650 for uPlot. The gap is 3,366 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both OpenSearch and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. uPlot 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. OpenSearch scores 92.9 and uPlot scores 93.7.