Tool
SearXNG
A free metasearch engine you can self-host: it fans queries out to many upstream engines and shows combined results without making you the product. Public instances exist; your own instance is the honest long-term path.
What it is
SearXNG is a metasearch front end. You type a query once; it asks enabled engines (web, images, news, and more, depending on config), merges and ranks results, and returns a page that does not profile you the way a commercial search account does. You can use a public instance or run your own. Docs cover engines, settings, and theming. Source lives at github.com/searxng/searxng.
What it replaces
It replaces “default browser search bar always hits one Big Search account” when you want aggregated results with less personalization theater — especially beside a homelab reverse proxy and private reach via Tailscale.
It does not replace owning an index. Upstream engines still decide what exists; CAPTCHAs, blocks, and rate limits hit your instance (or the public one you use). It is not a VPN, an ad blocker, or a full privacy suite by itself.
License
SearXNG is released under the GNU Affero General Public License v3.0 (AGPL-3.0), verified from the project’s primary LICENSE on GitHub. If you modify it and offer it as a network service, AGPL source obligations apply. Public instances have their own operators and policies; self-hosting means you own ops, abuse risk, and upstream breakage.
Where it falls over
- Upstream engines block or CAPTCHA aggressive scrapers — a busy public instance (or a poorly tuned private one) gets throttled or empty result sets.
- Self-hosting is not “install and forget”: Docker/compose, TLS, updates, and engine config need attention.
- Result quality depends on which engines you enable and how healthy they stay; it is not magically better than Google for every query.
- Public instances see other people’s queries — do not type secrets into a stranger’s box.
- AGPL-3.0 matters if you fork and expose a service; read the license before commercial wrapping.
- Does not encrypt your ISP path; pair with sane networking if privacy is the point.
Who it's for
Homelab operators and privacy-minded users who want a single search UI over multiple engines without a commercial search account as the default — especially next to Caddy/Nginx Proxy Manager and Tailscale. Not a substitute for understanding that upstream still holds the index.
Related in this cluster
- Docker — usual self-host install path
- Caddy — reverse proxy with automatic HTTPS
- Nginx Proxy Manager — UI-shaped reverse proxy path
- Tailscale — private reach without hanging search naked on the public net
- Vaultwarden — another “own the box” privacy-adjacent service
- Self-hosting hub — more open replacements and plumbing
Verdict
Use SearXNG when you want metasearch you control, with AGPL-3.0 source you can audit. Prefer your own instance for anything sensitive; treat public instances as convenience, not a vault. Expect upstream friction — this is aggregation, not a private Google clone.
← Tools · Self-hosting · Home · docs · GitHub