divid3

Private, on-device search routing.

divid3 is a meta-search router that runs entirely in your browser. It uses a small local ML model to read your intent, then sends you to whichever search engine you've decided handles that kind of query best — without a server, an account, or a middleman.

Try the hosted instance at divid3.com

---

⚡ What you get

• Private by design. Classification happens in your browser's WASM heap. No telemetry, no server logs, no query stream for someone else to monetize.
• You decide where queries go. All routing is configured by a single JSON file you control. Self-host with only the destinations you trust; remove anything you don't.
• Semantic intent. A 22 MB all-MiniLM-L6-v2 model embeds your query and picks the best-matching destination from your configured set.
• Bangs. DuckDuckGo-style shortcuts (!yt, !eb, !m, …) that always win over the semantic router.
• Rule-based fallbacks. Bare domains (github.com) and localhost:3000 route directly. Low-memory phones get a deterministic keyword router instead of the model.
• Choose-don't-autoroute on mobile + ?q= URLs. No 4-second countdown. On mobile and on any link with a query string (e.g. browser-bar searches), the router shows you the top match plus the ranked alternatives and waits for you to tap. Desktop typing still routes immediately because the live score chips already let you click any destination.
• No build step. Pure HTML / CSS / vanilla JS. Easy to audit. Easy to self-host.

---

🛡 Self-hosting & the privacy story

divid3 is built for people who want a search bar they actually trust — even when the destination itself isn't end-to-end private. The threat model is:

1. Where the query is read. On your device, by a model whose weights are committed to the repo. You can read the script that builds the embeddings (scripts/generate_search_embeddings.py) — there is no remote inference.
2. What gets sent over the network. Only the final HTTPS request to whatever engine you tapped. divid3 itself doesn't see any of it; there's no /api/route to intercept.
3. What you control. The full set of destinations, their URL templates, their bang shortcuts, and the keyword/embedding rules that pick between them. Delete an engine from scripts/search_phrases.json and it's gone everywhere, including from the on-device classifier.

You're welcome to ship a fork that points only at Kagi, Brave, SearXNG, your own engine, or anything else. Same code, your engines.

---

🛠 How routing works

1. Bangs. Regex match for !yt, !eb, etc. Always wins.
2. Explicit rules. Bare-domain (github.com) and localhost:port detection.
3. Semantic match. Transformers.js embeds the query and scores each destination by the mean of its top-3 cosine similarities against that destination's phrase corpus. Top-3 pooling (instead of plain nearest-neighbor) means a single stray phrase can't hijack a route — three examples have to agree. Explicit intent markers the keyword rules know about (near me, pictures of, music video, used, …) add a small, capped boost on top (0.03 per keyword point, max 5 points), so an unambiguous cue isn't outvoted by a fuzzy semantic neighbor.
4. Keyword fallback. When the model isn't usable (low-memory device, repeated crashes, ?lite=1), a deterministic weighted-keyword scorer takes over.
5. DDG as the universal fallback. In keyword mode, queries with no matching keywords fall back to DuckDuckGo (HTML) by default.

Measured accuracy

Routing quality is measured by scripts/eval_routing.py against a held-out benchmark of 582 labeled real-world queries (scripts/routing_benchmark.json — the validator enforces that no benchmark query is ever copied into the training phrases):

Router	Accuracy
Semantic (top-3 cosine + keyword boost)	98.8%
Keyword (?lite=1)	98.1%

Run it yourself after any corpus edit:

python3 scripts/eval_routing.py                      # full report + misroute analysis
python3 scripts/eval_routing.py --query "best ramen" # probe a single query

The misroute report names the exact phrase that "won" each wrong routing, which makes corpus debugging mechanical: find the hijacking phrase, sharpen or remove it, re-run.

---

🚀 Destinations

The router decides what kind of search a query is. Destinations (footer link, or press D) lets each person choose which site that kind opens. The defaults are below: every one works without an account, and they're spread across different companies rather than one. Every route offers alternatives such as ChatGPT, Claude, Lumo, Duck.ai or Perplexity for AI answers, X, Reddit, Bluesky or Google News for news, DuckDuckGo, Brave, Startpage or Google for web, Google Maps or Apple Maps for maps, and Amazon, Walmart, Target, Best Buy, Costco or Facebook Marketplace for shopping. Picks are saved in the browser's localStorage, never sent anywhere, and only when they differ from the defaults. The full list lives in destinations in scripts/search_phrases.json.

This is the beginning of the README. Read the rest at the original. Read the full README ↗