← Meilisearch for WordPress: A Complete Guide
Should you self-host or use Meilisearch Cloud?
Self-host if you’re comfortable owning a small VPS and want the lowest flat cost. Use Meilisearch Cloud if you’d rather pay a managed tier and skip the server, backups, and updates entirely. Both run the same search engine; the difference is who’s on call when it goes down.
What self-hosting involves
Installing Meilisearch is a single binary:
curl -L https://install.meilisearch.com | sh
sudo mv ./meilisearch /usr/local/bin/
meilisearch --master-key="your-master-key" --db-path /var/lib/meilisearch/data
That’s the easy part. Running it in production means a systemd service so it survives a reboot, Nginx (or another reverse proxy) in front of it with SSL, and a backup plan for the data directory, since your index is the only copy of your search data unless you rebuild it from WordPress. Updates are your responsibility: new Meilisearch versions ship regularly, and you decide when to apply them. Uptime monitoring matters too, since a down search server means broken search on your live site, not a graceful fallback.
84EM operates self-hosted Meilisearch for production WordPress sites, including a high-performance directory site serving thousands of listings. The ops burden is real but manageable once it’s set up correctly.
Meilisearch Cloud: what you pay for
Meilisearch Cloud is Meilisearch’s own managed option: they run the instance, handle updates and backups, and you get a hosted endpoint instead of a server to maintain. It costs more than a bare VPS, but it removes the operational burden above entirely. For a team without the appetite to run infrastructure, that trade is often worth it.
Security and access
A self-hosted instance needs at least two API keys: an admin key that can write to the index (used only by your WordPress indexer, never exposed to the browser) and a read-only, search-scoped key for the frontend. Meilisearch’s tenant token system lets you scope keys tightly, so a compromised frontend key can’t modify your index.
Network access matters too: the Meilisearch port shouldn’t be open to the public internet directly. Put it behind a reverse proxy, restrict admin-key traffic to your WordPress server, and treat the master key the way you’d treat a database root password.
When to hand it off
Self-hosting is worth reconsidering the moment nobody on your team has time to watch for updates, respond to an outage, or rotate a compromised key. That’s not a reason to avoid self-hosting, it’s a reason to have someone accountable for it. See Meilisearch pricing vs Algolia for how the ops cost factors into the total price comparison.
84EM’s maintenance and security support covers exactly this: monitoring, updates, and incident response for infrastructure like a self-hosted Meilisearch instance.
