Algolia Reviews

I used Algolia in a project where we built a real-time monitoring dashboard for IoT devices using React for the front end, FastAPI for the back end, and MQTT for handling data streams. Everything was in live mode, and we used web sockets in the FastAPI. We used Algolia to index device data and enable fast search and filtering of devices, logs, and events. These IoT devices were generating a large amount of data, reaching 10,000 data points in a second, so we needed a search device with indexing. This allowed users to quickly find specific device data and data points in real time without querying the back end directly for their requests.

Algolia provides extremely fast search performance, which is particularly useful for projects with big data and many data points. In my use case with IoT devices, I really needed fast search for specific data points. One of the best features is easy API integration. It was not difficult to integrate our back-end API to the search engine, which allowed us to implement real-time search functionality with minimal effort.

The positive impact of Algolia on my organization was significant because it helped us reduce the back-end load. When you have a large amount of data, it is very difficult to maintain, especially when customers need to search in real time. It saved the search performance significantly. Also, it helped save development time by avoiding the need to build a custom search system, which improved the user experience.

One area for Algolia's improvement is the relevance of tuning and configuration because it can take some time to properly configure ranking and filtering for a specific use case. If you are new to this or do not have experience with the tuning and configuration of the search, that can take some time to adapt and use this search engine.

To make it better, I would appreciate improvement in the relevance of tuning and configuration, as it takes time to properly configure ranking and filtering. I can also say that transparency for scaling usage and cost transparency for when you are scaling would be beneficial.

I have used Algolia in my project a few months ago.

Algolia is very stable. Search queries are consistently fast and reliable, even with real-time data updates.

Algolia scales very well. As the amount of indexed data grows, it continues to provide fast search performance without noticeable delays.

Customer support is good, but most of the time, documentation and guides were sufficient for implementation.

Previously, we relied on back-end database queries for search. We switched to Algolia to improve the performance and provide a better real-time search experience.

The API integration with Algolia was straightforward. It was not difficult, and we did not spend a lot of time figuring out how to do it.

The return on investment was positive because it decreased the development time. We did not need to create our search engine, and we avoided hiring more back-end developers since we could use this ready, specific solution. I believe we saved development time and did not hire additional back-end developers, so we potentially saved around 700-800 euros.

I found the pricing reasonable, especially at the smaller scales, but of course, it can increase as usage and the data volume grow.

We considered implementing search directly in the database but chose Algolia for better performance and scalability.

Algolia is a great solution for fast search, but it is important to plan the indexing strategy and manage usage to control costs. I would rate this review at a seven out of ten.

Our main use case for Algolia is powering our website's product search, and it helps customers instantly find relevant items, even with partial queries.

Algolia solved a unique challenge for us by handling typo tolerance, allowing our customers to still find what they need even with misspellings, which also improved the user experience.

The best features Algolia offers are its blazing-fast search speed and the extensive customization of ranking rules, which allows us to fine-tune results exactly how we want.

We fine-tune results by boosting popular products or recent arrivals. For example, during a sale, we prioritize discounted items at the top, giving users quicker access.

Algolia's analytics is a feature I would like to highlight, as it helps us understand what users search for, allowing us to continually improve the experience.

Algolia has significantly improved our user experience, and we saw search conversion rates increase by around 15% after implementing it.

We measure the increase by tracking search click-through rates and purchases originating from search queries. After implementing Algolia's relevance tuning, we noticed a clear uptick in users finding and purchasing products faster.

One improvement I suggest for Algolia is offering even more granular control in the dashboard for A/B testing and search configurations, which could help refine relevance more quickly.

Pricing can be steep as usage scales up, so a more flexible or transparent tiering model might help.

I would like to suggest having more detailed cost prediction tools so teams can forecast usage scaling more precisely.

I have been working in my current field for more than five or six years.

Algolia is very stable for us, and we have not encountered any major downtime issues. It is consistently reliable in production.

Algolia scales beautifully. As our catalog and traffic grow, it handles the increase effortlessly while maintaining fast search performance.

Customer support is great, as they have been prompt and helpful whenever we need assistance, making the experience smooth.

I would rate customer support a nine because they are responsive and knowledgeable whenever we reach out.

We previously used a basic in-house search solution, and we switched to Algolia for its speed and scalability along with far more advanced relevance tuning.

The setup was smooth, and pricing was transparent initially, but as usage scaled, we had to carefully monitor costs, which makes it important to keep an eye on usage drivers in this tool.

We did not purchase Algolia through the AWS Marketplace. We subscribed directly with Algolia's own platform.

I have seen a strong ROI after implementing Algolia, as we reduced search-related customer support tickets by around 25%, saving time and improving efficiency.

Pricing can be steep as usage scales up, so a more flexible or transparent tiering model might help.

I would like to suggest having more detailed cost prediction tools so teams can forecast usage scaling more precisely.

Before choosing Algolia, we did not evaluate other options specifically. We used basic in-house solutions a long time ago.

I advise others to start with a clear idea of their search goals, as Algolia is powerful, but turning it to match your users' needs is key to getting the most out of it.

Algolia has solid governance and security features. We have tested it with our search data, and it has been compliant with industry standards, so we feel confident in its protection.

Algolia's AI-driven relevance has been very reliable for us, consistently delivering accurate search results, making it easier for users to find exactly what they are looking for.

I would rate this review a nine overall.

Algolia powers the font search browse experience at Monotype, where users can search by font name, style, classification, designer, foundry, and faceted filtering with typo-tolerance, and it possibly powers font recommendations or similar font features.

At Monotype, I use Algolia primarily to power our font discovery experience, as we have a catalog of thousands of fonts and needed users, designers, brand teams, and agencies to find the right typeface fast. I am involved on the data side, making sure our font metadata is properly indexed in Algolia—things like font name, classification, weight, language support, foundry, and licensing info. We have to sync data from our external systems into the Algolia index so the catalog stays relevant.

Algolia's search is incredibly fast. Typo-tolerance is great for font names; designers misspell things such as Helvetica Neue all the time. Faceted filtering lets users narrow by style, weight, and language support seamlessly. Ranking customization is useful, allowing us to boost commercially important fonts.

Algolia's best features include search performance, typo-tolerance, faceted filtering, custom ranking, instant search UI libraries, dashboard, A/B testing, and easy onboarding.

Typo-tolerance and faceted filtering in Algolia are crucial; you do not realize how much you need them until you have them. Our users are mostly designers and creative professionals who search for font names in French, German, or made-up words. Names such as Frutiger, Baskerville, Neue, Haas, and Grotesk are frequently misspelled. Before Algolia, a misspelled search just returned zero results, and the user bounced. With Algolia's typo-tolerance, someone can type Frutiger Baskerville and still land on the right font. We do not have to maintain a synonyms list or build custom fuzzy matching; it just works out of the box. That alone likely reduces our zero results significantly. For faceted filtering, font discovery is inherently a browsing experience. A designer might come in knowing they want a sans-serif, bold weight, with Cyrillic language support. Faceted filtering gives them that drill-down experience where each filter instantly narrows the results and updates the available options, with real-time count updates. If you select sans-serif, you see immediately how many fonts are available in each weight category. Users never hit dead ends, making the whole experience feel responsive and guided rather than just a dumb search box.

Synonyms and relevance tuning are good features. We set up synonyms so if someone searches 'Gothic', they also get results tagged as 'sans-serif' since in typography, those terms overlap, along with other terms such as handwritten and script. Algolia makes the configuration straightforward; just rules as code, no code deploys needed. For speed of iteration, I appreciate how fast we could experiment with changing ranking rules, adding a new facet, and tweaking relevance. These are few-click configurations, not engineering sprints. Our product manager can go into the dashboard and adjust how results are ranked. Regarding geo and personalization, we did not go deep into it, but Algolia supports geo-based personalization and search. Algolia is basically a 'just works' option for search. The tradeoff is cost at scale, but for getting a polished search experience live quickly without a dedicated search team, it is hard to beat.

Algolia has positively impacted our organization by allowing us a faster time to market. Before Algolia, building a decent search experience meant setting up and maintaining Elasticsearch, hiring someone who understands relevance tuning, and spending months getting it right. With Algolia, we have a production-ready font search live in weeks. That frees up engineering time to focus on the actual product instead of infrastructure, resulting in better user engagement, reduced engineering burden, and empowering non-engineering teams.

The cost scales aggressively as the record count and search operations grow. Keeping the index in sync with our source of truth incurs friction. We build custom pipelines to handle incremental updates cleanly. The analytics dashboard is decent but not deep enough for the product team's needs, so we end up piping data from somewhere else.

Algolia can be improved in terms of pricing transparency and scalability. The biggest issue is cost; Algolia gets expensive fast as your record count and search operations grow. The pricing tiers feel like a cliff. Regarding index syncing and data pipeline support, keeping the index in sync with our source of truth has been more painful than it should be. We have built a custom pipeline to handle incremental updates, deletions, and schema changes. If Algolia offered native connectors or better CDC support, such as a direct integration with a database or change stream, that would save a lot of plumbing work. Additionally, the analytics depth needs improvement; the built-in analytics is decent for surface-level insights such as top searches and click-through rates, but for deeper analytics, such as understanding search journeys, segmenting user types, or correlating search behavior with conversion, we had to pipe events out to our own analytics stack. We need that, along with better documentation and query language flexibility.

I have been using Algolia for two years.

Our average search response has dropped to under 50 milliseconds. Previously, with our homegrown solution, it was closer to 300 to 400 milliseconds. That might sound small, but users feel the difference; search feels instant instead of sluggish. We cut our zero-result searches by 40 to 50%, mostly due to typo-tolerance and synonyms doing the trick. Before Algolia, a misspelled font name was a dead end. After, those queries return the right results. Fewer dead ends mean fewer bounces. For engineering time saved, I estimate we saved two to three engineering months per quarter that would have gone into maintaining and tuning a self-hosted search solution. For conversion, while we did not conduct a perfect A/B test after the launch, we saw a rough 15 to 20% uplift in users from searching to font preview pages. We also increased the product team velocity.

Model your cost early. Invest time in your data model upfront and get your data sync strategy right from day one. I would rate this solution an 8 out of 10.

My main use case for Algolia revolves around search functionality on listing pages, where users search for items using keywords and filters. For example, when a user types something such as iPhone, Algolia is responsible for instantly returning relevant results with features such as typo tolerance, ranking, and filtering, such as price range or category. From my QA perspective, I validate that the correct results return for different queries and that the filters behave correctly. I also automate these scenarios using Playwright, where I validate dynamic search results and ensure consistency in API responses. Overall, it is a very critical user-facing use case where both performance and accuracy matter greatly.

One important aspect is how real-time and dynamic the search behavior is, which makes testing slightly challenging but also interesting. I also worked on validating the indexing pipeline, ensuring that whenever new data was pushed from backend systems, it was correctly indexed and reflected in search results without delay. Beyond basic search validations, there is a lot of focus on speed, accuracy, and real-time accuracy, making it a critical component to test.

Algolia has had a noticeable positive impact on our organization, especially concerning engineering efficiency and user experience. From an engineering and QA standpoint, it simplifies many processes due to being API-driven and well-documented, making it easier to validate search behavior independently at the API level. This ease of validation aids in automating end-to-end flows on UI, allowing us to automate both API and UI separately, thus increasing our test coverage and confidence significantly, which boosts release confidence.

We have observed tangible improvements integrating Algolia, albeit with roughly one year of usage, so exact metrics are limited. One clear outcome I can mention is a reduction in search-related production bugs, which our team has significantly noticed in inspections. The number of bugs related to search queries has decreased greatly due to the smoother filtration logic and search IDs after integrating with Algolia. Previously, when the search logic was more custom-built, we encountered issues with incorrect results, slow responses, and edge cases failing. Now, those bugs have noticeably reduced, estimating a 25 to 30% drop in search-specific issues over several releases, though this data is rough.

In my opinion, the best features Algolia offers include instant search performance and filtering capabilities. Instant search performance stands out, as the response time is extremely fast, almost real-time as you type, which enhances user-friendliness but presents challenges for testing due to dynamically updating results. The filtering feature allows users to refine results based on categories, price, or other attributes, making it especially useful for e-commerce websites such as Amazon, Myntra, or Flipkart.

Customization is a useful feature, as Algolia provides insights such as top search queries, no-result searches, and user interaction patterns. These insights help QAs gain perspective since we can identify real user scenarios and engage in data-driven testing, ultimately providing our clients with the best products.

There is definitely room for improvement within Algolia, despite my positive experience. One major area for improvement is pricing transparency and cost control. As usage scales, particularly with high query volume and frequent indexing, costs can increase rapidly. This makes it challenging for QA engineering to predict or optimize costs, so better visibility would be beneficial. Additionally, handling non-deterministic results due to typo tolerance and ranking can be tricky; thus, improved methods for simulating specific behaviors in lower environments such as staging would enhance predictable testing reliability.

Debugging is an area worth addressing. While Algolia offers logs and analytics for issues such as unexpected ranking or missing results, pinpointing exact causes can be time-consuming. More detailed debugging tools or clearer traceability would be useful. Another improvement I can think of is enhancing the alerting and monitoring mechanisms. Proactive alerts on failed indexing jobs or sudden drops in search relevance could help teams react faster, preventing small production bugs from escalating into bigger issues.

I have been using Algolia for roughly one year in my recent projects.

Regarding stability, Algolia has been quite stable in my experience, with rarely any downtime or major disruptions. Search responses remain consistently fast, even under high loads, making stability one of its strong points for us.

Scalability is indeed one of Algolia's strongest areas, managing high query volumes and data scaling seamlessly without our needing to manage infrastructure. For instance, during peak traffic scenarios such as the Diwali sale event, Algolia effectively handled a significant spike in search queries without any noticeable degradation in response time, proving its reliability in scaling for both users and queries.

While Algolia offers logs and analytics for issues such as unexpected ranking or missing results, pinpointing exact causes can be time-consuming. More detailed debugging tools or clearer traceability would be useful. The response quality from customer support is generally good, but I have not personally interacted with customer support.

Before switching to Algolia, we primarily used a custom-built search solution, partly backed by traditional database queries and, in some cases, Elasticsearch. The challenges with that setup involved performance tuning and relevance management, necessitating considerable manual effort from the engineering side and producing inconsistencies and edge case failures. Additionally, transitioning from Elasticsearch versions added to QA efforts. However, after adopting Algolia, we found it easier to scale and maintain low latency.

My experience with pricing, setup cost, and licensing for Algolia is mixed. The initial setup is quite straightforward with no heavy infrastructure cost or long setup time, as it is a SaaS product, allowing me to get started swiftly with minimal overhead. However, pricing can become a concern at scale, especially since Algolia follows a usage-based model based on the number of search operations. Given our client-heavy application, it becomes quite pricey, although I am not directly involved in pricing strategies, merely an individual contributor using these technologies to generate results. Thus, while setup costs are low and onboarding is easy, we need to plan for long-term price scalability carefully.

The initial setup is quite straightforward with no heavy infrastructure cost or long setup time, as it is a SaaS product, allowing me to get started swiftly with minimal overhead. However, pricing can become a concern at scale, especially since Algolia follows a usage-based model based on the number of search operations. Given our client-heavy application, it becomes quite pricey.

Before choosing Algolia, we evaluated several alternatives, mainly Elasticsearch and managed solutions such as Amazon OpenSearch Service from AWS. While Elasticsearch provided flexibility, it came with higher operational overhead, requiring continuous effort in cluster management, scaling, and relevance tuning. This also complicated testing due to behavior being heavily influenced by configurations. Compared to these, Algolia's fully managed service, speed, ease of integration, and robust out-of-the-box features made both development and testing more streamlined.

My best advice for those considering Algolia is that it is scalable, so proper planning of data and indexing strategies from the beginning is essential. As search relies heavily on data structure and indexing, investing time upfront saves much effort later in tuning and testing. Additionally, it is crucial to monitor usage and costs since pricing is usage-based; optimizing queries and avoiding unnecessary calls is important. From a testing standpoint, I recommend building a solid suite of API-level validations in conjunction with UI automations because search behavior is dynamic and requires comprehensive coverage across layers.

Algolia is a mature, reliable, and high-performance search solution that significantly enhances user experience, especially in applications where search and discovery are critical. From a QA perspective, its API-first design, speed, and consistency facilitate validation and automation compared to many custom-built solutions, making it a strong choice for teams eager to implement an efficient and scalable search solution without the burden of heavy infrastructure investment. I would rate my overall experience with Algolia as an 8 out of 10.

My main use case for Algolia is to render the product listing page based on AI suggestions and the use of components provided by Algolia, specifically React components and the filters that come along with it.

A specific example of how I used Algolia in one of those projects is when we wanted to have a product listing page with very optimized search capabilities. For that, we decided to go with Algolia. The implementation involved installing the package in the Next.js codebase, and then using the React components already provided by Algolia documentation. We integrated it for the PLP. The sidebar, which is the filter section, the product listing data being provided, and all those features were used from Algolia.

The best features Algolia offers in my experience include the intensive, intelligent search that it provides, which is the one feature I really appreciate. Second is the filters that it provides; all the filters are pre-populated, and based on selections, it also gives you options whether a filter is valid or not. Invalid filters are removed, which is really important for a product listing page. Additionally, when we do a search related to any products, we can define the terms for which it can be searched, making it feel advanced search capability. These are quite useful features for Algolia.

Algolia has impacted my organization positively in a good way, as it has shaped the product and it feels as though the product has a premium search engine behind it. Since not all commerce platforms' search engines are as good as Algolia provides, this really takes the experience of users or customers to a different level.

As of now, I can suggest that the search part is already working very well, but if Algolia could incorporate more human language features, that would be beneficial. Nowadays we are in the era of AI, so AI is useful everywhere. If integration could increase on the AI part or create something like a microphone feature whereby a user can simply explain what they want, and Algolia can apply some key terms from that voice conversation and then filter out the terms. For example, if someone says 'I want to design my hall,' this is a very vague requirement from the user. However, how would Algolia be able to understand that when someone wants to design a hall? If they want to ask certain further questions, they can do so, or they can simply put some filters on and display all the results related to something they can use in the hall. This is something we are already using with LangChain and different tools in multiple platforms, but if Algolia could provide such a thing, that will be a really great added advantage.

Integration-wise, I think it is good; we do not need more help there. UI-wise, if Algolia could provide more design customization options, better than what it is right now, I think that will be all. I do not think there is more needed from Algolia. It is already a good tool, but since it is more or less concerned with refinements, I would say if Algolia could introduce the features I discussed earlier, it will be a really great addition to its current feature list.

I have been using Algolia on project basis. So, so far I have used Algolia in two projects.

In my experience, Algolia is stable.

Algolia is scalable because I can easily implement this, and I can always add more products to it. We were already using 1,000-plus product items in Algolia, and whenever it was required, we kept adding and reducing them. When we deployed using Algolia, it totally takes care of the load; it acts as a microservice because it is a service itself. We have integrated it, and whatever load it needs to take, it handles that and always returns the required values, so it is really good.

I have never used customer support, so I am not certain, but I believe their documentation is good enough.

I have been using Einstein Search, which is provided by Salesforce Commerce Cloud in the environment, and the reason for switching is obvious because we were in the Salesforce Commerce Cloud, so Einstein is an in-built AI tool for that.

In order to implement Algolia, we had to upload data into Algolia first, so the first thing was that we connected our PIM to Algolia. For that, we used Lambda services, AWS Lambda. Once that was connected, the data was pre-populated in the Algolia setup, and based on that, this was all accomplished.

Time is definitely saved with Algolia; any tool such as Algolia can save a lot of time in implementing the PLP and providing value to the product. I cannot say that fewer employees were needed because it is not such a big feature that requires reducing headcount. However, it is a good addition to what we are using, and Algolia's features have been useful for the product. A digital commerce or commerce storefront application does not only have one part of it, which is search; it has multiple things to be done. When it comes to search and optimization in the search field, Algolia has really stood out, making a difference. However, we cannot say that it helps in reducing headcounts or employees.

Regarding pricing, setup cost, and licensing, this was something above my pay grade, but I have used other tools in my personal capacity, and I believe that Algolia could be better economically. It should work in a way whereby you can provide better pricing patterns. I am really not the right person to talk about licensing.

I have evaluated other options, but I really cannot recall the names of the products at this time.

Algolia has impacted my organization positively in a good way, as it has shaped the product and it feels as though the product has a premium search engine behind it. Since not all commerce platforms' search engines are as good as Algolia provides, this really takes the experience of users or customers to a different level.

Out of those features, I find myself relying on the search part the most day-to-day. When we want to search, users do not usually know what they want in the first go. When you are on a PLP or even on the homepage, we can put a search bar there and the user can directly start searching something which feels natural and conversational. Algolia very gracefully handles this and provides the data or products which are matching with those searches, so this is really one of the best features that Algolia provides.

My advice to others looking into using Algolia is to go through the documentation. I would also ask them to first understand Algolia more than doing a small proof of concept before first-hand implementation. That will really help them to brush up their skills and they will be able to implement it properly on their project. I am speaking from a developer's point of view, but from marketing, sales, or the user's perspective, I would say if we are working outside of something like Salesforce, we can definitely use Algolia as a platform. We have to look into the pricing because Algolia is, I believe, a bit costly in terms of long-term use; they will have to consider that factor as well. I gave this review a rating of nine out of ten.

I like to describe it as an embedded Google that you can tailor with your own information. You can input your proprietary information and modify the weights and configuration of the search to tailor the results for your clients or services, like for internal tooling.

I can have a built-in flexible search engine. We used it specifically to return results to our clients in terms of listings based on their search and geographic location.

I like the fact that it's very powerful. It has many fine-tuning configurations. Essentially, every single piece of information you pass through it is a free document you can tailor. This allows me to craft the information in a manner that it can be easily searched.

For example, with our listings, we tailored them based on the individual's name, geographic location, and information specific to us, such as access to golf clubs and tennis courts. This very narrow information could then be used as part of the search results, providing our clients with a very intuitive search service.

The idea is that good search results lead to better commercial opportunities and customer retention because clients are satisfied with an easy-to-use service. That was definitely the greatest aspect of Algolia - it's a very powerful search engine.

There are two problems. Number one, it's a bit pricey, especially when there are similar algorithms. There's one called Typesense, which we considered to lower our bill. Algolia is good for a startup because it allows you to bootstrap powerful functionalities quickly. But if that startup ends up growing and becomes quite successful, the cost of Algolia will balloon with it. So, I could imagine that Algolia might have difficulty retaining clients.

The other problem I had to deal with as the lead software engineer is the documentation. I was basically assigned a guy who had no idea how Algolia works, and I had to get it to work, which I did. But the documentation for the service is not as good as it could be. You can still figure it out, but Algolia has a lot of functionalities, not just the search engine. They have built-in components for different UI libraries. In our case, we were using React, and they have a third-party library that you can import to use Algolia services as React components. 

It's great, but they have very little documentation for those kinds of third-party things. It's tough to use them if you don't explain to your potential developers how they're supposed to be used. I eventually had to call them directly and sit down with their engineers, and I realized that it's a great product, but they need to explain it better.

I used Algolia as an embedded search engine. I was the lead software engineer for a US-based startup called Teach Me To, based in San Diego. I used it throughout my entire stay with the company, which was seven and a half months.

Algolia is a powerful framework, so there are many ways the setup could have suboptimal results, and we actually experienced them. It's not 100% their fault; it was more about how we were integrating the program. For example, we were trying to return search results based on geographic location and put that on a map. We realized there were a lot of duplicate returns, with the same listing being returned as part of a big block of results. We didn't catch it because the pins on the map would overlap, so we would only see one pin when there were actually two of them.

The problem is that Algolia works like any cloud technology in terms of use. We were getting a bunch of redundant results that were nonetheless part of the billing because the configuration of the platform was wrong. That was part of my reason for fixing things that happened. It wasn't necessarily something wrong with Algolia, but rather with our integration of it. However, it's the kind of pitfall that developers should be aware of.

I would rate the stability an eight out of ten.

I believe the technology is scalable, but I have doubts as to whether the billing is scalable for any company. If you're a big, successful startup transitioning into a corporation, you might have the resources to build your own internal search engine because Algolia can get expensive unless they adjust their pricing.

I'm very happy with it. I would give them ten out of ten. They were responsive, active, and even followed up to see if everything was okay and if we needed more support.

The initial setup is fairly easy. It's not trivial, but it's not hard either. There are two sides to it:

1. the application side and
2. the cloud information side.

You have to make sure your information is correct on the cloud side to see it reflected on the application side. It is not 100% easy, but it is not necessarily hard because any good developer should be able to handle it.

Deployment time: It depends on the amount of data. They do have to index the information, so if you have less than a hundred thousand entries, it should be super quick. They have a great capability that allows you to demo it on a test set so you don't mess with your real-time production information. You can play around with Algolia on a development set and then pass it into production when you're ready.

However, if you have a lot of indices, let's say a million or more, it does take a couple of minutes to pass that information into the system, index it, and test it in development before passing it to production. It's not super slow, but it is worth mentioning.

For any developer starting out, it is worth it. If you're already a successful startup and you have other worries, that would be a debate amongst the internal teams. But, it's worth it to bootstrap something.

We played around with Python, which was part of a different part of our stack, but we didn't consider other options. 

When I came in, Algolia was already integrated into the product, so, I couldn't change the existing product, only improve upon it.

It's a really great solution. The more you work with it, the more intuitive it gets. I think Algolia is onto something that is very valuable. 

Overall, I would rate the solution an eight out of ten. 

Our main use case for Algolia is our documentation search, and it has been really awesome. Whenever someone is searching in our docs, they are actually checking our Algolia search index, which allows our users to get the very specific details about our product and also get the best results for their query.

The best feature Algolia offers is agentic generative search, where someone can get generative answers from our own docs, and that is useful. The implementation of that feature has changed the way our users interact with our documentation, making it easier for them to find details faster.

Earlier, there were so many support inquiries because of documentation issues. Now the support inquiries are properly about product issues rather than documentation issues. Whenever there is an issue, we direct users to our docs page where they can ask the question to the agent and get the answers back, which is really helpful.

Algolia has positively impacted our organization quite well. First of all, we got some credit that was awesome to get started, and then it allowed us to explore the product better and find the best use cases for it.

I would prefer if Algolia offered some sort of volume discounts if that is possible, as right now they are not the best when it comes to discounts, and it is a bit expensive as we grow, to be straightforward. Pricing is the main concern for us when thinking of improvements.

I have been working in my current field for about four or five years. I have probably used Algolia for about two years as of now.

Algolia is stable.

Algolia's scalability is excellent.

They have been great, which makes customer support awesome.

I did not previously use a different solution for documentation search, as we had our own internal solution. Before choosing Algolia, we tried our own solution, which was some sort of internal solution using RAG and an agentic system, but Algolia proved to be the best and easiest to implement.

I have seen a return on investment. We have fewer employees, but each employee's time is spent better. I do not have any exact statistics about that, but given the fact that we saw a twenty percent reduction in support tickets, that definitely should relate to some sort of positive metric, though it did not result in any employee reduction.

My experience with pricing, setup cost, and licensing is fine. That is their price, and we respect that.

For the specific use case of documentation search, I do not think there is any better solution other than implementing something on your own.

I can share specific outcomes that Algolia helped our organization achieve. We saw around a twenty percent reduction in support tickets after we implemented Algolia, which are measurable benefits. I would rate this product an eight out of ten.

I used Algolia to implement search functionalities. When I had too many products and wanted to improve search functionality, I built custom webhooks in the backend using ExpressJS and NodeJS. The product information was passed to Algolia, which I used only for search functionalities.

In my site, conversion rate or customer satisfaction progressed 100%. I rate it 100% for customer satisfaction because when users search for a product, they don't need to press the enter button. 

If they type ABC, the ABC type of product is automatically filtered and shown at the bottom of the screen. Algolia gives us that functionality, immediately showing filtering products without any bugs. That's why, in my site, it's 100% customer satisfaction. And from my side, it's okay.

In my experience, I used Algolia because it made searching and filtering products much easier. Algolia provides some cool functionalities like filtering, indexing, and searching. 

If I implemented such functionality without Algolia, I would have to create the filtering functionality customly. But with Algolia, it's much easier because they already have these features built-in.

I implement their inbuilt hooks or components, like InstantSearch, which is a React UI component provided by Algolia. It helps me with searching and filtering the products. I used Algolia for basic purposes because I haven't worked on any advanced projects with it yet.

The documentation is not beginner-friendly. When I first used it, I sometimes couldn't understand its components and how they worked. 

At one point, the product was automatically deleted from the backend for unknown reasons. But, I haven't had any other problems so far.

I started working with Algolia last year in December at my ex-company. I worked as a front-end technical lead and used different technologies, including Algolia. However, I only used the basic features, not the advanced ones, because it was already set up.

I didn't see any bugs. It's developer-friendly and user-friendly. I have not faced any bugs so far.

When I worked at my previous company, they had a limited developer team of just ten or twelve. So, five or six developers used Algolia in my current team.

My company decided to use Algolia. It's a very big and complicated web application. I asked them why we use Algolia, and they told me that implementing such functionality or filtering functionality customly would take too much time. But if we use Algolia, it helps us save time on maintenance, and we can use it frequently.

If someone reads the documentation well, then anyone can use Algolia. But for beginners, it's hard because the documentation is not beginner-friendly, in my opinion.

Deployment model: I used Algolia in the cloud for search recommendations to make the site's searching faster.  

First of all, I want to know why you would ask me this. If you have a complicated project, then I definitely recommend Algolia. But if the project is simple and not too complicated, then you can use custom filtering or functionality.

There are two types of beginners: 

1. Those who want to learn just from watching YouTube videos.
2. Those who are willing to read the documentation and research the features. 

For the latter, it will be okay, but for beginners who don't want to read the documentation and just want to watch YouTube videos, it will be hard for them to learn to use Aloglia.

Overall, I would rate it a nine out of ten. When I use this product, it reduces my time and saves me from time-consuming tasks because everything is automated. Every back end, Express, Scrapy, and others, they already told us that if we use Algolia, they already provide us with webhooks. 

If we implement the webhooks, it only takes two to five minutes maximum. Then we work on the front end just for designing. If I created the functionality without Algolia, it would take too much time, like 30 minutes or an hour. 

But when you use Algolia and webhooks, it takes only five minutes, and Algolia has its own component, InstantSearch, for filtering. We just implemented the component, and it's okay. That's why, from my side, I rate Algolia as nine out of ten.

I use Algolia for Magento 2 e-commerce websites so that I can enhance user search functionality. Throughout Algolia, our company can enhance our search results as per the user type, which can improve the user experience and reduce the time it takes for them to find a product. Algolia is also useful for filtering products. It can also be used to add any promotional banner, product ranking, product review, and product boosting.

The solution's most valuable feature is its ability to customize Algolia's API and then use it anywhere in Magento's application however we like.

There are no areas in the product where improvements are required. I believe it is one of the best products right now.

When indexing the products, one may face some issues with the tool.

I have been using Algolia for four years. I am a customer and developer who uses the tool to meet the requirements of our company's clients.

Scalability-wise, I rate the solution a nine out of ten.

I never had an opportunity to contact the solution's technical support team. Based on what I feel, I rate the technical support a ten out of ten.

Positive

I used to use Magento's default search functionality. Magento has some programming languages for indexing and search boxes. Algolia offers a very heavy functionality for search-related tasks.

The product's initial setup phase is super easy.

Algolia is a cool, super-easy-to-use, and affordable tool. Suppose a company's customer is looking for Algolia's search indexing. Considering such cases, an organization needs to be ready to pay the price of the solution since the tool has many features that can help customize its users' e-commerce store. People who are looking for Algolia are also ready to pay its price.

It is a super easy tool to use. You just need to download, install, and use the extensions. If you need more extensions, then it may get harder for you to be able to customize Algolia. In general, it is a cool tool.

I recommend the product to other people.

If a user wants super search functionality in their e-commerce store to enhance the user experience, they can go for Algolia. Algolia can also enhance the search results as well as provide enhanced analytical reports related to the search by analyzing the customers, and seeing how customers interact with the search bar. The tool provides users with personalization features that can be used to improve user interface. One can also customize the search-related user interface. The features of Algolia are extremely good.

I rate the tool a nine out of ten.

I developed an application solution for the Economist Group, a think tank based in London. They were planning a new initiative, which was a publication tech. We use Algolia Search to give users the capability to search documents in the application we created.

Since Algolia is a SaaS solution, we didn't have to maintain servers, look at the indexes, and monitor services. Not having to maintain the servers was less of a headache for us. Algolia's similarity to other search services like Elasticsearch has greatly helped us.

Algolia is not adopted that much, and it would be great if it were made more popular.

I have been using Algolia for two years.

I didn’t face any issues with the solution’s stability.

There was one issue we faced. The plan we had gave us a restricted amount of storage, and the search stopped when the plan stopped. If you plan for 1,000 documents, the search stops when you reach 1,000 documents. That was a drawback, and the tool wasn't scalable in the planned period.

We understood the search had stopped because the plan limit had been crossed. We had to add a credit card to get it working, and it started working. People use the search service through our website, which has around 10,000 monthly visitors. However, three system users have access to the tool.

I rate the solution’s scalability a four or five out of ten.

The technical support team was able to resolve our issues within two days.

I have previously worked with Elasticsearch.

The solution's initial setup is straightforward and not very difficult.

The first POC we did with Algolia took around two days. In weeks we were able to deploy the first iteration of the solution in production

The solution is worth the money.

I have heard that Algolia is an expensive solution.

I would recommend the solution to users looking for an easy search service. It is very easy to set up and do a POC with Algolia. If you are looking for custom sorting, Algolia is not the right solution for you.

Overall, I rate the solution an eight out of ten.