Elasticsearch alternative · Catalog search · One-time license

The Elasticsearch alternative that runs on one server — with nobody nursing it.

Dartfind is a purpose-built catalog search engine: one compiled binary on one ordinary x86 machine, answering in ~20 ms across up to 100 million records. No cluster to size, no JVM to feed with RAM, no analyzers and synonym lists to write, no engineer on payroll keeping search alive. One-time license — the client owns it outright.

Built for distributors, wholesalers and e-commerce with large catalogs — from 10,000 to 100 million records.

Why teams go looking for an Elasticsearch alternative.

The TCO

“Free” software, expensive reality

The download costs nothing. The production reality is a multi-node cluster, a RAM-hungry JVM, and an engineer who keeps it alive — recurring costs that dwarf most license fees. The software is free the way a puppy is free.

The tuning

Every broken query is a rule someone writes

Typos, partial part numbers, glued words — in Elasticsearch each case is an analyzer, a synonym list, a fuzziness setting somebody has to configure, test and maintain. Relevance becomes a permanent side project.

The fit

A platform, when you needed a component

Elasticsearch is a general search and analytics platform — brilliant at many things, sized and operated like the platform it is. If the actual job is “customers find products in a catalog,” you're running a freight train to deliver a parcel.

Dartfind vs Elasticsearch, side by side.

DartfindElasticsearch
PricingOne-time license, owned outrightFree download; cluster, hosting and engineer — recurring, every year
InfrastructureOne ordinary x86 serverMulti-node cluster, RAM-hungry JVM
OperationsNothing to nurse after setupShard rebalancing, version upgrades, monitoring, on-call
Dirty queriesNative — no analyzers, no synonym listsRules and dictionaries someone writes and maintains
Time to live search2 daysWeeks to months of setup and tuning
Query pathCompiled code — no interpreter, no garbage collectorJVM with GC pauses in the path

When Elasticsearch is still the right choice.

A comparison table where one column wins every row is an ad. Three cases where we’d tell you to stay put:

If the cluster exists only to power product search — and someone's salary exists only to keep that cluster standing — that's the setup Dartfind replaces with one binary, one server and one payment.

Switching is two connections.

A sync script feeds your catalog into the engine — from a database or a plain export — and keeps it updated on schedule. A query endpoint answers searches; your storefront calls it instead of Elasticsearch. Works alongside Adobe Commerce, SAP Commerce, Oro, BigCommerce or fully custom builds, because it sits behind an API rather than inside the platform. For most stacks this is days of work — and the free pilot skips integration entirely.

16,787
products live in production
~20 ms
per query, full catalog
1
ordinary machine, no cluster
0
outbound connections, ever

Those are numbers from a live deployment: an auto-parts retailer runs Dartfind as its counter and catalog search, fed with broken part numbers every day. Full case on the main page.

Don’t take the table’s word for it. Free pilot.

Send a catalog export — real or fake. Two days later you have a working search box in your infrastructure, next to your current Elasticsearch setup. Type your customers’ worst queries at both. Then decide.

Your dataa catalog export, real or fake — no access to your systems needed
Your infrastructureruns on your server; the data never leaves your network
2 daysfrom export to a working search box you can torture
$0no contract, no card, no strings attached
Got it. We’ll get back to you within a day to arrange the pilot.
Something went wrong — please try again.

Elasticsearch alternative — questions people actually ask.

Elasticsearch is free. What am I paying for?+
You're comparing a license price to a total cost. A production Elasticsearch deployment for search is typically a 3–9 node cluster, hosting for it, and an engineer keeping it alive — recurring costs, every year. Dartfind is one payment for the full deployment, and afterwards there is very little left to operate: one binary, one server, index in RAM.
Is Dartfind as powerful as Elasticsearch?+
As a general platform — no. Elasticsearch does logs, metrics, APM and analytics; Dartfind does one thing: catalog search, at ~20 ms across up to 100 million records on one CPU, with typo tolerance built into the matching math. If your workload is a product catalog, purpose-built beats general-purpose on cost, speed to live, and operations.
Why doesn't it need a cluster or a JVM?+
The engine is written in Rust, Ada SPARK, ISPC and Erlang — compiled languages with no interpreter and no garbage collector anywhere in the query path. Matching runs on compact binary signatures compared through native bitwise CPU instructions. That's why the whole index fits and answers on one ordinary x86 server, where the JVM needs gigabytes before doing useful work.
Do I still need synonym lists and analyzers?+
For broken input — no. Typos, partial part numbers, glued words and wrong keyboard layouts land natively, because tolerance to noise is a property of the math, not a rule set. Business-specific mappings — where “oil” in your trade also means part group 15-86 — still come from someone who knows your catalog, same as anywhere.
What does migration involve?+
Two connections. A sync script feeds your catalog into the engine from a database or a plain export; a query endpoint answers searches, and your storefront calls it instead of your Elasticsearch queries. Days of work for most stacks. The free pilot skips integration: send an export, get a working search to compare side by side with your current cluster.
What hardware does it need?+
Any x86 CPU with SSE2 — practically any machine made this millennium. No AVX-512, no GPU, no sized cluster. Whatever server you already own almost certainly qualifies, and it keeps working with the internet cable physically unplugged.