you are looking for
Performance drives the development of Manticore Search. We are dedicated to achieving low response times, which are crucial for analyzing large datasets. Throughput is also a key consideration, allowing Manticore to handle a high number of queries per second.
faster for big data
than Elasticsearch in the huge dataset benchmark (1.7 billion documents)
faster for Log Analytics
than Elasticsearch in the log analytics benchmark (10M Nginx log records)
faster in big Hackernews benchmark (medium-size data)
than Elasticsearch in the 100M Hackernews comments benchmark
faster in small Hackernews benchmark (small data)
than Elasticsearch in the 1 million Hackernews comments benchmark
Ease of use is our priority
We don’t want Manticore users, whether they be developers or devops, to become experts in databases or search engines, or to have a PhD in order to use Manticore products. We assume that you have other things to do, rather than spending hours trying to understand how this or that setting affects this or that functionality. Hence, Manticore Search should work fine in most cases, even with the default settings.
True open source
We love open source. Manticore Search and other publicly available Manticore products are all free to use and published under OSI-approved open source licences.
Don’t just take our word for it, hear what our lovely users have to say:
We've been using Manticore as a test with great success for the last few weeks. Overall I think 2 - 3 times faster than Elasticsearch for the same operations (6 million records, faceted search over time). Very happy. It also seems fast (both in cpu and memory use) enough that we only really need 1 worker
We’ve chosen this product because of the high performance compared to alternatives, the ability to expand the functionality with help of udf-functions and the availability of SQL-like query language.
We opted to migrate to Manticore instead of upgrading Sphinx since Manticore is open source and better supported. We’re very happy with our decision.
We contacted Manticore’s free support on Slack with questions related to migrating from Sphinx search. In 30 minutes we had the first reply, and a few days later our issue was resolved, and we now using Manticore search to perform over 5 billion queries every day.
Thank you for your help to quickly work through the bug fix. I should have not have surprised at the excellence and prompt nature of the service after working with you last fall on our upgrade from Sphinx, but I didn’t expect the bug to be found, fixed, and the fix to be deployed (with instructions and testing for our specific use case) before I was back in the office the next day. Your professional support has reinforced the value of hiring the developers of specialized software.
We cannot achieve such success without the Sphinx/Manticore search engine! Thank you all for making such a powerful search engine!
We publish books in Chinese for an English-speaking audience and were looking for a way to tokenize Chinese text to create glossaries. We contacted Manticore, got an immediate response from their team, and had our problem solved a couple of days later. Awesome service and great products.
Moving search engine for wine.co.za from Azure to Manticore - was just evaluating Manticore but based on this support I think we will definitely be moving here! Absolutely amazing service from Sergey - sorted out my problems quickly and effectively.
Manticore is a solution that just unloaded our server. Very fast, flexible, excellent and quick support, which allows you to solve problems almost instantly. The only thing missing is Russian-language documentation.
Manticore is a miracle. Just a beast, really! It's amazing that it's free. Thanks to you, my project has the opportunity to develop further. It doesn't make me any money yet, but requires a powerful server. I thought so until I tried Manticore. Where MySQL returns FTS search results in a minute, it returns them in a split second. Moreover, Manticore uses much less server resources. I'm just shocked that my 8 GBs of RAM was enough for me. Also, it greatly simplifies developer's life. I had to use my own PHP tokenizer before, including for the implementation of CJK search. This ugly hack is no longer needed. I always thought that if you won in something, you must definitely lose in something. In the case of Manticore, it doesn't work that way. Here you win literally in everything! Of course, there were difficulties too, and I haven't finished updating the codebase yet. But everything goes to success. This is just a small part of what should be said!
We are one of the largest online stores in Ukraine and we use Manticore in our search. We ordered the Ukrainian lemmatizer, when testing it, we noticed a bug that was quickly corrected by the team. Also further Mnticore team helped us to speed up this lemmatizer with caching and implemented it again in shortest possible time. Many thanks for quick solutions.
Very, very, very fast full-text search for articles on the site and quick search in the admin panel. With stored fields it became possible to let Manticore alone not only search for, but store and retrieve articles without the need to go to a backend database at all.
As a FOSS project, it was essential for us to pick a search engine that we could entirely self-host, and was free since we still have no income :/ a member of the Podcasting 2.0 community (basically the same people who created Podcast Index) told me about Sphinx as a search option, and I found out Manticore was a newer version of Sphinx, so I went with Manticore. I really didn't do much research beyond that. It seemed like Sphinx/Manticore is the leading FOSS option for search so I went with Manticore.