Managed Meilisearch Hosting — production-ready from $15 a month
Lightning-fast, typo-tolerant search engine. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Meilisearch, no lock-in.
Meilisearch on ManageStacks is the open-source instant search engine deployed to your own AWS, Azure, or GCP region — priced flat at $29 per instance per month regardless of document count or query volume, with sub-50ms typo-tolerant search, faceted filtering, tenant tokens for multi-tenant SaaS, and native AI-powered semantic search. Materially cheaper than Algolia at scale (Algolia meters records + operations), and materially simpler to operate than Elasticsearch for product/catalog/docs search.
What does Meilisearch do, and why do teams deploy it?
Meilisearch is the open-source search engine you reach for when you want typo-tolerant, relevance-scored search-as-you-type on a product catalog, documentation site, or SaaS-app search bar — and you don't want to run Elasticsearch. Sub-50ms response times, sensible defaults, and 5-minute integration are the value prop.
It handles typos, synonyms, prefix matching, and natural language queries out of the box; supports faceted search, filtering, sorting, geo search, and custom ranking rules; ships tenant tokens for multi-tenant SaaS; and — as of 2024 — supports hybrid semantic + keyword search using vector embeddings for RAG-style applications.
Client SDKs exist for JavaScript, TypeScript, Python, Ruby, PHP, Go, Rust, Swift, and Dart — plus first-class InstantSearch.js UI components (originally from Algolia, adapted for Meilisearch). Frontend integration is often faster than backend.
- Search-as-you-type with sub-50ms response times
- Typo tolerance, prefix matching, and synonyms built in
- Faceted search, filtering, and custom ranking rules
- Geo search for location-based queries
- Hybrid semantic + keyword search with vector embeddings (2024+)
- Multi-tenancy via tenant tokens with per-tenant scopes
Lightning-fast, typo-tolerant search engine
What does managed Meilisearch hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
Self-hosting Meilisearch vs managed — what does it really cost?
The software is free. The engineer-hours are not.
Running it yourself
- Install Meilisearch on a VM; configure TLS + persistent storage + admin key
- Set up snapshot backups to object storage manually
- Wire in tenant tokens for multi-tenant SaaS by hand
- Handle version upgrades yourself; test each release against your indexes
- Configure embedders for hybrid search separately if you need RAG
On ManageStacks
- Subscribe through your AWS, Azure, or GCP marketplace
- Meilisearch comes up with TLS, admin key, snapshot backups, and monitoring
- Hybrid search embedders (OpenAI, Ollama on same account) available with one config setting
- Rolling version upgrades handled by us with zero-downtime index swaps
- Grafana dashboards ship for search latency, indexing rate, and error rates
Meilisearch on ManageStacks vs the alternatives
How Meilisearch on ManageStacks compares to Algolia and other open-source instant-search alternatives.
| Meilisearch on ManageStacksUs | Algolia | Typesense Cloud | Self-hosted on your VM | |
|---|---|---|---|---|
| Deployment | Managed on your AWS, Azure, or GCP | Vendor-hosted | Vendor-hosted | You provision + operate |
| Data residency | Your cloud region | Vendor region choice | Vendor region choice | Your cloud region |
| Pricing basis | Flat per instance | Per record + per operation | Per node-hour + storage | Your compute cost |
| Typo tolerance | Excellent | Excellent | Excellent | Excellent |
| Open source | Yes (MIT) | No (proprietary) | Yes (GPL, hosted) | Yes (MIT) |
| Hybrid semantic search | Yes (2024+) | Included (Recommend) | Yes | Yes |
Provisioning, upgrades, backups and monitoring on your team’s plate.
What does running Meilisearch yourself involve?
ManageStacks deploys Meilisearch with persistent storage, TLS, an embedder configured for hybrid semantic + keyword search (if you want it), and Prometheus-based monitoring. We handle version upgrades, snapshot backups, and reindexing operations — you focus on document schema and relevance tuning.
Meilisearch key numbers
How long from subscribing to a live instance?
Subscribe
Subscribe to ManageStacks through your AWS, Azure, or GCP marketplace.
Provision
Meilisearch spins up with persistent storage, TLS, admin key, and Grafana monitoring — typically 3-5 minutes.
Index documents
POST documents to your index via the REST API or the client SDK for your language. Meilisearch auto-detects searchable attributes.
Integrate + search
Add InstantSearch.js components to your frontend, or query via SDK. Configure tenant tokens for multi-tenant SaaS.
When is self-hosting Meilisearch the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Meilisearch at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Meilisearch run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Meilisearch in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Meilisearch on ManageStacks
How does this compare to Algolia?
Algolia is priced per record + per operation ($1 per 1,000 records/month + $0.50 per 1,000 operations at Standard tier). ManageStacks Meilisearch is flat $29 per instance regardless of records or ops. For sites beyond ~100k records or high-query-volume sites, self-hosted Meilisearch is materially cheaper — often 10-30x. Algolia wins on the vendor's rules engine, DashboardUI polish, ML-powered relevance, and marketplace integrations. Meilisearch wins on data ownership, flat pricing, and self-hosting flexibility.
How does this compare to Typesense (another Algolia alternative)?
Both Meilisearch and Typesense are excellent open-source Algolia alternatives with similar goals. Meilisearch is written in Rust and has stronger typo tolerance out of the box; Typesense is C++ and has better raw performance per CPU. Feature sets are largely comparable. Pick Meilisearch for stronger DX and default relevance; Typesense for extreme-scale needs and simpler operational model.
Can I use Meilisearch for RAG applications?
Yes — Meilisearch supports hybrid search (semantic + keyword) using vector embeddings. Configure an embedder (OpenAI, Ollama, HuggingFace, or custom), and Meilisearch handles the embedding-generation and hybrid ranking. For pure vector search at scale (millions of vectors, no keyword component), Qdrant is a better fit; for hybrid retrieval, Meilisearch is often simpler.
How does Meilisearch handle multi-tenant SaaS?
Tenant tokens are Meilisearch's built-in multi-tenancy primitive — signed JWTs that constrain queries to specific filter expressions. Each tenant gets a scoped token; the frontend uses it directly; Meilisearch enforces the filter server-side. No per-tenant index needed for simple cases.
Does ManageStacks handle Meilisearch version upgrades?
Yes. Meilisearch ships frequent releases; we test each one and validate against your indexes before rolling forward. Zero-downtime index swaps preserve search availability during reindexing.
How is backup handled?
Meilisearch's snapshot format is a portable, self-describing archive. Daily encrypted snapshots stored in a separate region. Restore any snapshot to any Meilisearch instance.
What if I want to migrate off?
Snapshot format is portable to any Meilisearch instance. Or re-index into Typesense, Elasticsearch, or Algolia — data is just your JSON documents. Meilisearch is MIT-licensed and portable. Migration off is a supported operation.
Run Meilisearch without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $15/mo.