A
meilisearch
84.8
59,885 stars · license n/a
Databases
tile38 leads by 4.9 · narrow
A
84.8
59,885 stars · license n/a
B · leads
89.7
9,761 stars · MIT
meilisearch versus tile38 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; tile38 is written mainly in Go. The composite score is 84.8 for meilisearch and 89.7 for tile38.
meilisearch has 59,885 GitHub stars to tile38's 9,761, a gap of 50,124 (6.14×). Forks are 2,799 for meilisearch and 626 for tile38. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 81.
Push history: meilisearch was last pushed on 17 November 2026 (0 days ago), and tile38 was last pushed on 14 November 2026 (3 days ago). Open issues stand at 318 for meilisearch (0.005 per star) and 165 for tile38 (0.017 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. tile38 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 30 for meilisearch and 96 for tile38. This is a procurement signal, not legal advice.
Only tile38 is marked self-hostable here (9,761 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, tile38 is open source.
The lead is split. meilisearch is furthest ahead on fork community (100 to 81), while tile38 is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
tile38 finishes ahead at 89.7 against meilisearch at 84.8, a 4.9 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 | meilisearch | tile38 |
|---|---|---|
| GitHub stars | 59,885 | 9,761 |
| Forks | 2,799 | 626 |
| Open issues | 318 | 165 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.8 | 89.7 |
A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications.
Real-time Geospatial and Geofencing
meilisearch has more GitHub stars: 59,885 versus 9,761 for tile38. The gap is 50,124 stars.
meilisearch was pushed more recently: 17 November 2026 versus 14 November 2026 for tile38. That is 3 days apart.
Only tile38 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. tile38 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.
tile38 scores 89.7 and meilisearch scores 84.8. This page calls that a narrow lead for tile38.