SearXNG

Search multiple providers through your own private metasearch instance.

Choose your deployment and the way you want to use Selfhost. The instructions below follow that choice.

Deployment Use Selfhost with

Set up SearXNG

Editable Compose files in your own directory.

Start the service and set its public URL when attaching a domain.
Configure a private Valkey connection before enabling the request limiter.

selfhost app --directory ./searxng init searxng

Initialization writes portable files and does not start the app. Review compose.yaml, the private .env and any files in files/, then start it:

selfhost app --directory ./searxng start

No Selfhost dashboard or background service is needed. You can also start these files directly:

cd searxng
docker compose -f compose.yaml up -d

Connect an existing installation

Use Existing apps → Link an app in the dashboard, or the CLI’s existing-app commands. Choose SearXNG, its URL and, optionally, its exact Docker container on a connected server.

Save existing.json with your app URL. Add server_id and container for container inspection and actions.

{
  "profile": "searxng",
  "name": "SearXNG",
  "url": "https://app.example.com"
}

selfhost existing link --file existing.json
selfhost existing list
selfhost existing inspect EXISTING_ID

Linking enables the existing-app profile’s supported inspection and actions. It does not import Compose or attach the new-deployment settings and onboarding profiles described below.

Existing app commands, permissions and unlinking

Before configuring integrations

The persistent /etc/searxng volume keeps native settings.
Search-engine selection remains in native settings.yml.
There is no built-in user OIDC login contract in this profile.

SearXNG integrations

Compose service: searxng. These operations use the profile saved when this deployment is created.

Native settings

Changes use the app’s Compose environment. Unrelated settings are preserved.

Supported fields (5)

Public URL public-url: string
Proxy image results image-proxy: stringChoices: true, false
Enable request limiter limiter: Requires a separately configured Valkey service. stringChoices: true, false
Valkey URL valkey-url: secret · advanced
Public instance mode public-instance: string · advancedChoices: true, false

Save a JSON map of the field IDs you want to change as changes.json. Replace FIELD_ID with an ID from the supported fields above, and use its declared value type. Review the plan and replace REVIEWED_REVISION with the revision it returns.

{
  "FIELD_ID": "YOUR_VALUE"
}

selfhost app --directory ./searxng config searxng
selfhost app --directory ./searxng plan searxng changes.json
selfhost app --directory ./searxng apply searxng changes.json --revision REVIEWED_REVISION

Saved changes need service recreation to become active. Existing interpolated environment values stay under your control in .env or Compose.

App configuration reference

Versions and updates

This deployment uses the following images. Existing projects retain their saved recipe and images. A new catalogue version does not silently update them.

searxng: searxng/searxng:2026.9.25-12f8b6515

Review compatibility and back up app data before an update. Choose an image version and review the change.

Keep control of your setup

Selfhost remains optional. Your app runs using ordinary Compose files, its own settings and persistent data. Keep the Compose project name and volumes to preserve storage. Configuration exports and setting backups do not include application data.

Standalone CLI guide · Backups and removal · SearXNG documentation