Deploy degoog
Self-hosted search engine aggregator with a plugin and extension store
Just deployed
/app/data
Deploy and Host degoog on Railway
degoog is an open-source, self-hosted search engine aggregator. It sends your query to several search engines at once, and merges and ranks the results on one page. Engines, bang commands, result panels, themes and transports are extensions that you install from its built-in Store.
About Hosting degoog
degoog is a single Bun web server with no required database. Everything it owns (settings, installed engines and plugins, themes, the optional local indexer and its blocklist) lives in one data directory, so hosting it means keeping that directory on persistent storage and protecting the Settings area. Extensions run code on the server, so the Settings area must always sit behind a password. This template deploys degoog 1.2.0 from the official image, pinned by digest and built from a GitHub repo. It mounts a volume at /app/data, generates the settings password, trusts Railway's proxy headers so rate limits work per visitor, and health-checks /readyz.
Common Use Cases
- A private search page for yourself or a team that queries DuckDuckGo, Brave, Wikipedia and others from one place
- A default browser search engine with bangs such as
!wor!gh, added through/opensearch.xml - A customisable search front end for a community, with your own engines, themes and result panels
Dependencies for degoog Hosting
- A persistent volume for
/app/data(included) - Outbound internet access to the search engines you enable
Deployment Dependencies
- degoog source and releases: https://github.com/degoog-org/degoog
- degoog documentation: https://degoog-org.github.io/docs/
- Template repository (Dockerfile, changelog): https://github.com/aalfath/degoog-railway-template
Implementation Details
After deploy. degoog ships with no search engines. Open the public URL, click the gear icon (or go to /settings) and sign in with the DEGOOG_SETTINGS_PASSWORDS value from the service's Variables tab. Then open the Store tab and install the engines you want (for example DuckDuckGo, Brave Search, Wikipedia). The official extensions repository is already added.
Variables. DEGOOG_SETTINGS_PASSWORDS is generated at deploy (it can be a comma-separated list) and PORT is 4444. Nothing has to be filled in. Optional, added later as variables: DEGOOG_PUBLIC_INSTANCE=true for an instance open to strangers (settings move to /admin), DEGOOG_VALKEY_URL for a shared cache, and DEGOOG_POSTGRES to keep the indexer in Postgres. Add a Railway Redis or Postgres service and reference it with a variable such as ${{Postgres.DATABASE_URL}}.
Updates. Each new degoog release becomes a commit to the template repo that bumps the pinned version, with a changelog entry. Railway then shows an "update available" notice in your project and you choose when to apply it. Your volume is kept across updates.
Why Deploy degoog on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying degoog on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
