---
title: "Deploy OneDev Shell Runners"
description: "OneDev with trusted Railway shell runners and optional autoscaling."
category: "Automation"
url: https://railway.com/deploy/onedev-shell-runners
---

# Deploy OneDev Shell Runners

OneDev with trusted Railway shell runners and optional autoscaling.

**[Deploy OneDev Shell Runners on Railway](https://railway.com/template/onedev-shell-runners)**

- **Creator:** Tom
- **Category:** Automation

## Template content

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

### Shell Runner https://raw.githubusercontent.com/monotykamary/railway-template-onedev-shell-runners/main/assets/onedev.png

- **Source:** https://github.com/monotykamary/railway-template-onedev-shell-runners

### Runner Autoscaler https://raw.githubusercontent.com/monotykamary/railway-template-onedev-shell-runners/main/assets/onedev.png

- **Source:** https://github.com/monotykamary/railway-template-onedev-shell-runners
- **Health check:** /health

### OneDev https://raw.githubusercontent.com/monotykamary/railway-template-onedev-shell-runners/main/assets/onedev.png

- **Source:** https://github.com/monotykamary/railway-template-onedev-shell-runners
- **Health check:** /
- **Public domain:** Yes

## Documentation

# Deploy and Host OneDev with Railway Shell Runners

This template combines OneDev's integrated Git, pull request, issue, package, and CI orchestration features with trusted shell-based agents running on Railway. It includes PostgreSQL, persistent OneDev storage, a prebuilt runner toolchain, reusable agent-token leasing, and optional demand-driven replica scaling.

## About Hosting OneDev with Shell Runners

OneDev stores relational metadata in PostgreSQL and repositories, attachments, artifacts, and server state under `/opt/onedev`. The bundled agent connects over Railway's private network and executes jobs through OneDev's Remote Shell Executor. A separate autoscaler configures the executor, manages unique agent-token leases, and monitors waiting, pending, and running builds.

The default deployment keeps one runner available without requiring Railway API credentials. Users can add an environment-scoped Railway project token to enable queue-based scaling and cooldown scaling.

## Common Use Cases

- Run CI for trusted internal repositories
- Test Node.js, Python, Ruby, Java, and native projects
- Host Git repositories, issues, packages, and CI in one platform
- Replace fixed self-hosted runners with demand-based Railway capacity
- Use local PostgreSQL and SQLite tooling without service containers

## Dependencies for OneDev with Shell Runners Hosting

- OneDev server and agent 16.5.0
- PostgreSQL 18
- Persistent volumes for OneDev, PostgreSQL, and autoscaler leases
- Node.js autoscaler service
- Optional Railway project token for replica scaling

### Deployment Dependencies

- [OneDev documentation](https://docs.onedev.io/)
- [Remote Shell Executor documentation](https://docs.onedev.io/tutorials/cicd/plain-old-build)
- [OneDev agent management](https://docs.onedev.io/administration-guide/agent-management)
- [Railway project tokens](https://docs.railway.com/integrations/api)
- [Template source repository](https://github.com/monotykamary/railway-template-onedev-shell-runners)

### Security and Execution Model

Jobs run directly in the agent container and do not receive container isolation. Docker builds, job images, service containers, privileged operations, and untrusted pull-request execution are unsupported. Executor concurrency is limited to one job per agent, HTML report publishing and project-site publishing are disabled, and broad administrator or Railway credentials remain isolated to the autoscaler service.

### Why Deploy OneDev with Shell Runners on Railway?

Railway provides managed PostgreSQL, private networking, persistent volumes, HTTPS, health checks, and replica management. For trusted codebases that do not require Docker-based jobs, the template supplies an integrated source platform and practical CI toolchain without operating dedicated runner hosts.


## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — [Jul'26] WhatsApp automation platform using Evolution API, n8n & PostgreSQL
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/onedev-shell-runners