Changelog

App Search is in release candidate with our design partners. It searches the records inside an application or website: products in a store, listings on a marketplace, articles in a help center, or records inside a SaaS product.

Everything we’ve learned searching complex files with File Search now goes into App Search. Ranking blends keyword and meaning-based matching the same way, and the query understanding that fixes typos and recognizes codes like SKUs and CUSIPs works on records too. File Search still handles files and their contents, so Captain now searches both the documents a company keeps and the records its product serves. Each customer gets a dedicated endpoint, such as acme.captain.dev. See the App Search overview.

• Results while people type: typeahead answers each keystroke with spelling fixes and completions. Full search combines keyword and meaning-based matching with filters, facets and sort, and browse, similar records and multi-search return the same response shape. See Search.
• An index that keeps up with your data: records you add or replace are searchable within a few seconds, and updates and deletes apply within about a second. There’s no build step to run. See Records.
• Per-user access for sensitive records: when records carry access lists, a scoped key minted for one end user returns only what that user may see, and suggestions and facet counts follow the same rule. See Per-record access control.
• Search analytics: send click and conversion events, then read top queries, zero-result queries, click-through rate and conversion rate for each index. See Analytics.
• Works with existing Algolia clients: an Algolia client or InstantSearch front end can point at your endpoint with a Captain search key, and an existing Algolia index can be imported. Captain reviews each import before it builds. See Algolia compatibility.