SearXNG is a self-hosted metasearch engine that queries configured search services and presents aggregated results. The project recommends Compose for container deployments and supports Docker or Podman. Its installation documentation does not specify a universal CPU, memory, or disk minimum, so capacity depends on traffic, enabled engines, caching, and configuration.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.
Recommended
Documented guidance
No further general recommendations are published for this version.
Capacity depends on your workload
The reviewed official installation documentation does not publish a universal CPU, RAM, or disk minimum. Traffic, engine selection, cache behavior, and rate limiting affect resource use.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
Docker Compose using the project container templates
Docker or Podman container with mounted configuration and cache directories
Manual server installation following the administrator guide
The host must provide
Runtime
Container runtime
Working Docker or Podman for the documented container path
Configuration
A configured settings.yml, including the server secret key and selected engines
Reverse proxy
Recommended when exposing a public instance; use the project's deployment guidance
Storage
Persistent data
Keep the configuration directory persistent, including settings.yml. The container exposes /etc/searxng for configuration and /var/cache/searxng for persistent cache data. The documentation does not state a universal disk minimum.
Step by step
Deploy a SearXNG instance
Choose a container runtime
Install Docker or Podman on the host. The SearXNG guide recommends Compose for container deployments and provides project templates.
Mount the configuration and cache paths so settings and cache data survive container replacement, then review the current Compose template before updates.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official container installation requires a working Docker or Podman installation; Compose is the project-recommended container deployment method.This prerequisite has no comparable published plan field.
A public deployment should be configured with an appropriate secret key, limiter settings, and reverse proxy as applicable.This prerequisite has no comparable published plan field.
