SearXNG
Tool, web search, by SearXNG
Assessment
The right single web search for a home system: one endpoint, no key, configurable. Treat it as egress like any paid API, because it forwards queries from the home connection, and give it a keyed fallback for the days an engine blocks it.
2026-10-09
Strengths
- One JSON endpoint over many search engines, self-hosted
- No account, no key, no per-query cost
- Engine selection and categories in configuration
Limitations
- Self-hosted is not private: queries leave from the home address
- Engines rate-limit or block scrapers; results vary day to day
SearXNG is a self-hosted metasearch engine: it sends a query to a configurable set of search engines, merges the results, and returns them as HTML or JSON.[1] Running in a container, it gives every tool on a network one GET /search?q=…&format=json to call.
What it is for
Web search from agents and services: a weather question, a product lookup, current facts, research. One backend means one place to log every query and one place to enforce what may be asked.
The privacy misunderstanding
Self-hosted does not mean the query stays home. SearXNG forwards it to the engines from the home connection, so the engines see the home address and the words.[2] Under a rule that nothing leaves the network without a reason, SearXNG counts as leaving, and the same discipline applies: an approved reason per use, no identifiers in a query, every request logged.
Things to know
- Engines block scrapers intermittently; a keyed API such as Brave as a fallback keeps a tool working on those days.
- Space out background queries. Urgency rarely helps a nightly job and a burst gets the instance blocked.
- Keep the JSON format enabled in the configuration; it is off by default.
History
- 2026-10-09: article written and published.
- 2026-10-09: entry created.
Comments
Public comments on each entry are coming. Nothing is collected here yet.