Algolia Pricing in 2026: What Search Really Costs

Quick answer (July 2026): Algolia bills by usage, not by a flat subscription. The free Build plan covers 10,000 search requests and 1,000,000 records a month. Above that, the Grow plan charges $0.50 per 1,000 search requests and $0.40 per 1,000 records, with no base fee. Because search requests dominate at scale, the same store can cost $0 on the free tier, about $226 a month while it is growing, and roughly $1,655 a month at high traffic. Your bill is set by how many searches you serve and how many replicas you keep, not by how big your data is.

Algolia is a hosted search API that returns results in tens of milliseconds. It is the path of least resistance for site search, and, as one developer put it on a Hacker News thread about the pricing change, the "success tax" arrives when your traffic does. Here is the arithmetic, with three real 30-day bills.

How Algolia pricing works in 2026

Algolia has four plans. Two are self-serve and usage-based, one is a hard-capped free tier, and one is enterprise.

Two definitions decide your bill, and both trip people up:

• A search request is, in Algolia's words, "a group of one or more search operations sent in a single exchange." Query three indices in one federated call and it counts as one request, not three.
• A record is any item you index. Your total is the sum across every index, and standard sort replicas count as full copies. More on that below, because it is the number one bill surprise.

The per-unit prices come straight from Algolia's pricing page and its Grow-plan billing docs, checked July 12, 2026.

Three real 30-day Algolia bills

Bill 1: the docs site that stays at $0

A documentation site or small Firebase-backed app with 40,000 records and 9,000 searches a month sits entirely inside the Build free tier (1M records, 10K searches). Monthly cost: $0.

The catch is that Build is a hard cap, not a metered plan. Cross 10,000 searches and search simply stops until the next cycle; there is no overage bill to rescue you. That is fine for a hobby project and risky for anything that a customer touches.

Bill 2: the growing store at ~$226/mo

A store with 60,000 products and 350,000 searches a month on the Grow plan. But the owner added three sort orders (price low-to-high, high-to-low, and newest) as standard replicas, and each standard replica is a full copy of the index:

• Billable records: 60,000 x 4 (primary + 3 replicas) = 240,000
• Records over the 100K free tier: 140,000 -> 140 x $0.40 = $56.00
• Searches over the 10K free tier: 340,000 -> 340 x $0.50 = $170.00
• Total: about $226/mo

Now the lever. Switch those three standard replicas to virtual replicas (Algolia's Relevant Sort), which do not duplicate the record count. Billable records drop back to 60,000, under the free tier, and the record line falls from $56 to $0. Same store, same features, $56/mo saved by changing one setting.

Bill 3: the high-traffic marketplace at ~$1,655/mo

A content marketplace with 500,000 records and 3,000,000 searches a month on Grow:

• Records over free: 400,000 -> 400 x $0.40 = $160.00
• Searches over free: 2,990,000 -> 2,990 x $0.50 = $1,495.00
• Total: about $1,655/mo (roughly $19,900/yr)

Notice the shape: searches are 90 percent of the bill. Records barely move the needle at scale. And if this account were on Grow Plus at $1.75 per 1,000 searches, that search line alone becomes 2,990 x $1.75 = $5,232.50, pushing the bill past $5,390/mo. The plan version, not the data size, is what blows up the invoice. This is the "$60k/year" territory that shows up in r/softwarearchitecture threads.

The four things that quietly inflate an Algolia bill

1. The replica tax. Standard replicas are full copies. Three sort orders on a 200K-record index bill you for 800K records. Use virtual replicas where the use case allows.
2. Search-as-you-type multiplies requests. InstantSearch fires one request per keystroke by default, so a 12-character query can be up to 12 billable requests. Debouncing keystrokes (a short delay before firing) commonly cuts search-request volume 60 to 80 percent.
3. Federate in one call. Because one "exchange" is one request, batching autocomplete + products + suggestions into a single multi-query call bills as one request instead of three.
4. Algolia forgives your three worst days. Before calculating overages, Algolia drops your three highest-usage days each month. One Black-Friday spike is partly absorbed, so do not panic-migrate over a single bad day.

Is Algolia cheaper than the alternatives?

Not for steady, search-heavy workloads. The metered model rewards spiky, low-volume search and punishes always-on search at scale.

Meilisearch Cloud starts around $30/mo and includes 50,000 searches (five times Algolia's free search allowance), with gentler overages. Typesense Cloud bills a flat hourly rate for a dedicated cluster with no per-search or per-record metering, which flattens your cost curve once search volume is high. Elasticsearch and OpenSearch go further on control and economics but hand you the DevOps.

The honest trade: Algolia's relevance and zero-ops tuning are genuinely excellent, and for many teams the convenience is worth the premium up to a point. Past a few million searches a month, a flat-fee engine usually wins on cost. Run your own numbers against the bills above before you commit.

If you are auditing your whole stack, the same "cheap records, expensive usage" pattern shows up across metered vendors; see our Firebase pricing teardown and the Cloudinary usage-metering teardown for the same math applied to reads and transformations.

How to cut your Algolia bill this week

• Convert standard sort replicas to virtual replicas wherever ranking allows.
• Debounce search-as-you-type, or raise the query-length threshold before firing.
• Federate multi-index queries into a single request.
• Set a monthly spending cap so an accidental crawl loop cannot run up four figures.
• Re-check whether you actually need Grow Plus; the search overage is 3.5x higher than Grow.

Math check: on Algolia, records cost $0.40/1K and searches cost $0.50/1K, but at scale searches are ~90% of the bill, so every keystroke you stop firing is money.