For agencies & system integrators · Partner program

The third option in your search vendor analysis.

A catalog search engine you spec into client builds — same speed and quality as Elastic or Algolia, at a fraction of the cost. The client gets a compiled program on their own server, owned outright: one-time license, not a subscription. You get a clean line in the SOW, and the integration and customization work quoted as your services.

For agencies building for distributors, wholesalers, e-commerce and B2B portals — catalogs from 10,000 to 100 million records.

STATEMENT OF WORK — SEARCH COMPONENT EXAMPLE
Dartfind license — one-time, client-ownedvendor line
Integration: catalog sync + query endpointyour services
Customization & ranking tuned to the catalogyour services
Ongoing support retaineryour services
One vendor line. Everything else in the search scope is billed by you — and your search revenue lands upfront, at the deal, not as drip commissions.

Why it wins the comparison.

Cost

One-time beats forever

In any client cost comparison, a one-time license beats a subscription that runs forever and grows with traffic. Put it in the vendor analysis and let the client do the math.

Budget

Freed budget stays in the project

Whatever the client doesn't sink into search subscriptions stays in the build — more scope for your design, development and support work.

Reach

Closes clients the cloud can't touch

On-prem and offline by default. Clients with data-residency rules, security policies or plain distrust of per-query metering — the deals cloud search vendors are locked out of, you can now take.

Side by side in the vendor analysis.

Dartfind Elastic / Algolia
Client pricing One-time license, owned outright Subscription forever / grows with traffic
Infrastructure One ordinary server — any x86 CPU Cluster and engineer / vendor cloud
Deployment Live in days, two connections Weeks of setup, tuning, dependencies
Broken queries Typos and partial SKUs land natively Dictionaries and rules someone writes
Data location Client network, works fully offline Leaves the network / cloud only

Integration, from your side of the SOW.

Two connections and the component is live: a sync script feeds the client catalog into the engine and keeps it updated on schedule, and a query endpoint answers searches — the storefront calls it instead of the platform default.

Platforms

Sits behind an API, not inside the platform

Works alongside Adobe Commerce, SAP Commerce, Oro, BigCommerce or fully custom builds. No plugin lock-in — the storefront just calls a different endpoint.

Demo effect

Impressive in the very first client demo

The engine reads broken input natively — typos, partial part numbers, glued words — with no dictionaries or rules to configure. The search works the way the client's customers already expect, on day one.

Reuse

A component for every catalog build

Once your team has wired it in once, it's a repeatable module: every project where a catalog needs finding gets a better search and a better margin. Days of work, not months.

The economics, plainly.

The client price never grows with catalog size or traffic — which is exactly why it wins the comparison. Your margin lands upfront on every deal, and the integration, customization and support around the license are quoted and billed as your services. Partner terms are simple and we walk through them on the first call.

Talk partner terms One call. Numbers on the table.

Proof, not promises: free pilot on your client's catalog.

Send any client catalog export — real or synthetic, anonymized is fine. Two days later you are demoing a working search to your client on their own queries. If it wins the vendor analysis, we close it together. If not, it cost you nothing.

Any exportCSV or any dump — real, synthetic or anonymized client data
2 daysfrom export to a live search box you demo to the client
Their querieslet the client type their customers' worst searches at it
$0no contract, no card, no commitment on your side

How the partnership starts.

STEP 1

Intro call

We walk through the engine, the pilot mechanics and partner terms. You decide if it belongs in your vendor shortlist.

STEP 2

Pilot on a live deal

Pick a client project with a catalog. We stand up the pilot in 2 days; you run the demo under your own flag.

STEP 3

Close it together

License lands as one line in your SOW. Integration, customization and support are quoted as your services — your revenue, upfront.

Got it. We’ll get back to you within a day to set up the intro call.
Something went wrong — please try again.

Questions agencies actually ask.

Who owns the client relationship?+
You do. The client is yours, the SOW is yours, the demo runs under your flag. We supply the engine, the pilot and the technical backup on calls when you want us there. We don’t sell around you.
Who does the integration — you or us?+
Your team, and that’s the point: integration and customization are your billable services. It’s two connections — a catalog sync script and a query endpoint — so for most platforms it’s days of work. We hand over documentation and stay reachable during the first build.
What does the partner earn?+
Two streams. A margin on the one-time license, paid upfront at the deal — not drip commissions over a subscription lifetime. Plus everything around the license: integration, customization, ranking tuning and the ongoing support retainer, all quoted and billed by you. Concrete terms are discussed on the intro call.
What platforms does it work with?+
Adobe Commerce, SAP Commerce, Oro, BigCommerce and fully custom builds — anything that can call an HTTP endpoint. The engine sits behind an API rather than inside the platform, so there is no plugin dependency to maintain across platform upgrades.
Is it actually production-grade?+
The engine already runs in production at an auto-parts retailer, fed with broken part numbers every day — 16,787 products, ~20 ms per query, one ordinary machine. It’s written in Rust, Ada SPARK, ISPC and Erlang: the languages of rockets, avionics and telecom, where software is not allowed to fail or lag. No Python, no interpreters, nothing slow in the path of a query.
What if the client wants custom features later?+
Front-end and integration-level work is yours to quote. Engine-level features — new filters, sorting logic, custom matching behavior — we build as paid work, and they ship to every customer after yours. Either way there’s a paid change request, and you stay the general contractor.
How big a catalog can it handle?+
100 million records on a single server, index in RAM, answers in tens of milliseconds. From a 10,000-SKU distributor to a marketplace-scale catalog, it’s the same binary on one ordinary x86 machine.