Instead of trusting one search company with every query, degoog is a self-hosted search aggregator that fans each one out to the engines you choose, from your own server, and merges the answers into one deduplicated, ranked list. It installs with no engines at all; a first-run tour then walks you through picking Google, Bing, DuckDuckGo, Brave, Startpage, Reddit, or Wikipedia from the built-in Store. Pages found by several engines collapse into a single row that lists every source, while a sidebar times each engine, explains failures like rate limits or CAPTCHAs, and retries only the one that failed. Tabs appear for each search type your engines serve, and the Images tab adds size, color, layout, and safe-mode filters beside a zoomable preview panel. Bangs target one engine or run commands (!w for Wikipedia, !ip, !speedtest, !uuid), and Store plugins add weather, definitions, QR codes, and search across your own Jellyfin or Meilisearch libraries. Owners can block, rewrite, or score domains, serve a script-free page to text browsers, and turn on an indexer that remembers seen results for later recall. A JSON search API, a SearXNG-compatible response mode for Open WebUI, and an MCP companion feed the same results to scripts and LLM clients. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Up to 280 search services - Google, Bing, DuckDuckGo, Brave, Qwant, Startpage - aggregated without tracking or profiling: SearXNG is a privacy-respecting metasearch engine (AGPL-3.0, successor to Searx). Your instance queries the upstream engines on your behalf: your IP address, cookies, and search history never reach them, tracker parameters are stripped from result URLs, and an optional image proxy fetches thumbnails server-side so result pages leak nothing. It can even route outbound queries through Tor for full anonymity. Search is organized into categories - general, images, videos, news, maps, music, IT, science, files - with bang shortcuts for targeting specific engines, and every source can be enabled, disabled, or weighted per category in settings.yml. A plugin system adds calculators, hash tools, tracker removal, and unit conversions inline, and preferences (themes, safe search, languages, engine selection) persist in cookies rather than server-side accounts. The real argument for running your own instance rather than trusting a public one is control: you decide the logging policy (none), the engine mix, rate limiting, and who gets access - making it the default search backend for browsers, families, and teams that want Google-quality results without the profile.