Deploy Paperclip (Official Image)

Run AI agent teams (Claude Code, Codex, Gemini) with budgets and approvals

Deploy Paperclip (Official Image)

/var/lib/postgresql/data

Just deployed

/paperclip

Deploy and Host Paperclip on Railway

Paperclip is an open-source control plane for running a company staffed by AI agents. You define goals, an org chart and monthly budgets, then hire agents (Claude Code, Codex, OpenCode, Gemini, Kimi and more) that pick up tasks on a heartbeat, report to managers and ask you for approval when they need it.

About Hosting Paperclip

This template runs the official ghcr.io/paperclipai/paperclip image, pinned to release 2026.1117.0 (no wrapper repo) next to a Railway Postgres 17 database. Both services keep their data on volumes: Postgres holds companies, agents, tasks and users; the /paperclip volume holds agent workspaces, uploaded files, the local secrets key and hourly database backups.

It boots in authenticated mode with private exposure, so every page needs a login, and the first admin is claimed straight from the browser. No CLI and no setup tokens.

Common Use Cases

  • Run a small team of coding agents against your repos with budgets and approvals
  • Give a solo founder an always-on "company" of agents that works through a backlog
  • Try Paperclip on a real URL before committing to your own server

Dependencies for Paperclip Hosting

  • A Railway account (Hobby is enough to start; agents that run CLIs like Claude Code want 2 GB+ of RAM)
  • An API key or subscription login for at least one agent runtime (Anthropic, OpenAI, Google, and so on)

Deployment Dependencies

Implementation Details

Step-by-step guide with screenshots and troubleshooting: https://github.com/hmseeb/paperclip-railway-template#readme

Claiming your instance (do this first)

  1. When the deploy goes green, open the Paperclip service's public URL.
  2. Create an account and sign in.
  3. On the setup screen choose Claim this instance. You are now the instance admin and can create your first company.

Claim it right away. Until someone claims it, the first signed-in user on the URL becomes the admin. Once it is claimed, later sign-ups are ordinary accounts with no access to your companies.

Connecting agents (no terminal needed)

Paperclip signs in to your subscription from the browser. In onboarding or an agent's model settings:

  • Claude subscription: click Claude. Open the Sign in to Claude link, approve, paste the authorization code and click Submit code, then Connect. Paperclip makes a long-lived claude setup-token token, so the connection does not expire overnight.
  • Codex (ChatGPT subscription): click OpenAI. Open the link, enter the code that Paperclip shows, approve, then click Connect.
  • API keys: click Use API key instead under the provider tiles and paste the key.

The Claude Code, Codex, OpenCode, Gemini and Kimi CLIs are already installed in the image.

Updating Paperclip: the image is pinned on purpose, because the template's start command and settings depend on the layout of that exact release. New releases are tested and bumped in this template. Existing deploys can move by redeploying from the template, or by setting the Paperclip service's image to the tag the template now uses.

Newest Claude models: agents use the Claude Code that ships with the pinned Paperclip release. The template also installs the latest Claude Code CLI onto your volume on every boot for the container shell. If a new model is not in Paperclip's model list yet, type its full ID (for example claude-opus-5-5) in the Model box, choose Use manual model, and save.

Variables you might change

VariableDefaultNotes
PAPERCLIP_PUBLIC_URLhttps:// + your Railway domainSet it to your custom domain after adding one
PAPERCLIP_AUTH_DISABLE_SIGN_UPunsetSet to true to close open sign-ups once your team has joined
HEARTBEAT_SCHEDULER_ENABLEDtrueSet to false to pause every agent heartbeat at once

Secrets (BETTER_AUTH_SECRET, PAPERCLIP_AGENT_JWT_SECRET, PAPERCLIP_TOOL_ACTION_SIGNING_SECRET, the Postgres password) are generated per deploy. Do not change BETTER_AUTH_SECRET after users exist; it signs every session.

Upgrading

Change the Paperclip service image tag to a newer release from https://github.com/paperclipai/paperclip/releases and redeploy. Database migrations apply automatically on boot (PAPERCLIP_MIGRATION_AUTO_APPLY=true).

Troubleshooting

  • "Someone else has already claimed this instance": another account claimed it first. If that was not you, delete the project and deploy again, then claim immediately.
  • No claim option on the setup screen: the instance is already claimed (/api/health shows "bootstrapStatus":"ready"). Sign in with the admin account.
  • Health shows a database_backup_missing warning right after deploy: normal. The first automatic backup runs within the hour.
  • Agents fail to start: the agent has no model connection. Connect one from the agent's settings.
  • The sign-in code is rejected or expired: each code works once and for a few minutes. Click Start sign-in again and use the new link.

Why Deploy Paperclip on Railway?

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 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.


Template Content

More templates in this category

View Template
Chat Chat
Chat Chat, your own unified chat and search to AI platform.

okisdev
117
View Template
Weaviate
Vector database with hybrid search and an API key-protected API

GitHub Locker
1
View Template
Möbius Personal AI OS
Self-hosted AI agent that builds and runs apps for you, with memory.

Tracklayer
1