Self-Hosted Quickstart
Run Probo locally with Docker Compose and set up your first compliance framework
This guide walks you through deploying Probo locally with Docker Compose and setting up your first compliance framework. You should be up and running in about 15 minutes.
For a managed service or a production Kubernetes deployment, compare the deployment options.
Prerequisites
Section titled “Prerequisites”- Docker and Docker Compose installed on your machine
- OpenSSL for generating local secrets
Deploy Probo
Section titled “Deploy Probo”-
Clone the repository
Terminal window git clone https://github.com/getprobo/probo.gitcd probo -
Create the local environment
Generate the required secrets and application settings:
Terminal window cat > .env <<EOFPROBOD_ENCRYPTION_KEY=$(openssl rand -base64 32)PROBOD_AUTH_COOKIE_SECRET=$(openssl rand -base64 32)PROBOD_AUTH_PASSWORD_PEPPER=$(openssl rand -base64 32)PROBOD_TRUST_AUTH_TOKEN_SECRET=$(openssl rand -base64 32)PROBOD_BASE_URL=http://localhost:8080PROBOD_API_ADDR=0.0.0.0:8080PROBOD_API_CORS_ALLOWED_ORIGINS=http://localhost:8080EOFKeep
.envprivate. These values protect encrypted data and authentication sessions. -
Start the services
Terminal window docker compose -f compose.prod.yaml up -dThis starts the Probo server, PostgreSQL, SeaweedFS, and the headless browser used for document generation.
-
Verify the deployment
Terminal window curl --fail http://localhost:8080/healthzdocker compose -f compose.prod.yaml psThe health request should succeed and each service should report a running or healthy state. If it does not, inspect the application logs:
Terminal window docker compose -f compose.prod.yaml logs probo -
Access the web interface
Open http://localhost:8080 in your browser. Create your account and log in.
-
Create your organization
After logging in, create your first organization. This is the top-level entity that contains all your compliance data.
-
Import a compliance framework
Navigate to the frameworks section and import the framework relevant to your business — for example, SOC 2 or ISO 27001. This gives you a set of controls to work with.
Next Steps
Section titled “Next Steps”You now have a running Probo instance with a compliance framework in place. From here, you can start mapping controls to your security practices, collecting evidence, and managing risks.