typesense

Deploy self-hosted Typesense search with typo tolerance and faceting.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/jeo-skills --skill typesense
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typesense
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/typesense
Command: npx skills add https://github.com/akillness/jeo-skills --skill typesense

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, pip, typesense, uv, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Stand up a self-hosted, typo-tolerant search environment with Typesense — the open-source Algolia / ElasticSearch alternative (single C++ binary, <50ms instant search, no runtime deps).

This provides a routing-first wrapper to deploy server modes (binary, Docker image, or managed Cloud), wire official client libraries, model a collection schema, index documents, and run typo-tolerant search with facets, geo-search, sorting, grouping, synonyms, and scoped API keys, then connect an InstantSearch.js UI and a Raft-based HA cluster for production. Use cases include building site/app/product search, migrating from Algolia/Elasticsearch, or adding search to catalogs, docs, or e-commerce experiences.

Core Features & Use Cases

  • Typo-tolerant search with faceting, filtering, and ranking for site/app data
  • Multi-mode deployment: Docker, binary, or Cloud; official clients for Python/JS/PHP/Ruby and community clients
  • High availability with Raft-based clustering and an InstantSearch UI integration for production search

Quick Start

Install Typesense via Docker or binary, install a client, design a collection schema, index documents, and perform a search.

Frequently Asked Questions about typesense

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a self-hosted, typo-tolerant search engine for my application?

You can set up a self-hosted search engine by deploying Typesense via Docker, binary, or Cloud mode. This environment wraps the routing-first deployment to wire official client libraries, model collection schemas, and index documents for instant search.

What is the best way to migrate from Algolia or Elasticsearch to a self-hosted search backend?

Migrating to a self-hosted search backend involves using Typesense as an open-source alternative. It provides a single C++ binary with no runtime dependencies, supporting typo tolerance, faceting, filtering, and ranking to replace Algolia or Elasticsearch functionalities.

Does this self-hosted search engine support high availability and geo-search for e-commerce catalogs?

Yes, the self-hosted search engine supports geo-search and high availability through a Raft-based clustering mode. It handles e-commerce catalog data by providing faceted search, sorting, grouping, and scoped API keys for production-level search experiences.

Can I integrate an instant search UI with my self-hosted search backend?

Yes, you can integrate an instant search UI by connecting InstantSearch.js with your self-hosted search backend. This allows you to build site, app, or product search experiences with sub-50ms latency and typo tolerance.

How do I design a collection schema and index documents for a faceted search experience?

To design a collection schema and index documents for faceted search, use the official Python, JS, PHP, or Ruby client libraries. This setup enables typo-tolerant search with filtering, sorting, grouping, and synonyms across your site data.

What are the limitations of using a single binary search engine for production site search?

A single binary search engine runs without runtime dependencies but requires a Raft-based HA cluster for production high availability. It satisfies requirements for scoped API keys and federated multi-search but needs proper Docker, binary, or Cloud deployment configuration.