Deploy and Host Probo — Latest on Railway

Probo is open-source compliance management software for organizing controls, evidence, risks, vendors, policies, and audits.

About Hosting Probo — Latest

This template deploys the latest Probo release tested by this template, currently v0.271.0, with PostgreSQL, a Railway Bucket, and headless Chrome. The Probo and Chrome images are pinned by immutable digest so every deployment is reproducible; the repository updates those pins only after the new release passes its deployment tests.

It supplies current PROBOD_* variables, complete HTTPS origins, Railway bucket addressing, a persistent RSA OAuth signing key, and fixes for Railway's root-owned volume.

No OpenAI key is required for MCP-first operation through Codex. When the variable is left blank, the wrapper uses a clearly non-secret placeholder solely to satisfy Probo v0.271.0 startup wiring. The application and MCP remain available; Probo's built-in AI features require a real provider key.

EU-first deployment

Railway templates inherit each deployer's preferred account region; the template composer cannot force a region for every user. For an EU deployment, set Account Settings → Preferred Region to EU West Metal (Amsterdam, Netherlands) before deploying. Do this before project creation because the Railway Bucket region cannot be changed later.

After deployment, verify that Probo, PostgreSQL, Chrome, and Bucket all show EU West. The attached Probo and PostgreSQL volumes follow their services' region. Users may deliberately select another Railway region before deployment.

Common Use Cases

Self-host an MCP-first Probo compliance workspace
Use Codex through the authenticated Probo MCP
Run guided company and ISO/IEC 27001 onboarding
Inventory existing compliance documents from approved connectors
Run evidence collection and document workflows

Dependencies for Probo Hosting

A Railway account
SMTP credentials only if invitations, password resets, or notifications are required
An OpenAI key only if Probo's built-in AI features are required

Codex onboarding

Start with the Codex and Probo MCP onboarding interview. It asks for:

the selected Probo organization and company context;
current compliance documents, evidence, owners, status, and locations;
scoped Google Drive, GitHub, or other Codex connectors;
permission to use an existing Chrome session for named sources without a connector and for Probo UI verification.

Codex works read-only first, distinguishes evidence from blank templates, retains source links, and shows a normalized company-context draft for approval. After approval it updates only the selected organization's context through the current Probo MCP schema, re-reads it, and reports the verification result. Remaining imports and consequential writes require separate approval. Users should never paste passwords, tokens, API keys, or session cookies into the onboarding answers.

ISO/IEC 27001 starter kit

The image bundles a Probo-native ISO/IEC 27001 starter kit. On first boot it seeds an editable copy at /data/starter-kits/probo-iso27001 and preserves operator changes on later restarts and upgrades.

The kit includes the onboarding interview, organization discovery questionnaire, Clause 4-10 document structures, risk and SoA planning, objectives, monitoring, internal audit, management review, operational evidence registers, and a Probo MCP import map.

It never auto-imports records. Follow the starter-kit README, inventory the selected tenant read-only, prepare a manifest, and obtain explicit approval before writes. Draft templates are not operating evidence or a declaration of conformity.

Operational notes

Back up PostgreSQL and the Railway Bucket as one recovery point. The /data volume contains the editable starter kit and generated runtime material such as the OAuth signing key; it does not replace database and object-storage backups.

Why Deploy Probo — Latest on Railway?

Railway hosts the application, database, object storage, and supporting browser service in one reusable stack. The template supplies private service references and public networking so operators can focus on using Probo through Codex instead of recreating its infrastructure.