Deploy CloudDev AI
Deploy and Host CloudDev AI on Railway
clouddev-router
Just deployed
/app/data
clouddev-postgres
Just deployed
/var/lib/postgresql/data
clouddev-git
Just deployed
/var/lib/gitea
clouddev-ide
Just deployed
/workspace
Deploy and Host CloudDev AI on Railway
CloudDev AI deploys a private, single-user development workspace. It runs code-server, key-only OpenSSH, CloudCLI, Codex CLI, Claude Code, Forgejo, and OmniRoute as a Railway project. Persistent volumes hold project files, Git repositories, provider configuration, and recoverable agent-session history. The template needs no input. Owners connect their own provider accounts after deployment and can add an SSH public key later for desktop VS Code.
About Hosting CloudDev AI
CloudDev AI keeps the editor, terminal agents, and CloudCLI mobile interface in one always-on workspace service. VS Code Desktop connects through an explicit Railway TCP proxy. Browser VS Code and CloudCLI use the same project files and supported provider-session history. Separate Forgejo, PostgreSQL, and OmniRoute services provide private Git hosting, metadata storage, and model routing. The workspace uses a persistent volume and one replica. Railway restarts stop active processes, so only sessions supported by an upstream agent can be resumed after a restart. Provider accounts and keys are not included. Each owner connects their account through the authenticated OmniRoute dashboard and gives coding agents only a scoped inference key.
Common Use Cases
- Edit the same projects from native VS Code, a desktop browser, or a phone.
- Run Codex CLI and Claude Code against the owner's authenticated OmniRoute providers.
- Keep private repositories and review changes through a self-hosted Forgejo interface.
- Disconnect a client while a server-side task continues, then reopen a supported session in another interface.
- Continue work after a restart by reviewing the durable task registry and manually resuming sessions supported by the relevant upstream agent.
Dependencies for CloudDev AI Hosting
Deployment Dependencies
- Railway runs the four-service project and persistent volumes.
- code-server provides browser VS Code.
- CloudCLI provides the mobile-first agent and session interface.
- OpenAI Codex CLI and Claude Code run in the shared workspace service.
- OmniRoute routes inference requests to provider accounts configured by the owner.
- Forgejo stores private Git repositories. A separate PostgreSQL service stores Forgejo metadata.
Implementation Details
Railway generates every password and signing secret for each deployment. No
value is shared between installs. After deployment, read
CODE_SERVER_PASSWORD from the clouddev-ide variables and sign in at the
workspace domain. Forgejo and OmniRoute keep their own accounts; their
bootstrap passwords are FORGEJO_ADMIN_PASSWORD and INITIAL_PASSWORD.
Change them after the first sign-in. SSH_AUTHORIZED_KEYS is optional. Add
Ed25519 public keys there to enable desktop VS Code Remote-SSH. Provider
credentials are added after deployment and are never part of the template.
Why Deploy CloudDev AI on Railway?
Railway provisions the workspace, Git service, database, gateway, and their
private networking in one project. The project configuration is kept in
.railway/railway.ts, and the template adds generated domains and
per-deployment secrets. Volume-backed services stay at one replica. Railway
Private Networking does not restrict outbound connections from the workspace.
Review the threat model, data flows, and restore procedure before placing
sensitive projects on the instance.
Template Content
clouddev-router
Schero94/clouddev-ai-sovereign-workspaceclouddev-postgres
ghcr.io/railwayapp-templates/postgres-ssl:18clouddev-git
Schero94/clouddev-ai-sovereign-workspaceclouddev-ide
Schero94/clouddev-ai-sovereign-workspace
