Deploy and Host Company Brain Gateway

Company Brain Gateway gives one company governed remote MCP access to a private GitHub Company Brain without giving teammates local Git clones. Each deployment is isolated and owned by the buyer in Railway.

About Hosting Company Brain Gateway

The template deploys two services: the exact Company Brain Gateway v0.1.0 image and a pinned PgVector database. It also creates separate persistent volumes for the repository workspace and database. Only the Gateway receives a public domain; PgVector remains private.

After deployment, use the Gateway administrator interface to bootstrap the first administrator, create the repository deploy key, add its public half to one private GitHub repository, seal the one-time private value in Railway, switch setup mode off, redeploy, then connect and index the Company Brain.

Why Deploy Company Brain Gateway on Railway?

Railway gives each buyer a separate project, private service networking, generated secrets, persistent volumes, health checks, and exact-image deployments. The buyer owns the infrastructure, credentials, data, billing, backup settings, and deployment decisions.

Common Use Cases

Give founders and teammates cited Company Brain retrieval through Codex or Claude Code.
Promote governed decisions, playbooks, and approved company context without sharing a Git clone.
Apply named identity, path boundaries, audit receipts, revocation, and repository/index health checks.
Run the same versioned artifact as a self-serve buyer deployment or an Atlas-managed isolated deployment.

Dependencies for Company Brain Gateway Hosting

You need a Railway account and one private GitHub repository containing the Company Brain. Enter its SSH URL when deploying. Keep repository administration and the generated deploy key restricted to that repository.

Deployment Dependencies

Railway project with persistent volumes and public networking for the Gateway only.
Private GitHub Company Brain repository and its SSH URL.
Codex or Claude Code as the supported remote MCP client.
An authorized operator who can configure and test Railway volume backups.

The template generates database and application secrets. Do not copy secrets, deploy keys, tokens, or one-time reveals into source control, course materials, or support tickets.