MeiliSearch and Skryx are conceptually very close. The request shape is similar, the defaults are similar, the philosophy is similar.
# Concept mapping
| MeiliSearch | Skryx |
|---|---|
| Master/admin API key | index:admin scoped key |
| Search-only key | search scoped key |
| Index | Index |
searchableAttributes |
query_by |
filterableAttributes |
Schema fields with facet: true |
sortableAttributes |
Schema numeric fields |
rankingRules |
Skryx ranking rules (boost / pin / hide) |
# Why move
- AI features included — query understanding + search coach, no DIY.
- Auto-sync data sources.
- Hosted, EU-resident, multi-tenant from day one.
# What stays the same
- Typo tolerance defaults (Skryx uses the same
min_word_length_for_1_typo/2_typosshape). - Faceting semantics.
- Synonyms (multi-way + one-way).
If your team already operates MeiliSearch and the SaaS angle is what's drawing you, the migration is the cheapest of any source — most queries translate one-for-one.