Observed Signal · Jul 3, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
Browser-native semantic search with WASM under 1ms
A developer describes building browser-native semantic vector search using a small WebAssembly module and in-browser embeddings so search can run without a backend, API keys, or per-query cost. The author built altor-vec (HNSW compiled to a 54KB WASM module), demonstrates a build-time index generation using a local embedding pipeline (Xenova/all-MiniLM-L6-v2 via the transformers pipeline), and shows a React integration that loads the WASM index and runs queries in the browser. Reported metrics include <1ms p95 query time for 10K vectors in Chrome, ~17MB index size for 10K docs, and a ~23MB embedding model first-load. The approach is positioned for public documentation sites, marketing sites, and similar use cases where index updates happen at deploy time.
Provides a low-cost, client-side approach to semantic search for documentation and marketing sites; relevant to teams wanting serverless, privacy-friendly search without per-query billing but not industry-shifting for core AdTech/MarTech platforms.
Track Algolia Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- altor-vec is an HNSW vector search compiled to a 54KB WASM module and served as a static index.
- Reported query time: <1ms p95 for 10,000 vectors (384 dimensions) in Chrome.
- Index size: ~17MB for 10,000 documents; embedding model first-load: ~23MB.
- Index is generated at build time using an embedding pipeline (example uses 'Xenova/all-MiniLM-L6-v2' via @huggingface/transformers) and serialized to a binary file served from a CDN.
- Per-query monetary cost: $0 (no server or per-query API billing when embedding in-browser or precomputing embeddings at build time).
Connected Companies & Entities
2 Entities mapped“My documentation site had search that sent every user query to Algolia....”
“import { pipeline } from '@huggingface/transformers';...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Client-side semantic search without server or vectors
A technical post describing a client-side semantic search engine for a 796-page static site that runs entirely in the browser with no server-side model or hosted vector DB. The implementation ships three static JSON artifacts (lex.json, index.json, body.json) and a single 401-line JS ranking engine. It uses a Model2Vec-style distilled per-word 384-dimensional vector table (quantized to int8) derived from Xenova/all-MiniLM-L6-v2, BM25 lexical and full-text channels, and Reciprocal Rank Fusion (RRF, k=60) on ranks rather than scores. The design favors privacy (no third-party embedding calls), progressive loading of channels, and deterministic, testable behavior; the article also documents concrete tradeoffs (loss of context, accent/tokenization issues, coverage drift) and measurements showing where the approach excels or fails. Published 2026-08-14.
Building a Vector Search Engine with HNSW
A technical explainer by Ebenezer Akinseinde that walks through the math and mechanics of building a vector search engine using Hierarchical Navigable Small World (HNSW) graphs. The article describes how text is mapped to high-dimensional embeddings (example: Google’s text-embedding-004), compares common similarity metrics (cosine similarity, dot product, L2 distance), and demonstrates a TypeScript HNSW implementation with insertion and search routines. It outlines why brute-force KNN fails at scale and shows HNSW’s complexity benefits (O(N) → O(log N)), plus production techniques such as memory-mapped files (mmap) and Product Quantization (PQ) to reduce memory and storage. The full piece includes an interactive 2D sandbox for visualizing queries, and practical engineering takeaways (e.g., L2-normalize embeddings on ingestion).
VS Code Open-Sources Docfind: Client-Side Wasm Search
The VS Code engineering team open-sourced docfind, a Rust-written search engine compiled to WebAssembly that embeds a website's search index into a compact ~2.7MB binary. Docfind's CLI turns a documents.json input into two artifacts (docfind_bg.wasm and docfind.js) which are served to users; searches run entirely in the browser with no backend requests, near-native execution speed (~0.4ms per query) and no API costs. The implementation uses RAKE for keyword extraction, FSST for string compression and FST for indexed lookup. Docfind targets static, build-time content (docs, blogs, static catalogs) and carries trade-offs around cache-busting and unsuitability for highly dynamic data.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.