--- title: "Deploy Paradev Host" description: "Run Paradev (Superset) coding agents on a remote Railway host" category: "AI/ML" url: https://railway.com/deploy/paradev-host --- # Deploy Paradev Host Run Paradev (Superset) coding agents on a remote Railway host **[Deploy Paradev Host on Railway](https://railway.com/template/paradev-host)** Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/paradev-host/manifest.json - **Creator:** Medim's Projects - **Category:** AI/ML ## Template content ### Paradev Host https://paradev.com/media/superset-app-icon.png - **Source:** https://github.com/kadumedim/paradev-railway-host ## Documentation # Deploy Paradev (Superset) Host Run your Paradev (formerly Superset) coding agents on Railway instead of your laptop. Self-hosted remote host for Claude Code, Codex, Amp, Gemini CLI, OpenCode and any other CLI agent. ## Deploy and Host Paradev (Superset) Host on Railway > **Required first step:** after the first deploy, authenticate GitHub (`gh auth login`) or set `GH_TOKEN`, otherwise the host can't clone your repos. Details in *How to use it*. Paradev (formerly Superset) is a workspace for running many coding agents in parallel, each in its own git worktree. By default the agents run on your own machine. This template gives you a **remote host** on Railway, so you can dispatch agent tasks to it from the Paradev desktop app, the CLI, or your phone. Close your laptop and the agents keep working. ## About Hosting Paradev Host Paradev has two halves: the app you use (desktop, CLI, mobile) and the **host** that actually holds the repos, terminals and running agents. The host is a headless daemon started with `superset start`. Normally it runs on the same computer as the app. Remote hosts let it run somewhere else and connect back through the **Paradev Relay**. This template deploys that host as a long-running Railway service: - **Host daemon:** `superset start`, registered with the Paradev Relay under your account and organization. - **Persistent volume:** keeps cloned repos, worktrees, the host database and agent credentials across redeploys. - **Toolchain:** `git`, `gh` and the common agent CLIs (Claude Code, Codex and others) on `PATH`. - **No public domain needed:** the host connects out to the relay, so there is no inbound port to expose or secure. ## Why Deploy Paradev Host on Railway Running agents locally has three problems: the laptop sleeps, parallel agents eat your CPU and RAM, and long tasks tie up your machine. A host on Railway fixes all three without you managing a server. | | Local machine | Self-managed VPS | Railway template | |---|---|---|---| | Runs while you're offline | No | Yes | Yes | | Setup time | None | Hour or more (systemd, users, updates) | Minutes | | Persistent storage | Your disk | You configure it | Volume included | | Public ports / firewall | None | You secure them | None needed | | Billing | Your hardware | Fixed monthly | Usage-based | | Scale resources | Buy a new laptop | Resize the VPS | Change service resources | ## Common Use Cases for Paradev Host - **Overnight tasks:** start a batch of agents on a backlog and review the diffs in the morning. - **Parallel fleets:** run 10+ agents at once without slowing down your laptop. - **Scheduled automations:** triage issues, draft changelogs or update dependencies on a schedule. - **Phone-first work:** kick off and check agents from the Paradev mobile app while away from your desk. - **Shared team host:** give teammates access to one host with the repos and credentials you choose. - **Orchestration:** let one agent dispatch workers to the host using the `superset:orchestrate` skill. ## Dependencies for Paradev Host The host needs a Paradev account, GitHub access and an agent login. Everything else ships in the template. **Deployment dependencies** - A [Paradev](https://paradev.com) account. The host runs under your account and organization. - A GitHub account with access to the repos you want agents to work on. - At least one agent subscription or API key (Anthropic, OpenAI or another provider). Agents bill to your own subscriptions, not Paradev's. - The Paradev desktop app, CLI or mobile app to connect from. **Implementation details** | Variable | Required | Purpose | |---|---|---| | `SUPERSET_API_KEY` | Yes | API key from **Settings → API Keys** in Paradev. Lets the headless host register without a browser login. | | `GH_TOKEN` | Optional | GitHub token used by `gh` to clone and open PRs. Leave empty and run `gh auth login` in the terminal instead. | | `ANTHROPIC_API_KEY` | Optional | Passed to Claude Code. Leave empty and log in through the terminal instead. | | `OPENAI_API_KEY` | Optional | Passed to Codex. Leave empty and log in through the terminal instead. | ## How the host works Your app doesn't connect to Railway directly. The host registers with the Paradev Relay, and the app reaches it through the relay. Terminals, agent runs, the diff viewer and forwarded dev-server ports (TCP only) all travel that way. The host binds to `127.0.0.1` inside the container, which is why no domain is needed. Only the user who owns the key can see the host at first. Add teammates under **Settings → Hosts → Add member**. ## How to use it 1. **Create an API key** in Paradev under **Settings → API Keys**. 2. **Deploy this template** and paste the key into `SUPERSET_API_KEY`. 3. **Authenticate GitHub.** Either set `GH_TOKEN`, or open a terminal on the service and run `gh auth login`. 4. **Check the host.** In the Paradev app, open the **Workspaces** list and use the **Device** filter (top right). Your Railway host appears under **Other devices**. 5. **Register a project.** On the host, run `superset projects create --name "My Project" --local --clone https://github.com/org/repo.git --parent-dir ~/code`. For a project that already exists, use `superset projects setup --local --parent-dir ~/code`. 6. **Create a workspace on the host** and launch an agent in it. It runs on Railway. 7. **Sign in to your agent.** Set `ANTHROPIC_API_KEY` or `OPENAI_API_KEY`, or log in once through a terminal on the host. The volume keeps the session. ## Useful commands Run these from a Railway shell on the host: ```bash superset status # is the host running and registered? superset hosts list # hosts in your organization superset workspaces list # workspaces on this host superset update # update the CLI manually ``` ## Security notes The relay exposes everything the host can reach: repos, tokens and agent credentials. Use a dedicated Railway project, a fine-grained `GH_TOKEN` limited to the repos you need, and only add teammates you trust. Forwarded ports send cookies and auth headers to the dev server, so treat them as the remote service itself. ## License and pricing Paradev's source is available under the Elastic License 2.0. You can use and self-host it, but not resell it as a service. The app has a free tier and paid plans, so check [paradev.com](https://paradev.com) for current limits on remote hosts. Railway bills by usage. An idle host costs little. Cost rises when agents build, test or run dev servers, so it scales with how many agents you run in parallel. Model usage is billed separately by your agent provider. ## Troubleshooting **The host doesn't appear in the Device list.** Confirm `SUPERSET_API_KEY` is valid and belongs to the same organization you're signed in to in the app. Regenerate the key in **Settings → API Keys** if unsure. **Clone fails on a private repo.** `gh` isn't authenticated. Set `GH_TOKEN` or run `gh auth login` in the service terminal. **Agent says it isn't logged in.** Set `ANTHROPIC_API_KEY` or `OPENAI_API_KEY`, or log in once in a service terminal. The login persists on the volume. **Repos and workspaces vanish after a redeploy.** Check that the service's volume is still attached. **Forwarded port doesn't work.** Port forwarding needs a recent host service (1.26 or newer) and only forwards ports started by that workspace. **Running agents stop after a restart.** Restarting the service interrupts terminals. Redeploy when no agents are mid-task. ## FAQ **Do I need to expose a public domain?** No. The host connects out to the Paradev Relay. **Which agents work?** Any CLI agent on the host's `PATH`, including Claude Code, Codex, Amp, Gemini CLI, Cursor Agent and OpenCode. **Can I use this from my phone?** Yes. Sign in to the Paradev mobile app with the same organization and pick the host. The host runs on Railway, so your computer doesn't need to stay awake. **Is this the same as Apache Superset?** No. This is the coding-agent workspace from superset.sh, now Paradev. It is unrelated to Apache Superset, the BI dashboard tool. **Can teammates share the host?** Yes, from **Settings → Hosts → Add member**. **Does Paradev see my code or model traffic?** Repos live on your Railway volume and agents use your own provider keys. Check Paradev's docs for what the relay carries. ## Related templates - [Paseo Daemon](https://railway.com/deploy/paseo-daemon): self-hosted daemon for Claude Code, Codex and OpenCode with a web UI. - [n8n with FFmpeg](https://railway.com/deploy/n8n-w-ffmpeg): n8n with FFmpeg built in for media workflows. - [n8n with Workers and Task Runner](https://railway.com/deploy/n8n-w-workers-task-runner): n8n in queue mode with workers and an external task runner. *[Updated Nov '26]* ## Similar templates - [Chat Chat](https://railway.com/deploy/-WWW5r) — Chat Chat, your own unified chat and search to AI platform. - [Weaviate](https://railway.com/deploy/weaviate-1) — Vector database with hybrid search and an API key-protected API - [Möbius v0.1 Personal AI OS](https://railway.com/deploy/mobius-v01-personal-ai-os) — Self-hosted AI agent that builds and runs apps for you, with memory. Open this page in a browser: https://railway.com/deploy/paradev-host