
Deploy OpenChamber
Password-protected web UI for the OpenCode coding agent
OpenChamber
Just deployed
Deploy and Host OpenChamber on Railway
OpenChamber is a web and desktop interface for the OpenCode AI coding agent: chat with agents, review diffs, manage sessions, run a terminal and work on git repositories from any browser, including your phone. This template runs it as a private, always-on coding agent in the cloud.
About Hosting OpenChamber
This template builds the official Docker image from the repository and runs it as one service:
- OpenChamber on port 3000 with a public domain, with OpenCode started inside the container
- Password protection on the web UI, with a generated OPENCHAMBER_UI_PASSWORD
- A persistent volume at /data holding OpenChamber settings, OpenCode config, auth and sessions, the SSH key and your workspaces
- OpenCode starts in /home/openchamber/workspaces, which lives on the volume
The first build takes a few minutes.
After deploy:
- Open the service Variables tab and copy OPENCHAMBER_UI_PASSWORD.
- Open https://YOUR-RAILWAY-DOMAIN and sign in with it.
- Connect a model provider in the OpenChamber settings (OpenCode supports Anthropic, OpenAI, OpenRouter, GitHub Copilot, local-compatible APIs and more). Credentials are stored on the volume.
- Clone a repository into /home/openchamber/workspaces from the built-in terminal and open it as a project.
- For private git over SSH, copy the public key printed in the deploy logs (or run
cat ~/.ssh/id_ed25519.pubin the terminal) and add it to your git host. It is generated once and kept on the volume.
Common Use Cases
- An always-on coding agent you can reach from your phone or any browser
- Long-running agent sessions that keep going after you close your laptop
- A shared, password-protected OpenCode workspace for a side project
- Reviewing agent diffs and running commands away from your workstation
Dependencies for OpenChamber Hosting
- Source: https://github.com/openchamber/openchamber (MIT license)
- OpenCode CLI (installed in the image)
- An API key or subscription for at least one model provider
Deployment Dependencies
Implementation Details
- Railway allows one volume per service, while the image expects several data folders in the home directory. The start command keeps .config, .local, .ssh and workspaces on the volume and links them into /home/openchamber, then starts the stock entrypoint as the unprivileged openchamber user.
- Anyone with the UI password can run commands in the container through the agent and the terminal. Use a long password and do not share the domain.
- Changing OPENCHAMBER_UI_PASSWORD and redeploying changes the login password; existing browser sessions stay valid until they expire.
Why Deploy OpenChamber 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 OpenChamber 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
OpenChamber
openchamber/openchamber
