Velociraptor

Velociraptor is a Digital Forensics and Incident Response (DFIR) platform for triaging and hunting malicious activity across Linux, macOS, and Windows…

  • Security
  • Tools & Utilities
Velociraptor is a Digital Forensics and Incident Response (DFIR) platform for triaging and hunting malicious activity across Linux, macOS, and Windows endpoints. This Unraid container runs the Velociraptor server with a multi-arch image, automatic self-signed HTTPS, and prebuilt client bundles, giving security teams and homelabbers a ready-to-deploy incident response hub.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
82last commit 47 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 29 days ago

GitHub stars
0
Open issues
1
Last commit
2026-10-05
License
MIT
Activity
stale

Checked 9 days ago - source: GitHub (Xboarder56/velociraptor-docker)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create the API client config first Before running pyvelociraptor, generate an api_client.yaml file from the Velociraptor server and use --config to point to it. Without that file, the tool cannot sign in to the server, so queries and artifact collections fail. source
  • Keep your API config private Store api_client.yaml in a secure place and avoid committing or sharing it. That file holds credentials for the Velociraptor API, and if someone gets it they can issue queries and collect data from your clients. source
  • Install pandas for tables If you plan to use the examples that return pandas DataFrames (tabular results), install pandas first. Without it, those Python snippets error out even if your API connection works. source
  • First run On first start the container auto-generates server.config.yaml and client.config.yaml and repacks Linux, macOS, and Windows client bundles into /velociraptor/client_bundles/. source
  • Login Open https://[Unraid-IP]:8889, accept the self-signed TLS certificate, and log in with the credentials set via VELOX_DEFAULT_USER / VELOX_DEFAULT_PASSWORD. source
  • Ports and storage Mount /mnt/user/appdata/velociraptor to /velociraptor to persist config, keys, artifacts, and client bundles; expose ports 8000 (client/ingest), 8001 (gRPC API), 8889 (GUI), and 8003 (Prometheus). source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where is persistent data stored in the Docker image?

Mount a host directory to /velociraptor. It stores the server and client configuration, keys, artifacts, and repacked client bundles.

Which ports should be published?

Publish 8000 for client/ingest, 8889 for the HTTPS web GUI, 8001 for the gRPC API, and 8003 for Prometheus metrics.

How do I log in on first run?

Open the GUI on HTTPS port 8889, accept the self-signed certificate, and use the bootstrap admin user and password. Change the bootstrap credentials immediately.

How do clients reach a reverse-proxied server?

Set VELOX_FRONTEND_HOSTNAME, VELOX_FRONTEND_PORT, and VELOX_FRONTEND_SERVER_SCHEME, or set VELOX_FRONTEND_SERVER_URL as a full override. These variables are read at container start.

What SELinux mount label is needed?

On SELinux-enforcing hosts, label the bind mount for the container by adding :Z to the /velociraptor volume mount.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads