Changelog

What's new in Findlane, newest first. Follow along with the RSS feed.

  1. A pricing page, and this changelog

    Every plan's limits, the overage caps, and billing answers on one page, and a changelog with an RSS feed.

    See pricing
  2. Use cases and data recipes

    Pages for each kind of data Findlane searches, and a Your data section in the docs with the records and settings to start from.

    • Use cases for online stores, docs and help centers, articles and research, and listings and places, each with a live demo.
    • Plan your records, then a recipe for products, docs, articles, or listings.
    • The MCP server's set-up prompt reads the recipe for your kind of data before it chooses settings.
    See the use cases
  3. Location search

    Give records a location, then search near a point, within a radius, or inside a map's view.

    • A locationField setting, and near, within, and sort: "distance" in searches. Each hit says how far away it is, in meters.
    • near: { visitor: true } starts near the visitor's city, with no permission prompt.
    • In React, useGeoSearch keeps a map, its results, and the URL in step (@findlane/browser 0.5.0).
    • Try it on 35,000 restaurants.
    Read about location search
  4. An MCP server for AI agents

    Connect Claude Code, Cursor, VS Code, or Claude to Findlane, and an agent can set up and look after your search.

    • Sign in once in your browser, and choose the workspace the agent may manage.
    • 21 tools: indexes, records, settings, test searches, allowed origins, analytics, API keys, and the docs.
    • Searches agents run to check their work are free.
    Connect an agent
  5. Did you mean

    Searches say when typo tolerance changed the query, and a search that finds nothing can ask for a correction.

    • Turn on didYouMean in an index's settings.
    • suggest() returns a query that finds results, and React's DidYouMean shows it.
    • Suggestions don't count toward your plan's searches.
    Read about did you mean
  6. React components

    @findlane/browser/react has a search box, a ⌘K search dialog, a results page with filters, and the hooks behind them.

    • Facet checkboxes keep the other values listed after one is ticked, with disjunctiveFacets.
    • Sorts can settle ties with up to two more fields, with thenBy.
    • Findlane's own docs search with SearchDialog.
    Read the React docs
  7. Price sliders and more facets

    facetStats returns the smallest and largest values of number fields, such as the ends of a price slider.

    • An index can have up to 128 filter, facet, and sort fields, and a search can ask for 32 facets.
    Read about number ranges
  8. Where people search

    Analytics shows where searches come from on a map, with top cities, devices, browser languages, and a feed of recent searches.

  9. Languages

    A languages setting for Danish, English, German, Icelandic, Norwegian, and Swedish: searches leave out common words, and match plurals and other spellings.

    • New indexes also match letters such as ø, ß, æ, ł, and þ to their plain spellings, so kobenhavn finds København.
    • Icelandic doesn't match plurals yet.
    Read about languages
  10. Findlane for Shopify

    An app that keeps a store's products in sync and answers the theme's own search box, without code. It's on its way to the Shopify App Store.

    Read about the app
  11. Findlane is live

    Hosted search with an HTTP API, server and browser SDKs, a dashboard, and a playground with a live store catalog.

    • Typo tolerance, facets, filters, sorts, and synonyms.
    • Search straight from the browser with an index's public ID and the origins you allow.
    • The browser SDK on a CDN, for a script tag.
    • Search analytics, and invitations for teammates.
    Start with the quick start