Quick start

Cloud-hosted
Self-hosted

The fastest way to get started is with the cloud-hosted version of Probo.

Create your account

Visit app.getprobo.com and sign up for a free account.

Create your organization

After signing in, create an organization for your company. This is the top-level container for all your compliance data.

Select a compliance framework

Navigate to Frameworks and select the framework you want to pursue — SOC2, ISO 27001, GDPR, HIPAA, or others. Probo will populate a pre-built set of controls to work through.

Invite your team

Go to Settings → Team and invite colleagues. Assign roles (Owner, Admin, Employee, Viewer, Auditor) based on their responsibilities.

Compliance frameworks

Understand how frameworks, controls, measures, and evidence fit together.

Roles and permissions

Learn about the five roles and what each one can do.

Run Probo on your own infrastructure using Docker Compose and a single Go binary.

Prerequisites

Before you begin, make sure you have:

Go 1.21+ — download
Node.js 22+ — download
Docker — download
mkcert — for local TLS (brew install mkcert or see docs)

Setup

Clone the repository

git clone --recurse-submodules https://github.com/getprobo/probo.git
cd probo

The --recurse-submodules flag is required — Probo uses Git submodules for some dependencies.

Install dependencies

# Install Go dependencies
go mod download

# Install Node.js dependencies
npm ci

Start infrastructure services

make stack-up

This starts PostgreSQL, SeaweedFS (S3-compatible file storage), Mailpit (local email), Chrome (for PDF generation), and the observability stack via Docker Compose.

Build the project

make build

This compiles the Go binary and bundles the React frontend into bin/probod.

For faster iteration on backend changes only, skip the frontend build: SKIP_APPS=1 make build

Start Probo

bin/probod -cfg-file cfg/dev.yaml

The application will be available at http://localhost:8080.

The cfg/dev.yaml configuration uses insecure placeholder secrets and is intended for local development only. Never use it in production. See Deployment for production configuration.

Testing custom domains (optional)

To test the trust center custom domain feature locally, add the CNAME target to your hosts file:

# macOS / Linux: edit /etc/hosts
# Windows: edit C:\Windows\System32\drivers\etc\hosts
127.0.0.1 custom.getprobo.com

The CNAME target is configured in cfg/dev.yaml under custom-domains.cname-target.

Deployment

Production deployment with Docker Compose.

Configuration reference

All configuration options for self-hosted Probo.

Get Started

Core Features

Access & Security

Integrations

Self-Hosting

Compliance frameworks

Roles and permissions

Prerequisites

Setup

Testing custom domains (optional)

Deployment

Configuration reference

Build docs developers (and LLMs) love

Get Started

Core Features

Access & Security

Integrations

Self-Hosting

Compliance frameworks

Roles and permissions

​Prerequisites

​Setup

​Testing custom domains (optional)

Deployment

Configuration reference

Build docs developers (and LLMs) love

Prerequisites

Setup

Testing custom domains (optional)