Deploy and Host self hosted Paperclip Governance (Open-Source Governance for AI Agent Teams) on Railway

This template runs a self-hosted Paperclip control plane on Railway with Postgres. You act as the board for a company of AI agents: approve hires and the CEO strategy, cap budgets, pause agents, read the activity log.

About Hosting Paperclip Governance open-source software on Railway (self hosted Paperclip agent governance template)

This template runs the pinned Paperclip image on port 3100 with Railway Postgres 18 behind it, a volume mounted at /paperclip, generated 64-hex secrets for auth sessions, agent tokens and secret encryption, plus boot-time migrations.

Railway handles the domain, TLS, Postgres provisioning, health checks on /api/health and volume wiring, so the board work (reviewing hire_agent and approve_ceo_strategy requests) starts on deploy day.

Why Deploy Paperclip Governance, the CrewAI alternative on Railway (Railway Free Trial)

CrewAI gives you a framework and leaves approvals to code you write. Paperclip ships the board room: hire and strategy gates, a hard stop at 100 percent budget, and an audit log. Spin it up on the $5 Railway trial and review one real approval queue.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Paperclip Governance on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Railway vs Other Hosting Providers and VPS for Paperclip Governance self hosting

A raw VPS hands you a box; this template arrives with Postgres and TLS already joined.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Pinned image, managed Postgres, TLS, and the volume ready.	A Droplet and separate Postgres; you write the compose file and proxy.
AWS	Same template, health checks, managed certificates.	ECS or EC2, RDS and an ALB; you own every layer.
Hetzner	Template deploy with domain and database URL injected.	Cheap raw compute; you patch Postgres and back up the volume.

The board controls are identical either way; only the plumbing you own changes.

Common Use Cases for hosted Paperclip Governance

Approve every hire an agent proposes: a manager files a hire_agent request with role, adapter config and budget, and nothing spawns until you approve it.
Sign off the CEO strategy before execution: approve_ceo_strategy holds the CEO's first plan at the gate, so no task moves until you've read it.
Cap a runaway agent with a hard stop: a monthly budget in cents warns at 80 percent and auto-pauses the agent at 100 percent, blocking new work.
Audit who changed what: the activity log records actor, action, entity and details for every mutation, so you can trace a task edit or a budget change.
Request a revision instead of a blunt rejection: add a decision note and the agent reworks the request and resubmits it to the gate.

Dependencies for Paperclip Governance Docker hosted on Railway

Two services: paperclip from ghcr.io/paperclipai/paperclip:2026.1012.0 (pinned by sha256) on port 3100, health /api/health, plus Railway Postgres 18 for DATABASE_URL. Run one replica; migrations run on boot.

Deployment Dependencies for Managed Paperclip Governance Service (AI Agent Governance)

Generated: BETTER_AUTH_SECRET (sessions), PAPERCLIP_AGENT_JWT_SECRET (agent tokens) and PAPERCLIP_SECRETS_MASTER_KEY (company secrets).

Implementation Details for Paperclip Governance (Using Paperclip official docker image)

The start command chains upstream tini, docker-entrypoint.sh (chowns the volume, drops to node), the invite helper and the server command. Deploy logs print a one-time [railway-bootstrap] invite URL valid 72 hours. Keep the master key stable.

How does Paperclip Governance compare against other ways to keep AI agents under human control

Paperclip vs CrewAI (CrewAI Alternative)

Where Paperclip wins: approval queue, budgets and audit log ship in the UI; CrewAI is a Python library you wire in.
Decision notes: you approve, reject or request a revision on hire_agent and approve_ceo_strategy without touching code.
Where CrewAI wins: finer code-level control over agent logic in an existing Python pipeline.

Paperclip vs Microsoft AutoGen (AutoGen Alternative)

Where Paperclip wins: AutoGen is a conversation framework; Paperclip wraps agents in a company a board can pause or terminate.
Audit trail: task, approval, agent and cost changes log an actor, action, entity and details.
Where AutoGen wins: more flexible for experimental multi-agent patterns than a fixed org chart.

Paperclip vs LangGraph (LangGraph Alternative)

Where Paperclip wins: LangGraph makes you build checkpoints and human pauses; Paperclip's gates and budget stops are built in.
Budget stop: a monthly budget in cents warns at 80 percent and auto-pauses the agent at 100.
Where LangGraph wins: deterministic, tightly specified workflows get sharper control from an explicit graph.

Paperclip vs OpenAI Agents SDK (OpenAI Agents SDK Alternative)

Where Paperclip wins: the SDK is a lightweight library; Paperclip is a self-hosted plane with a UI, Postgres and an MIT license.
Model choice: Claude Code, Codex, Gemini CLI and HTTP adapters queue behind the same approvals.
Where the SDK wins: less infrastructure. If guardrails inside one app are enough, a library is a smaller bet.

How to use Paperclip Governance (the OSS AI agent orchestration platform)?

Log in on your Railway domain as the board.
Create a company with a goal and a CEO agent.
Let the CEO propose a strategy, then open the Approvals page.
Review the payload, then approve, reject or request a revision with a decision note. A hire_agent request carries the proposed role and budget.
Set monthly budgets per agent in cents. At 80 percent you get a warning, at 100 percent the agent auto-pauses.
Check the queue from a shell:

curl -b cookies.txt "https://your-domain/api/companies/COMPANY_ID/approvals?status=pending"

The activity log records each decision with your name on it.

How to self host Paperclip Governance on other VPS Services (Paperclip self hosting guide)

You can run the same board controls off Railway. You just take on the Postgres, the volume, and the secret rotation yourself.

Clone the Repository

git clone https://github.com/paperclipai/paperclip
cd paperclip

Install Dependencies

You need Node.js, pnpm, and a Postgres 18 instance. Then install packages:

pnpm install

Configure Environment Variables

Set HOST=0.0.0.0, PORT=3100, SERVE_UI=true, PAPERCLIP_HOME, and DATABASE_URL. Keep the master key stable, because changing it makes existing secrets unreadable. Point PAPERCLIP_PUBLIC_URL and PAPERCLIP_API_URL at your domain so invite links resolve.

Start the Paperclip Governance Application

pnpm build
pnpm start

Migrations run on boot. Run one replica, proxy port 3100, then claim the admin account from the bootstrap invite URL in the logs, and set PAPERCLIP_AUTH_DISABLE_SIGN_UP=true afterwards.

Railway handles the Postgres, the volume, the pinned image, and the generated secrets for you.

Official Pricing of Paperclip Governance (Paperclip pricing)

Paperclip is MIT licensed, so the software is free. There's no per-seat or per-agent fee, and no Paperclip cloud price to compare against here. Your monthly per-agent budget caps are the real cost control, since a paused agent at 100 percent stops spending.

Paperclip Governance cloud vs self hosted comparison (Pricing, features, costs, and more)

The governance features are the same whether Paperclip runs here or anywhere else. The difference is who owns the box, the Postgres instance and the secrets key. Self hosting keeps every approval, budget and activity log entry in your own database.

Monthly cost of self hosting Paperclip Governance on Railway

Expect roughly $10-20/mo for the app plus Postgres at light use, more if agents run coding CLIs in the container. The software is MIT and free. You pay Railway and your model providers. The $5 trial covers the first stretch of approval reviews.

System Requirements for Hosting Paperclip Governance on a VPS

Give the container 2 vCPU and 2 GB RAM at minimum, plus external Postgres for production. Run one replica, keep a persistent volume for /paperclip, and set the three 64-hex secrets before the first boot. Migrations run automatically, so a small instance is fine until agents start executing real work.

Frequently Asked Questions (FAQs)

What needs approval by default?

Hire Agent requests, when a manager proposes a subordinate, and the CEO Strategy before the first plan reaches execution. Both appear on the Approvals page and in the inbox.

Can agents bypass an approval?

No. A hire_agent request stays pending until a board operator approves, rejects or requests a revision with a decision note. Agents hold API keys, but the decision endpoint is yours.

What happens at 100 percent budget?

The agent auto-pauses and new work is blocked.

Can I see who changed a task?

Yes. The activity log records every mutation with actor, action, entity and details, covering task changes, approvals, agent changes and costs.

How do I pause an agent?

Pause it from the agent's board controls. The same place resumes or terminates it, and pausing blocks new work without wiping history.

Can approvals be handled through the API?

Yes. Query pending requests, then approve, reject, request a revision or comment as the board. It's the same queue the UI shows.