Platform

Build

Connect & extend

Govern & run

Government
EnterprisePricing
Resources

Live sessions

Platform · Search

Find anything, within each person’s permissions.

Records, documents, pages, and external systems, in one search box: forgiving of typos, aware of meaning, and trimmed to what each person is allowed to see.

Illustration of the same search, “building permit”, run by two people. A signed-in permit reviewer gets four results: two permit applications, the public guidance page, and a PDF checklist. A public visitor who isn't signed in gets only the guidance page and the checklist.

Ask

People search for answers, not tables.

They type a name, a reference number, a phrase from a letter, and expect the answer, wherever it lives. One search box covers every kind of content.

  • Records.

    Every entity, in the fields you choose, including the names on linked records, so an applicant’s name finds their requests.

  • Documents.

    The words inside PDF, Word, and other office files, not just their file names.

  • Pages.

    Program information, guidance, and help content, in the same results as the data.

  • Results that lead somewhere.

    Grouped by type with a count for each, matched words highlighted, and every result opens the record or page itself.

Unify

One search across systems that never talked to each other.

The answer often lives somewhere else: a legacy database, a document store, an older website, a system with nothing but an API. Bring them into one index without migrating or replacing any of them, and people search all of it from one place.

SourceBrought in byVisible to

  • Grants applicationIts own recordsBy role
  • Legacy case databaseA database queryFrom a column
  • Document storagePDF, Word, ExcelFolder permissions
  • Program websiteSitemap crawlEveryone
  • Payments systemA workflow, via its APIProgram managers

One indexOne search box, trimmed for each person

  • Permissions travel with it.

    Each source sets who may see its results: by role, by a column in its own data, or open to everyone.

  • Any database.

    Bring in rows from other databases with a query, legacy systems included.

  • Websites and feeds.

    Crawl websites, sitemaps, and RSS feeds into the same results.

  • Anything with an API.

    Workflows fetch content from other systems and add it to the index, as often as you need.

Every system stays where it is.People look in one place.

Trust

Every answer depends on who’s asking.

A search box can reveal what no page would ever show. So results follow the same permissions as everything else, and the same search returns different answers for different people.

  • By role.

    Records, pages, and files appear only for the roles allowed to open them.

  • Only their own.

    Where people see only their own records in a list, they see only their own records in search.

  • Public means public.

    Visitors who haven’t signed in find public content, and nothing else.

The rules aren’t set twice. Search follows the permissions you already gave your pages, records, and files.

Reuse

Search inside forms, workflows, and APIs.

Search isn’t only a box at the top of the page. Everything comes into one index with its permissions, and the same search serves every part of the application that needs to find something.

Brought in

  • Records
  • Documents
  • Pages
  • Other databases
  • External APIs

One index

Permissions preserved

  • Search box
  • Forms
  • Workflows
  • APIs
  • AI assistants

Used by

  • Lookups in forms.

    Type a few letters to pick an applicant, a program, or an address, from your data or from any API.

  • A step in any workflow.

    Workflows search, page through what they find, and act on it.

  • An API of your own.

    Publish search as an API endpoint for other systems, with the same permissions applied.

  • A tool for AI assistants.

    Give an assistant your search as a tool, so its answers draw on your own content.

Understand

It finds what they meant.

People misspell names, skip accents, and describe what they need instead of quoting it. Search meets them halfway.

  • Typos forgiven.

    Close matches still count, so “bilding permit” finds the building permit application.

  • Accents optional.

    A caseworker typing “Rene Lefevre” finds René Lefèvre’s case.

  • Suggestions as they type.

    Drawn from what others searched for, or from live results, so “prop” offers property tax.

  • By meaning, too.

    Semantic search matches intent, not just words: “can I add a deck to my house” finds the building permit guide.

Each visitor searches the content in their own language, and ranking is yours to tune: weigh titles above body text, favor recent items, or sort by date.

Narrow

From thousands of rows to the one you need.

Inside a list, search works on the spot.

  • As they type.

    Results narrow with every word, across every searchable column, including columns from linked records.

  • Filters that show what’s there.

    Each column filter lists the values actually present, narrowed by the other filters and by what the person may see.

  • Views worth sharing.

    Search, filters, and sorting live in the address, so a filtered view can be bookmarked or sent to a colleague.

Learn

See what people are looking for.

Every search is a question someone needed answered. Together, they show what your users want, and where the application falls short.

Popular searchesLast 30 days

SearchTimesResults

  • building permit41238
  • business license26021
  • permit status19812
  • short-term rental64None
  • What they ask.

    Popular and recent searches, with how many results each one found.

  • What they choose.

    Which result people opened, and how far down the list it was.

  • What’s missing.

    Searches that come back empty point to content that doesn’t exist yet, or isn’t named the way people think.

Maintain

Search that stays current, without becoming another system to run.

Search is only as good as its last update. The index keeps itself current and backed up, and shows you how it’s doing.

  • Near real time, where it matters.

    Automation jobs update the index right after changes are made, and a schedule you set catches everything else.

  • Only what changed.

    Each update picks up just the records changed since the last one, in the background, through a queue.

  • Self-repairing.

    Indexes are backed up on a schedule. If one is ever damaged, it’s restored from the latest backup and caught up from there.

  • Visible health.

    A dashboard shows what’s in the index (records, pages, files, and other sources) and which updates are running.

Tell us where your information lives.We’ll show you one search across it.

Databases, documents, websites, older systems. Talk to us, and see them searched from one place, within each person’s permissions.