Deploy and Host GitTerm on Railway

GitTerm runs your coding agents in remote workspaces you can reopen from anywhere. Pick your agent (OpenCode or T3Code), bring your own model keys, and run workspaces across Railway, AWS, E2B, Daytona, Cloudflare, Vercel, and more.

About Hosting GitTerm

This template deploys the full GitTerm stack: web app, API server, proxy, background worker, Postgres, and Redis. On first boot the server runs migrations, seeds built in catalog data, and creates your admin user from ADMIN_EMAIL and ADMIN_PASSWORD. After that you configure workspace providers in the admin UI and start creating workspaces. Path routing works on a single domain with no extra DNS work. Use subdomain routing only if your domain has wildcard DNS and a wildcard TLS cert.

Why Deploy GitTerm on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you do not have to deal with configuration, while allowing you to vertically and horizontally scale it. By deploying GitTerm on Railway, you are one step closer to supporting a complete full stack setup with minimal burden. Host your app, databases, workers, and AI agents on Railway.

Common Use Cases

Run OpenCode or T3Code in the cloud and code from any device
Keep a persistent workspace alive across sessions and pause it when idle
Preview workspace apps on live URLs and share them with teammates
Run agent work on the provider that fits the job, from sandboxes to your own cloud

Dependencies for GitTerm Hosting

web: dashboard and auth UI
server: main API, runs migrations and seeds on startup
listener: webhook and event ingress
worker: background reaper for idle workspaces. Runs as a cron job on Railway cron, not as an always-on service. Default is every 15 minutes, change it in the worker service cron schedule.
proxy: Caddy reverse proxy in front of everything
PostgreSQL: primary database
Redis: cache and pub/sub

Deployment Dependencies

ADMIN_EMAIL (required): your admin login
ADMIN_PASSWORD (required): your admin password
Provider credentials later, set inside the admin UI (Railway, AWS, E2B, Daytona, and others)
GitHub App or PAT for repo access (optional, set inside the admin UI)
Docs: GitTerm repo README for provider setup guides and routing details