usemoss/moss
The retrieval layer for production AI systems. Lightning-fast (<10ms) search without vector databases. Built for browser, edge, on-device, and cloud.
What it solves
Most retrieval stacks for AI agents rely on remote vector databases, creating network round trips that add 200–500 ms of latency. This lag can break the flow of real-time conversational AI, such as voice bots or copilots, making them feel unresponsive.
How it works
Moss is a search runtime rather than a traditional database. It uses a hybrid architecture consisting of three parts:
- Moss Cloud: Manages document ingestion, embedding, storage, and distribution.
- Index: Packages documents and vectors into a single artifact stored on the cloud.
- Runtime: An SDK embedded directly into the application (available for Python, TypeScript, Elixir, and C). The runtime pulls the index over HTTPS and holds it in memory, allowing queries to be processed locally within the application process to eliminate network hops on the hot path.
It also offers a WebAssembly build for running semantic search entirely within the browser.
Who it’s for
Developers building real-time Conversational AI agents, voice bots, copilots, and offline-first applications that require ultra-low latency retrieval.
Highlights
- Ultra-low latency: Achieves sub-10 ms query times (including embeddings) by running search in-process.
- Hybrid Search: Combines semantic and keyword search in a single query.
- Built-in Embeddings: Includes embedding models out-of-the-box, removing the need for external API keys.
- Browser Support: A WASM-based SDK allows for client-side semantic search without a server.
- Broad Integration: Compatible with major frameworks like LangChain, LlamaIndex, DSPy, and various voice AI platforms (Pipecat, Vapi, ElevenLabs).
Related
- Project
- Project
- Project
- Project
- Project