Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A multiuser vulnerability management platform that collects and normalizes results from security scanners into shared workspaces, with dashboards and visualizations for analysts and managers. Findings are loaded through more than 80 supported tools through plugins, by importing report files such as XML or JSON, or through the REST API and the faraday-cli command line client. Remote scans can be run through the separate Faraday Agents Dispatcher. The open-source server runs on PostgreSQL with Redis and Celery workers; Commercial Professional and Corporate editions are sold by the vendor.
Runs on a VPS from $24/mo (Kamatera 8GB, 8 GB RAM) · prices checked Nov 2026
Fits home hardware (493 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Faraday when a security team needs one shared place for scanner and pentest results, with analysts working in the same workspaces. The README describes it as a way to use community tools in a multiuser way: it aggregates and normalizes the data you load, with dashboards for managers and analysts. Findings come in through plugins for more than 80 tools, by importing report files such as XML or JSON, or through the REST API and the separate faraday-cli client, and the Faraday Agents Dispatcher can run scanners remotely. The community server is GPL-3.0 Python on PostgreSQL with Redis and Celery workers. Our snippet follows the repository's `docker-compose.yaml` (server, worker, beat, Postgres, Redis) with every Faraday service on `faradaysec/faraday:5.25.4` (released 2026-10-29) instead of `latest`, Postgres moved from upstream's `12.7-alpine` to `17.11-alpine`, Redis pinned to `8.4.8-alpine`, and generated database and admin passwords in `.env`. The FAQ system-requirements table lists 4 GB RAM as the minimum and 8 GB or more as recommended, so our floor is that 4096 MB. In the catalog, DefectDojo is the closest alternative, also collecting scanner findings with products, engagements and SLAs; Dependency-Track tracks vulnerable components from SBOMs, CrowdSec bans abusive IPs, and step-ca issues certificates. Faraday is the one the README builds around a multiuser workspace for scanner output.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Faraday — adapted from upstream docker-compose.yaml (faraday-server, worker and beat, Postgres, Redis), images pinned to faradaysec/faraday:5.25.4
# Changed from upstream: generated Postgres and admin passwords in .env (upstream uses postgres/postgres and a random admin password printed to the logs), Postgres 17.11 and Redis 8.4.8 pinned, the manual-profile helper services and image build block dropped
mkdir faraday && cd faraday
echo "DB_PASSWORD=$(openssl rand -hex 16)" > .env
echo "FARADAY_PASSWORD=$(openssl rand -hex 12)" >> .env
cat > docker-compose.yml <<'EOF'
x-faraday-env: &faraday-env
PGSQL_USER: faraday
PGSQL_PASSWD: ${DB_PASSWORD}
PGSQL_HOST: db
PGSQL_DBNAME: faraday
REDIS_SERVER: redis
services:
db:
image: postgres:17.11-alpine
restart: always
environment:
POSTGRES_USER: faraday
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_DB: faraday
volumes:
- db:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U faraday -d faraday"]
interval: 5s
timeout: 5s
retries: 10
redis:
image: redis:8.4.8-alpine
restart: always
faraday-server:
image: faradaysec/faraday:5.25.4
restart: always
entrypoint: /entrypoint.sh
ports:
- "5985:5985"
volumes:
- faraday:/home/faraday/.faraday
environment:
<<: *faraday-env
FARADAY_PASSWORD: ${FARADAY_PASSWORD}
depends_on:
db:
condition: service_healthy
redis:
condition: service_started
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:5985/_api/config"]
interval: 20s
timeout: 5s
retries: 10
faraday-default-worker:
image: faradaysec/faraday:5.25.4
restart: always
command: ["faraday-worker"]
volumes:
- faraday:/home/faraday/.faraday
environment: *faraday-env
depends_on:
faraday-server:
condition: service_healthy
faraday-beat:
image: faradaysec/faraday:5.25.4
restart: always
command: ["faraday-beat"]
volumes:
- faraday:/home/faraday/.faraday
environment: *faraday-env
depends_on:
faraday-server:
condition: service_healthy
volumes:
db:
faraday:
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:5985/_api/config; do sleep 3; done'
# → http://SERVER_IP:5985 (log in as faraday with FARADAY_PASSWORD from .env)Faraday's README, FAQ, Docker guide, release notes and entrypoint script flag these before you rely on it:
Faraday used 493 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 4096 MB.
The Faraday install snippet is marked verified on Ubuntu 26.04 (Nov 2026).