Degoog

Degoog is a self-hosted search aggregator that queries multiple search engines at the same time and merges the results into a single ranked list.

  • Network Services
  • Other
  • Productivity
  • Security
  • Tools & Utilities
  • Web & Publishing
Degoog is a self-hosted search aggregator that queries multiple search engines at the same time and merges the results into a single ranked list. You can add custom search engines, bang-command plugins, slot panels above or below the results, and custom HTTP transports such as curl or FlareSolverr, giving privacy-minded homelab users one ad-free search box that runs entirely on their own server.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 14 days ago
Popular
682,545 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM
Security check
89no serious findings, 1 minor, CI, tests

Availability: platform listings confirmed today, links checked 3 days ago

GitHub stars
2,545
Open issues
22
Last commit
2026-11-06
Latest release
1.1.1
License
AGPL-3.0
Activity
declining

Checked 7 days ago - source: GitHub (degoog-org/degoog)

Resources & Compatibility

Minimum requirements: 2 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Sign in before using the store Some store features, like installing or listing items, require auth (a login/check that proves who you are). Without it, those store actions will be blocked and the store may not work as expected. source
  • Open /settings after startup After the app is running, visit the /settings page to reach its settings area or access gate. If you skip this, the app may stay unconfigured or gated, which can prevent normal features from working. source
  • Default Port and User Degoog binds every interface (0.0.0.0) on port 4444 by default, running as user 1000:1000; see the environment variables page in the docs to change these. source

Fetched 32 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What port and data directory permissions should I use for degoog?

It runs on port 4444 by default. Create a data directory and chown it to 1000:1000 before starting the container.

What should I set before exposing degoog to the internet?

Set DEGOOG_SETTINGS_PASSWORDS before exposing the instance. Without protection, anyone can install extensions that run code on the server.

When do I need Valkey or Postgres with degoog?

Add Valkey for multi-replica or public instances so the shared cache keeps settings and invalidation in sync. Use Postgres for busy public instances with a large indexer because it scales concurrent writes and FTS better than SQLite.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads