typesense/typesense
Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences observed · 2026-08-28
Health v2 · maintenance only
84/100
- Activity 98
- Release rhythm 56
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 105.5
- age_days: 3514
- days_rel: 136
- days_push: 15
- n_releases_24m: 7
Adoption not part of the score
26481 stars · 965 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Typesense is an open-source, in-memory search engine written in C++ that provides fast, typo-tolerant full-text search with sub-50ms latency, plus vector/semantic search capabilities. It positions itself as an easier-to-use open-source alternative to Algolia, Pinecone, and Elasticsearch.
Use cases
- add typo-tolerant autocomplete search to my website
- build a faceted product browsing experience for an e-commerce store
- self-host an open source alternative to Algolia
- run semantic or hybrid search over documents with vector embeddings
- add geo search to a listings site like Airbnb
- power instant search-as-you-type over millions of records
- index and search my database full-text without Elasticsearch complexity
- use a search engine as a geo-distributed cache close to users
When to choose
- you need instant, typo-tolerant search-as-you-type with minimal configuration
- you want an open-source Algolia replacement without per-search pricing
- Elasticsearch feels too complex or operationally heavy for your use case
- you need combined full-text and vector/semantic search in one engine
- you're building e-commerce search with faceting, synonyms, and merchandising
When to avoid
- you need a general-purpose analytics or log aggregation store - use Elasticsearch or OpenSearch
- your dataset exceeds available RAM, since Typesense is in-memory
- you need complex joins or relational queries - use a database instead
- you require a permissive license - Typesense is GPL-3.0
- you need heavy document ingestion pipelines or complex aggregations
Facets
service · maturity stable
search-engine vector-database caching rag databases e-commerce large-language-models self-hosted cloud cpp typo-tolerance full-text-search fuzzy-search faceting geosearch semantic-search vector-search algolia-alternative elasticsearch-alternative instantsearch synonyms in-memory site-search autocomplete search retrieval-augmented-generation linux macos docker
10 sources
- readme: https://github.com/typesense/typesense · fetched 2026-08-28 · 67681ca5461f
- homepage: https://typesense.org · fetched 2026-08-29 · 6e34d005cf7f
- site_page: https://typesense.org/about · fetched 2026-08-29 · 6474f315d172
- site_page: https://typesense.org/docs · fetched 2026-08-29 · c0e3f87822f3
- site_page: https://typesense.org/docs/guide · fetched 2026-08-29 · 4beecb3d2d71
- site_page: https://typesense.org/docs/overview/use-cases.html · fetched 2026-08-29 · 294d5f3d2a2f
- site_page: https://typesense.org/docs/latest/api/search.html · fetched 2026-08-29 · c80f80ffcf79
- site_page: https://typesense.org/docs/guide/ranking-and-relevance.html · fetched 2026-08-29 · 2474e63c9a4a
- site_page: https://typesense.org/docs/latest/api/synonyms.html · fetched 2026-08-29 · c80f80ffcf79
- site_page: https://typesense.org/docs/latest/api/api-keys.html · fetched 2026-08-29 · c80f80ffcf79
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| typesense/typesense | main | 84 |
For agents
markdown · JSON · MCP: product_card(name="typesense/typesense")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem