Home / Engine / Alternatives / Typesense

StackGrep Engine vs Typesense

Typesense is an open-source, typo-tolerant search engine that keeps its index in memory, self-hosted or on Typesense Cloud. Regex queries aren't supported (people ask for them in its GitHub issues). StackGrep Engine is something else: exact text and regex search over your own documents, built for AI agents, with every match counted and your index kept in object storage.

Join the waitlist See the engine

What StackGrep does differently

  • Regex search over whole documents, which Typesense doesn't support
  • The index lives in object storage, not in RAM, so big collections don't need big servers
  • Exact counts of every match
  • Sync straight from your S3 bucket
  • Hosted MCP server for agents

When Typesense is the better pick

If you want an open-source engine you host yourself, with typo tolerance, faceting and as-you-type search for a front end.

Three calls to try it

POST /api/collections/docs/docs     {"docs": [{"id": "a1", "text": "...", "meta": {"team": "ops"}}]}
GET  /api/collections/docs/search?q=net+30&filter=team:ops
GET  /api/collections/docs/count?q=net+30

Quickstart →

Questions

Is StackGrep open source?

Not today. The engine is written in Tern, our own language, which opens soon at ternlang.dev.

Does StackGrep need my data in memory?

No. Collections are stored as compact index segments in object storage and cached where searches run, so memory isn't what limits size.

Other comparisons

Use cases

Give your agents exact search

StackGrep Engine is onboarding teams from the waitlist. Bring your documents or your bucket.

Join the waitlist Read the docs