Comparisons
Self-hosted Meilisearch vs Meilisearch Cloud: when each one wins
Self-hosting Meilisearch means you run the open-source engine on your own infrastructure — full control, near-zero recurring cost, full operational responsibility. Meilisearch Cloud is the official managed service from the Meilisearch team — zero ops, predictable bill, less control. Both run the exact same open-source engine; the difference is who carries the pager.
The 30-second answer
- Self-host if you have an engineer who can run a Linux service, you want predictable infrastructure costs, your data must stay in a specific region, or you need to peer your search engine with private services.
- Use Meilisearch Cloud if you want SLAs, zero-touch upgrades, automatic backups, and you're fine spending $30–$200/month per project to skip the operational work.
Side-by-side comparison
| Concern | Self-hosted | Meilisearch Cloud |
|---|---|---|
| Engine | Same open-source Meilisearch | Same open-source Meilisearch |
| SLA | None — yours to define | 99.9% on Pro plans |
| Backups | You configure dumps + snapshots | Automated daily backups |
| Version upgrades | You schedule them | Handled for you |
| Scaling | You provision the box | Click to scale up/down |
| Network isolation | Your VPC, your firewall | Public internet by default |
| Cost (small project) | ~$5–20/month VPS | $30–100/month |
| Cost (large project) | ~$80–200/month dedicated server | $500+/month |
| Time to first index | ~30 minutes | ~5 minutes |
| Multi-region replication | You build it | Available on enterprise tiers |
When self-hosting is the right call
1. You already run other services
If your team already operates Postgres, Redis, or any other stateful service in production, adding Meilisearch is a marginal cost. The skill investment is amortized across other services.
2. Data residency or compliance
If your data must stay in a specific country, a specific VPC, or behind a specific firewall, self-hosting is the only option. Meilisearch Cloud regions cover the major cloud providers but not every jurisdiction.
3. Cost predictability at scale
Self-hosting flat-rates the bill at "the cost of one server" rather than scaling with documents and queries. For workloads with millions of records and millions of searches, the gap is significant.
4. Network peering with private services
If your application needs to talk to Meilisearch over a private network (VPC peering, internal load balancer), self-hosting is required. Meilisearch Cloud is reachable over the public internet.
When Meilisearch Cloud is the right call
1. You don't have a DevOps engineer
If nobody on your team wants to learn the operational side of running a database service — backups, monitoring, version upgrades, capacity planning — Meilisearch Cloud removes all of it. You pay for that removal, and it's worth it for many teams.
2. You need an SLA
Self-hosted means there's no contractual guarantee anyone will fix the search engine if it goes down at 3am. Meilisearch Cloud's Pro tier includes a 99.9% SLA with credits for breaches.
3. Your project is small enough that the cost gap doesn't matter
For a small project (one index, low traffic), Meilisearch Cloud's $30/month tier is cheaper than the operational time cost of doing it yourself.
The hybrid approach: self-host + a managed dashboard
A common middle ground is to self-host Meilisearch (for cost + control) but use a third-party operator dashboard for the day-to-day work. AdminDex exists for exactly this — it gives you the visual settings editor, API key manager, task viewer, and operator UI that Meilisearch Cloud ships, but pointed at your own self-hosted server. Best of both worlds: you keep the data and pay $0–10/month for the engine, and you pay AdminDex for the management layer.
Migration cost
Moving between self-hosted and Meilisearch Cloud is easy in either direction:
- Run
POST /dumpson the source instance. - Copy the resulting dump file to the destination.
- Run
POST /dumps/importon the destination.
Index settings, documents, and API keys all transfer cleanly. Allow ~10 minutes for a small dataset and up to an hour for a multi-GB index.
FAQ
Can I migrate from Meilisearch Cloud to self-hosted later?
Yes, easily. Use the dump endpoint on Meilisearch Cloud to export everything, then import it into your self-hosted instance. The engine is identical so there's no compatibility risk.
Does self-hosting Meilisearch work behind a corporate firewall?
Yes — that's actually one of the main reasons people self-host. You can run Meilisearch on a private VPC with no public access at all, peered with your application servers.
Is there a free tier of Meilisearch Cloud?
Yes, the Build plan starts at $0/month with limits on documents and search volume. Beyond the free limits the Pro plan starts around $30/month.
How does AdminDex relate to Meilisearch Cloud?
AdminDex is a third-party dashboard for self-hosted Meilisearch instances. It is not affiliated with Meilisearch Cloud. We don't host Meilisearch — we manage the Meilisearch you already run yourself. See our FAQ for more.
Stop running Meilisearch from a terminal.
AdminDex gives you a visual dashboard for every Meilisearch instance you own — settings, API keys, tasks, and search analytics.
Related reading
-
Meilisearch vs Algolia in 2026: a developer's comparison
Side-by-side comparison of Meilisearch and Algolia for SaaS search in 2026 — pricing, features, hosting model, and when each one wins.
-
How to deploy Meilisearch on Docker in 5 minutes
Step-by-step Docker deployment of Meilisearch with persistent storage, the master key set as an env var, and HTTPS via a reverse proxy.
-
Meilisearch admin key security: a complete guide
How Meilisearch admin keys work, what scopes you can grant, how to rotate them safely, and the operational best practices for treating them like production secrets.
Spotted an inaccuracy? Email the AdminDex team →