Deploy Gitterm

GitTerm lets you run OpenCode in remote, persistent workspaces you can reopen from anywhere. It ships with a web app, API, proxy, worker, Postgres, and Redis, and works across multiple infrastructure backends with more provider support on the way. Deploy it on Railway, add your admin login, then configure workspace providers from the app. Use path routing for a standard single domain, or subdomain routing if you have wildcard domain support on the proxy.

What You Need

Required:

• ADMIN_EMAIL
• ADMIN_PASSWORD

Optional later:

• GitHub OAuth credentials for sign-in
• GitHub App credentials for repository access
• Provider credentials for Railway, AWS, E2B, Cloudflare, and future providers

Provider configuration is done inside the GitTerm admin UI, not in the template form.

Routing

Path Routing

Best when you only have a single normal domain on the proxy.

• https://your-domain.com/ -> app
• https://your-domain.com/api/ -> API
• https://your-domain.com/listener/ -> listener
• https://your-domain.com/ws// -> workspaces

Subdomain Routing

Use this only if your proxy domain has wildcard DNS and wildcard TLS support.

• https://-.your-domain.com

If you are unsure, use path routing.

Startup Behavior

On startup, the server automatically:

1. runs database migrations
2. seeds built-in app data
3. creates or upgrades the admin user when ADMIN_EMAIL and ADMIN_PASSWORD are set

Services Included

• web
• server
• listener
• worker
• proxy
• PostgreSQL
• Redis