Sprigr compiles your search index into a blazingly fast client-side search engine. Users search locally in the browser. No per-query fees, no infrastructure to manage, no servers to scale. Your search cost is the same at 10 searches per month or 10 million.
Sprigr compiles your search index into a client-side engine. Search runs locally in the browser with zero API calls. Your cost is a flat monthly fee regardless of query volume. Whether your users run 10 searches or 10 million, the bill doesn't change.
You focus on the work. Sprigr runs the paperwork.
Eliminating API calls does not just save money. It makes search fundamentally faster and more reliable.
Serverless search functions take 50-500 ms to cold start. Sprigr's search engine is already loaded in the browser. The first search query is just as fast as the thousandth, under 10 ms, every time. There is no waiting for a function to spin up, no Lambda initialization, no container warm-up.
API-based search enforces rate limits to protect server resources. When your site gets a traffic spike (a product launch, a viral post, a Black Friday rush) rate limits throttle your search right when it matters most. Sprigr has no rate limits because there is no server to protect. Each user runs search independently in their browser.
Once the search engine and index are cached, search works without any network connection. Users on planes, trains, or spotty mobile connections can still search your content. This is critical for progressive web apps, mobile apps, and documentation sites used in areas with unreliable internet.
Per-query pricing punishes growth. Sprigr costs the same whether your users run 10 searches or 10 million. Your search bill is predictable and doesn't surge with traffic.
The compiled index is served from a 300+ location edge network. First-load time is optimized regardless of where your users are. After that, the engine is cached locally.
No query logs, no user identifiers, no cross-border data transfers. Queries stay on the device. GDPR obligations for search functionality effectively disappear.
Three steps from your data to instant, serverless search.
Send records to the Sprigr REST API. Products, articles, documentation, job listings, any structured JSON. This is the only time your data touches a server.
Sprigr builds a compact binary search index optimized for in-browser execution. A 10,000-record catalog compresses to 1-5 MB for keyword search. Indexes with semantic search enabled are larger. The index is served from a global edge network.
The lightweight search engine loads in the user's browser and searches the index locally. Every keystroke produces results in under 10 ms. No API call. No server. No cost per query.
At 100,000 searches/mo, Algolia is around $50. At 1 million, around $500. At 10 million, over $3,000. Sprigr is flat: whether your users run 10 searches or 10 million, the bill doesn't change. Predictable pricing that rewards growth instead of punishing it.
See pricing →You push your data to Sprigr via a REST API during indexing. Sprigr compiles that data into a compact compiled binary search index. When a user visits your site, the search engine and index are loaded into the browser. Every search query runs locally in the browser. No API call is made for search. The only network request is the initial load of the search engine and index, which is cached by the browser for subsequent visits.
No. Since searches run in the user's browser, there is no server to rate-limit. Users can search as fast as they can type, and every keystroke produces results in under 10 milliseconds. There are no per-query costs, no daily quotas, and no throttling. The only limit is the user's device performance, which on modern hardware is effectively unlimited for search workloads.
Nothing changes for search performance. Each user's searches run in their own browser, so search scales linearly with users at zero marginal cost. The search engine is served from a global edge network across 300+ locations, so the initial load is fast regardless of traffic volume. No auto-scaling, no capacity planning, no emergency infrastructure bills.
The practical limit for client-side search is around 50,000 to 100,000 records, depending on record size. A typical 10,000-record product catalog compresses to 1-5 MB of keyword index data. Indexes with semantic search enabled include vector embeddings and are larger. Large indexes are automatically split into parallel-loaded shards for fast startup. For very large datasets, Sprigr also provides a server-side REST API as a fallback.
Yes. Once the search engine and search index are loaded and cached by the browser, all search functionality works without any network connection. This makes Sprigr ideal for progressive web apps, mobile apps, documentation sites, and any scenario where connectivity is unreliable. Search results, filtering, and highlighting all work identically offline.
Free forever for small projects. Paid plans from $49/mo.