
Deploy hll-crcon-cloud
Cloud hosting for CRCON, the community RCON tool for Hell Let Loose.
maintenance
Just deployed
frontend
Just deployed
redis
Just deployed
/data
postgres
Just deployed
/var/lib/postgresql/data
backend
Just deployed
supervisor
Just deployed
/scoreboard_db
Just deployed
Deploy and Host hll-crcon-cloud on Railway
hll-crcon-cloud packages CRCON, the community-built admin tool for Hell Let Loose game servers, as a one-click Railway template. You get the full web admin UI: live game view, player management, bans, VIPs, automod, Discord webhooks, and a public scoreboard site, without renting a VPS or touching Docker.
About Hosting hll-crcon-cloud
Upstream CRCON ships as a 7-container Docker Compose stack meant for a self-managed VPS. This template maps that stack onto seven Railway services: Postgres and Redis for state, the Django API backend, a supervisor running roughly 15 background workers (stats, automod, log ingestion), a maintenance service that runs database migrations, a Discord webhook worker, and an nginx frontend serving the admin UI and public scoreboard. Deploying takes three inputs: your game server's IP, RCON port, and RCON password. Everything else, including secrets, database credentials, private networking, TLS, and startup ordering, is wired up automatically. First boot takes around five minutes, then you log in and change the default admin password.
Common Use Cases
- Hell Let Loose server admins who want the standard community admin tool without managing a VPS, Docker, or TLS certificates
- Communities running a public scoreboard and stats site for their players alongside the private admin UI
- Multi-server clans managing up to 10 game servers from one install with shared bans, VIPs, and player profiles
Dependencies for hll-crcon-cloud Hosting
- A Hell Let Loose (or Hell Let Loose: Vietnam) game server from any provider, with its RCON host, port, and password
- Nothing else: databases, networking, and TLS are provisioned by the template
Implementation Details
The stack runs the upstream CRCON images pinned to a tested release, so all upstream documentation applies. Only the backend service asks for input:
The backend waits for the maintenance service to finish database migrations before starting, replacing Compose's depends_on ordering, so a fresh deploy converges on its own with no manual steps. Docs, a multi-server runbook, and troubleshooting live at github.com/sledro/crcon.cloud.
Why Deploy hll-crcon-cloud 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 hll-crcon-cloud 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
maintenance
cericmathey/hll_rcon_tool:v12.2.1frontend
sledro/crcon.cloudredis
redis:alpinepostgres
postgres:12-alpinebackend
sledro/crcon.cloudHLL_HOST
IP address of your Hell Let Loose game server (no port)
HLL_PORT
RCON port of your game server (not the game or query port)
HLL_PASSWORD
RCON password of your game server
supervisor
sledro/crcon.cloud
