A · level
OpenSearch
92.5
14,016 stars · Apache-2.0
Analytics
Too close to call · 92.5 to 92.8
A · level
92.5
14,016 stars · Apache-2.0
B · level
92.8
13,520 stars · Apache-2.0
OpenSearch versus trino is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Java. The composite score is 92.5 for OpenSearch and 92.8 for trino.
OpenSearch has 14,016 GitHub stars to trino's 13,520, a gap of 496 (1.04×). Forks are 3,088 for OpenSearch and 3,880 for trino. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 97 versus 100.
Push history: OpenSearch was last pushed on 17 November 2026 (0 days ago), and trino was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,385 for OpenSearch (0.242 per star) and 2,758 for trino (0.204 per star). Issue-health scores are 34 and 34; activity scores are 100 and 100.
Both OpenSearch and trino are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both OpenSearch (14,016 stars) and trino (13,520 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, trino is open source.
The lead is split. OpenSearch is furthest ahead on adoption (100 to 100), while trino is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
Composite score: OpenSearch 92.5, trino 92.8. 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 | trino |
|---|---|---|
| GitHub stars | 14,016 | 13,520 |
| Forks | 3,088 | 3,880 |
| Open issues | 3,385 | 2,758 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 34 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.5 | 92.8 |
🔎 Open source distributed and RESTful search engine.
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
OpenSearch has more GitHub stars: 14,016 versus 13,520 for trino. The gap is 496 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both OpenSearch and trino 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. trino 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. 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.5 and trino scores 92.8.