specterops/bloodhound

Python

20 environment variables found in .env.example

Set these on your host before deploying. Each platform has an “Environment Variables” section in the deploy flow. (showing first 20, more exist in .env.example)

WEB_PORT All Profiles
TRAEFIK_PORT
DEBUG_PORT
BH_CONFIG_FILE
BH_HOSTNAME BloodHound API
BH_PKG_MOD_VOLUME
BH_API_PORT
TOOLAPI_PORT
GRAPH_DRIVER Graph Driver (use neo4j or pg)
BH_PG_ADMIN_HOSTNAME BloodHound PG Admin
BH_PG_ADMIN_EMAIL
BH_PG_ADMIN_PASSWORD secret
BH_PG_ADMIN_PORT
BH_NEO4J_HOSTNAME BloodHound Neo4j
BH_NEO4J_AUTH
BH_NEO4J_ALLOW_UPGRADE
BH_NEO4J_VOLUME
BH_NEO4J_PORT Set NEO4J_VOLUME to a local filesystem mount BH_NEO4J_VOLUME=./local-harnesses/data
BH_NEO4J_WEB_PORT
BH_POSTGRES_USER BloodHound Postgres

Best match Fly.io Anything Dockerized — requires the Fly CLI.

macOS

brew install flyctl && fly launch --from https://github.com/specterops/bloodhound

Linux

curl -L https://fly.io/install.sh | sh && fly launch --from https://github.com/specterops/bloodhound

Windows (PowerShell)

iwr https://fly.io/install.ps1 -useb | iex; fly launch --from https://github.com/specterops/bloodhound

Alternative Deploy on Railway Apps that need Postgres, Redis, or background workers.

Or deploy to a different host

Render Full-stack with managed Postgres + Redis. DigitalOcean App Platform Containers, droplets, and managed services.

← Try another repo