Meilisearch Problems & Issues
SaasLightning-fast search engine for your apps
Should you use Meilisearch?
TryMeilisearch is worth trying for most users (score 72/100). Most reported issues: Meilisearch Cloud suffers frequent outages; Service jams with large datasets (30M+ docs); Indexing falls behind by 30-50 minutes on updates. Not a good fit for: Companies needing enterprise-grade reliability; Teams with millions of frequently-updated records; Companies requiring per-user permissions. Users most often switch to OpenSearch, Apache Solr, Algolia.
Top problems
- Meilisearch Cloud suffers frequent outages
- Service jams with large datasets (30M+ docs)
- Indexing falls behind by 30-50 minutes on updates
Good for
- Small to medium websites
- Developers who want simplicity
- Budget-conscious startups
Avoid if you are
- Companies needing enterprise-grade reliability
- Teams with millions of frequently-updated records
- Companies requiring per-user permissions
Common alternatives: OpenSearch, Apache Solr, Algolia
Overview
Meilisearch is an open-source, lightning-fast search engine written in Rust. Available self-hosted (free) or via Meilisearch Cloud. Features instant search, typo tolerance, hybrid search with AI, and faceted filtering. Simple setup but struggles at scale with millions of documents and frequent updates.
Signals & Issues
Patterns extracted from real user feedback — not raw reviews.
Multiple G2 reviewers report cloud service reliability issues. One user describes Meilisearch Cloud as 'just a bunch of incompetent people unable to solve any issues' with 'search freezes lasting for three hours frequently.' Cloud resiliency needs significant improvement.
GitHub issue #4438 documents how 'when indexing new documents through the JS API, Meilisearch returns a JSON indicating a successfully enqueued task, but documents may silently fail to index without logging or meaningful response.' No error visibility.
GitHub issue #5180 documents that 'sort order is not working as expected, with results resetting after 4-5 pages.' Pagination with sorting becomes unreliable for users browsing deep into result sets.
GitHub issues report that after importing 30 million documents, 'the service experiences jams three or four times daily, each lasting several to ten minutes, making the service unavailable.' Large datasets require careful management.
Users report that 'despite successfully importing 1 million+ records, Meilisearch doesn't search 9/10ths of the records, searching maybe only the first 100k.' This creates a critical gap where most data is effectively invisible.
For frequently changing data, Meilisearch struggles to keep up. Users report 'updating the index on single events like user starring a post is not effective' with 'the index getting backlogged and behind by 30-50 minutes.' Not suited for real-time update scenarios.
Hacker News users raise concerns about storage efficiency: 'a 10MB document is taking approximately 200MB according to their documentation.' This 20x storage multiplier becomes expensive at scale and limits dataset size.
G2 reviews note 'if you have a lot of traffic, the pricing per search on the cloud can be expensive.' Recent pricing changes have raised concerns, as 'the new pricing model might not feel as fair or cost-effective for those with large indexes but lower usage.'
Users feel 'the dashboard should be more sophisticated to effectively manage indexes.' The dashboard doesn't provide insights on search requests like response times and top queries. Advanced use cases require workarounds or external tooling.
Users report having to 'use workarounds to handle lacking auth/permissions support.' Meilisearch doesn't natively support per-user search permissions, requiring Redis or other tools to manage access control.
What Users Love
Lightning-fast search with sub-50ms response times
Meilisearch delivers exceptionally fast search performance. Users consistently praise 'lightning-fast and highly relevant search results' with typical response times under 50ms. Built in Rust for maximum efficiency.
Extremely easy setup and developer-friendly
Developers love the simplicity: 'seamless integration with Laravel, ease of use, nice cloud dashboard.' Can be set up in minutes with excellent SDKs for all major languages. Documentation is comprehensive and approachable.
Self-hosted is completely free and MIT licensed
Unlike Algolia or Typesense's GPL license, Meilisearch's MIT license provides maximum flexibility. Self-hosted version is 100% free with no limitations. No licensing fees or hidden costs for self-hosting.
Typo tolerance and instant search built-in
Out-of-the-box typo tolerance, synonyms, and instant-as-you-type search work without configuration. Users don't need to worry about misspellings. Makes search feel polished from day one.
Excellent client libraries for all languages
Strong SDKs for JavaScript, Python, PHP, Ruby, Go, Java, Rust, and more. First-party integrations with Laravel, Rails, and other frameworks. Official Docker images for easy deployment.
Hybrid search with AI-powered semantic capabilities
Recent releases added hybrid search combining full-text and AI-powered semantic search. Supports vector embeddings from OpenAI, Cohere, or Hugging Face models. Balances keyword matching with contextual understanding.
Pricing Plans
Users: Unlimited
Storage: Limited by your server
Limitations: No managed hosting, no AI search features, manual scaling required, no analytics dashboard
Users: Unlimited team members
Storage: Based on documents
Limitations: Basic support only, no priority support, limited analytics retention (7 days)
Users: Unlimited team members
Storage: Based on documents
Limitations: No custom SLA without Enterprise, AI features limited
Users: Unlimited
Storage: Based on instance size (XS to 4XL)
Limitations: Self-serve only up to 4XL, larger instances require sales contact
Features
core
- Typo Tolerance
- Instant Search
- Faceted Search
- Synonyms & Stop Words
- Geo Search
ai
- Hybrid AI Search
- Vector Embeddings
security
- Multi-tenancy
integration
- RESTful API
- SDKs for 10+ Languages
Who Should Use This?
Good Fit
Small to medium websites
Perfect for documentation sites, blogs, and e-commerce stores with under 1 million products. Fast setup, excellent search quality, and affordable pricing. The sweet spot for Meilisearch.
Developers who want simplicity
Meilisearch shines for developers who want Algolia-quality search without the complexity. Great SDKs, easy configuration, and instant results make it a joy to implement.
Budget-conscious startups
Self-hosted version is 100% free with MIT license. Can run on modest infrastructure and grow with your product. Cloud pricing is more predictable than Algolia.
Engineering teams seeking DevOps simplicity
Single binary deployment, no JVM tuning, no cluster management. Rust-based efficiency means low resource usage. Much simpler to operate than Elasticsearch.
Neutral
Sales and marketing teams (internal search)
Works well for product catalogs and internal search. Lacks built-in analytics for conversion tracking. May need additional tooling for marketing use cases.
Avoid
Companies needing enterprise-grade reliability
Meilisearch Cloud has reported frequent outages and 'search freezes lasting three hours.' For mission-critical search, consider Algolia or Elasticsearch with proper SLAs.
Teams with millions of frequently-updated records
Indexing falls 30-50 minutes behind with frequent updates. Service jams occur with 30M+ documents. Better suited for static or slowly-changing datasets like documentation.
Companies requiring per-user permissions
No native auth/permissions support. Requires workarounds with Redis or custom middleware. Elasticsearch or Algolia handle multi-tenant permissions better out of the box.
Regret Patterns
Common buyer's remorse scenarios reported by users.
Teams attracted by Meilisearch's simplicity chose Cloud for convenience, only to experience multi-hour outages affecting production search. Wished they had self-hosted or chosen a more reliable managed service.
Started with 100k documents and Meilisearch was blazing fast. As data grew to millions, indexing slowed dramatically and service became unstable. Didn't anticipate scalability ceiling.
Expected Meilisearch to handle real-time updates like user actions or inventory changes. Discovered 30-50 minute index lag making search results stale. Had to implement workarounds or switch tools.
Built multi-tenant app assuming permissions could be added later. Discovered Meilisearch has no native auth/permissions. Had to build custom middleware with Redis, adding complexity.
Didn't realize 10MB of documents becomes 200MB indexed. Infrastructure costs multiplied unexpectedly as dataset grew. Had to provision more disk/RAM than anticipated.
When It Breaks Down
Scenarios where this product tends to fail users.
Service experiences jams 3-4 times daily, each lasting several minutes. Search becomes unavailable during these periods. Meilisearch single-node architecture hits limits. Need to migrate to distributed solution like Elasticsearch.
Index falls behind by 30-50 minutes, making search results stale. Meilisearch optimizes for search speed over index speed. Real-time e-commerce inventory or social media feeds become problematic.
Multi-hour outages impact production search with no fallback. Cloud reliability issues surface. Either need to self-host with proper redundancy or switch to a provider with better SLAs.
Meilisearch has no native per-user or per-tenant permissions. Must build custom middleware layer with Redis or similar. Adds architectural complexity that tools like Elasticsearch handle natively.
Dashboard doesn't show response times, top queries, or detailed metrics. Need to build custom logging and analytics pipeline. Algolia's built-in analytics become appealing.
Alternatives Users Switch To
Typesense
8x mentionedTeams switch for better large dataset handling and replicated cluster architecture. Gain: high availability via Raft consensus, dynamic query-time parameters without reindexing, fixed cluster pricing. Trade-off: GPL license vs MIT, smaller ecosystem.
Algolia
7x mentionedCompanies switch for enterprise reliability and global CDN. Gain: 99.999% uptime SLA, world-class support, comprehensive analytics and A/B testing. Trade-off: Expensive at scale, pricing unpredictable with traffic spikes.
Elasticsearch
6x mentionedTeams switch for true distributed architecture and scale. Gain: horizontal scaling across nodes, battle-tested at petabyte scale, rich analytics. Trade-off: Operational complexity, JVM tuning required, steep learning curve.
OpenSearch
5x mentionedCompanies switch for Elasticsearch-like power without licensing concerns. Gain: 100% open source, AWS-backed development, Elasticsearch compatibility. Trade-off: Same operational complexity as Elasticsearch.
Apache Solr
4x mentionedEnterprises switch for mature, battle-tested search with no vendor lock-in. Gain: decades of production use, extensive plugin ecosystem, free forever. Trade-off: Complex setup, less developer-friendly than modern alternatives.
Frequently Asked Questions
See how Meilisearch compares in our Best Search Software rankings, or calculate costs with our Budget Calculator.
Work at Meilisearch or spotted something outdated? Suggest a correction — we verify every change against public sources. See our methodology.