A
meilisearch
83.4
59,885 stars · license n/a
Databases
shardingsphere leads by 11.3 · clear
A
83.4
59,885 stars · license n/a
B · leads
94.7
20,830 stars · Apache-2.0
meilisearch versus shardingsphere 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; shardingsphere is written mainly in Java. The composite score is 83.4 for meilisearch and 94.7 for shardingsphere.
meilisearch has 59,885 GitHub stars to shardingsphere's 20,830, a gap of 39,055 (2.87×). Forks are 2,799 for meilisearch and 6,910 for shardingsphere. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 90 versus 100.
Push history: meilisearch was last pushed on 17 November 2026 (0 days ago), and shardingsphere was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for meilisearch (0.005 per star) and 267 for shardingsphere (0.013 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. shardingsphere 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. License scores in this pair are 30 for meilisearch and 96 for shardingsphere. This is a procurement signal, not legal advice.
Only shardingsphere is marked self-hostable here (20,830 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, shardingsphere is open source.
The lead is split. meilisearch is furthest ahead on adoption (100 to 90), while shardingsphere is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
shardingsphere finishes ahead at 94.7 against meilisearch at 83.4, a 11.3 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 | meilisearch | shardingsphere |
|---|---|---|
| GitHub stars | 59,885 | 20,830 |
| Forks | 2,799 | 6,910 |
| Open issues | 318 | 267 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 83.4 | 94.7 |
A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications.
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
meilisearch has more GitHub stars: 59,885 versus 20,830 for shardingsphere. The gap is 39,055 stars.
Both were last pushed on 17 November 2026.
Only shardingsphere 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. shardingsphere 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.
shardingsphere scores 94.7 and meilisearch scores 83.4. This page calls that a clear lead for shardingsphere.