Skip to content

Suggested searches

    Search all documentation ↑↓ to navigate Enter to open Esc to close

    Self-Hosted Quickstart

    Deploy a local Probo evaluation environment with Docker Compose in about 15 minutes, then import your first compliance framework.

    Markdown

    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.

    Terminal window
    git clone https://github.com/getprobo/probo.git
    cd probo

    Generate the required secrets and application settings:

    Terminal window
    cat > .env <<EOF
    PROBOD_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:8080
    PROBOD_API_ADDR=0.0.0.0:8080
    PROBOD_API_CORS_ALLOWED_ORIGINS=http://localhost:8080
    EOF

    Keep .env private. These values protect encrypted data and authentication sessions.

    Terminal window
    docker compose -f compose.prod.yaml up -d

    This starts the Probo server, PostgreSQL, SeaweedFS, and the headless browser used for document generation.

    Terminal window
    curl --fail http://localhost:8080/healthz
    docker compose -f compose.prod.yaml ps

    The 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

    Open http://localhost:8080 in your browser. Create your account and log in.

    After logging in, create your first organization. This is the top-level entity that contains all your compliance data.

    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.

    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.