Why the indirection in the pricing page. Like, if a unit is 1,000 searches/month, why not just put that in the matrix. Free = 10,000 searches/month. Standard = $1 per 1,000 searches. ... Pay as you go: 1,000 - 10,000 searches = Free 11,000 - 100,000 searches = $1.00/ 1,000 searches The whole to unit conversion really just adds a level of indirection that I don't understand. This was further confused by units having d…
This pricing change from Algolia makes it easier for low-volume search users or someone who is just getting started to use their enterprise features, but at the same time as the parent mentions, makes it an order of magnitude more expensive for mid-to-high volume users. Imo, this is a mismatch as there is already a trial in place for someone who's just getting started to try those features out. For anyone interested…
Algolia introduces pay-as-you-go pricing for search
81–90 of 100 posts
Re: Algolia introduces pay-as-you-go pricing for search
#82Earlier quoted context omitted.
(I am the CTO and Co-founder). I can reassure you this is not the case, I don't have visibility on when we will do an IPO and we grandfather all existing customers. We always did that and we still have customers today on 2013 pricing! It bring a lot of complexity internally. We released this new pricing only because we are convinced this is better for customers.
I signed up for an account just to respond to this. I run a small, low-budget, lean startup and we were banking on the starter plan lasting us at least 6 months as we gradually scaled. You cited in the blog post that making this change was supposed to "reduce entry costs" but how has this happened? Just the limit of the old free plan would cost you more than the old starter plan! The limit of the old starter plan wou…
The previous pricing was based on indexing operations + search operations. The new pricing is only based on search request and in a lot of situation N search operations = 1 search request (disjunctive faceting, federated search, etc.). At the end, for the big majority of free users (> 99%) they have as many or more search request in the 10 free units than in the old plan.
Re: Algolia introduces pay-as-you-go pricing for search
#83Earlier quoted context omitted.
Out of curiosity, could you expand on how it doesn't make sense for SaaS use cases?
I am the co-founder of Algolia, we have a dedicated pricing for the SaaS use cases that we call OEM pricing (in a few words pay per GB of usage). When we have a platform, it is very hard to have a pricing that works perfectly well for all industries and that is simple!
It’s a way better experience than having to talk to a sales rep to get a sense of pricing after 3 calls.
We face the same challenge with Decimlas.app, and will be adding pricing to the landing page in the next few weeks.
Re: Algolia introduces pay-as-you-go pricing for search
#84Why the indirection in the pricing page. Like, if a unit is 1,000 searches/month, why not just put that in the matrix. Free = 10,000 searches/month. Standard = $1 per 1,000 searches. ... Pay as you go: 1,000 - 10,000 searches = Free 11,000 - 100,000 searches = $1.00/ 1,000 searches The whole to unit conversion really just adds a level of indirection that I don't understand. This was further confused by units having d…
I've been working on an open source alternative. It's dead simple to setup and run (including raft based clustering). It also integrates seamlessly with Instantsearch.js library. Would love to hear your feedback on Typesense: https://github.com/typesense/typesense
Good luck!
Re: Algolia introduces pay-as-you-go pricing for search
#85Interesting change. Disclaimer, I joined one of Algolia's competitors ( http://sajari.com ) 6 months ago and we are about to release a new product and change our pricing, so I've been thinking about this a lot. Having worked at Atlassian before, I understand how important simple pricing can be. My personal (and probably biased opinion) is that this is a move in the wrong direction. It appears simpler on the surface,…
THIS ! I feel many times business put the "business-complexities" onto the client, in this case the search-unit and although the CTO explained why (I gloss over it) as a customer , I don't need to understand what makes it difficult in your business nor do I want to know all your internal jargon and limitations. I the customer understand searches and searches per month. Don't make me think ! Like going to a restaurant…
Each industry has different aspects of how much value they get from a product, the effort to try to encapsulate these aspects into a single pricing functions is much appreciated.
We face the same challenge with Decimals.app - should be adding pricing soon as well
Re: Algolia introduces pay-as-you-go pricing for search
#86This is a huge increase in pricing for all our customers using Algolia. https://web.archive.org/web/20200620142025/https://www.algol... The previous Starter tier pricing was a lot cheaper. Most important point to note is that additional searches were closer to 10k/$1 vs the proposed 1000 (additional 100k operations: $10/month). Yes, these were 'operations' not searches' but the mapping between operations vs searches…
This is not the case, the price of unit decrease with volume and you can have a big discount if you want to commit to a yearly (similar to AWS/GCP/Azure)
Re: Algolia introduces pay-as-you-go pricing for search
#87Earlier quoted context omitted.
Interesting. This reminds me of Canada Post's address complete API. You can integrate it with your website or app to ensure the addresses the users enter are valid within Canada and entered correctly. The pricing is around 5–10¢ per search [0]. At that price point, it only makes sense to use it for e-commerce if you are going to deliver physical goods to the customer and want to minimize the number of returned "addre…
Many local governments publish shapefiles (geojson) that have address information. You could parse out addresses and have a fairly simple free option. Since this data is based on property taxes, these data sets aren't going to be missing parcels (or the tax collector would be missing potential revenue).
Also, one of the main benefits from Canada Post API is that it gives you the canonical address Canada Post uses to deliver packages. I don't think this always overlaps with addresses municipalities use to assess taxes. For example, I can imagine for an apartment building belonging to a real estate management company, there would be a single entry in the municipality database (because there is only one owner who needs to pay taxes), but one entry per unit in Canada Post database.
Re: Algolia introduces pay-as-you-go pricing for search
#88This is a huge increase in pricing for all our customers using Algolia. https://web.archive.org/web/20200620142025/https://www.algol... The previous Starter tier pricing was a lot cheaper. Most important point to note is that additional searches were closer to 10k/$1 vs the proposed 1000 (additional 100k operations: $10/month). Yes, these were 'operations' not searches' but the mapping between operations vs searches…
I see it like they're chasing the lower end of the market like single dev projects that don't want to spend much - which I guess makes sense. But for us this definitely would be a lot more expensive.
Re: Algolia introduces pay-as-you-go pricing for search
#89Earlier quoted context omitted.
I've been working on an open source alternative. It's dead simple to setup and run (including raft based clustering). It also integrates seamlessly with Instantsearch.js library. Would love to hear your feedback on Typesense: https://github.com/typesense/typesense
Hi there, I see you posted multiple times your Typesense link. Just wanted to point out that your demo website is broken for some days now. I keep getting "ERR_CERT_DATE_INVALID". Good luck!
Re: Algolia introduces pay-as-you-go pricing for search
#90Earlier quoted context omitted.
I see it like they're chasing the lower end of the market like single dev projects that don't want to spend much - which I guess makes sense. But for us this definitely would be a lot more expensive.
Well, if so they've failed in my case. I've got a customer doing £1m annual turnover on e-commerce, and we were about to start an integration with Algolia. The new pricing has stopped that from going ahead. I've been asked to find an alternative.
I made a simple Proof-of-concept of a PHP backend based on Redisearch compatible with the Instantsearch.js library.
You can take a look at it here : https://github.com/MKCG/algolia-on-redisearch/tree/master/ap...
With the Covid crisis we were no longer able to pay 3K per month for a basic search engine and now we are using a solution based on this on production (> 30M search/month).