Self-host SearXNG with Levelrail
VerifiedA privacy-respecting metasearch engine that aggregates results from dozens of search services.
- Authorsearxng
- LicenceAGPL-3.0-or-later
- Memory256 MiB
- Archarm64
- Services2
How to self-host SearXNG
-
Pull the images
2 images are pulled on your server.
Show images
redis:7-alpinesearxng/searxng:2026.9.23-3cd69d30e
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
SearXNG requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-or-later, network copyleft (agpl) license
- Verified. Verified on arm64 with image tag 7-alpine. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then SearXNG. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the SearXNG docs page.
Deploy SearXNG your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy SearXNG from the CLI
levelrail-cli templates deploy searxng --name my-searxng Deploy SearXNG with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/searxng/deploy SearXNG configuration
SearXNG services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| redis | redis:7-alpine | none | searxng_redis_data -> /data |
| searxng | searxng/searxng:2026.9.23-3cd69d30e | 8080 | none |
SearXNG environment variables
| Variable | Service | Value |
|---|---|---|
| SEARXNG_REDIS_URL | searxng | Preset by the template |
| SEARXNG_SECRET | searxng | Generated at deploy |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: searxng_redis_data -> /data
SearXNG FAQ
How much memory does SearXNG need?
The catalog lists about 256 MiB of memory for SearXNG across its 2 services.
Does SearXNG run on arm64?
For SearXNG, arm64 is tested; amd64 is image published.
What licence is SearXNG under?
SearXNG is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does SearXNG need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does SearXNG bundle?
The template includes Redis, running as its own service.
Which ports does SearXNG use?
SearXNG listens on port 8080 inside the stack.
Where does SearXNG keep its data?
In a named volume: searxng_redis_data mounted at /data.
Can I deploy SearXNG on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id searxng for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image redis:7-alpine, searxng/searxng:2026.9.23-3cd69d30e is what you deploy there.