Deploy LoopForge

Deploy and Host LoopForge on Railway

LoopForge is a self-hosted team workspace for delivering software with coding agents. Its browser-based Main Bot coordinates repositories, project roles, workflows, approvals, and execution evidence in one place. This deployment packages the web UI and API in a pinned GHCR image and stores durable application state in MySQL with Railway-managed volumes.

About Hosting LoopForge on Railway

Railway runs the pinned LoopForge container alongside MySQL, provides an HTTPS service domain, and persists application and database data with volumes. The app is configured for Railway's private MySQL network and public web routing on port 8080.

Tech Stack

• LoopForge web UI and API
• Go application runtime
• Node.js-based bundled agent tooling
• MySQL 8.4
• Docker images from GHCR and Docker Hub
• Railway HTTPS networking and persistent volumes

Why Deploy LoopForge on Railway

Railway provides simple container deployment, managed networking, HTTPS domains, persistent storage, private service discovery, and straightforward environment-variable configuration. This makes it easy to run LoopForge without maintaining a host server or manually configuring reverse-proxy TLS.

Common Use Cases

• Team software delivery with coding agents
• Repository-aware project planning and implementation
• Reusable SOP and workflow execution
• Human approval gates and execution evidence
• Centralized agent, repository, and project management

Deployment Notes

• The LoopForge HTTP/API service listens on container port 8080 and exposes PORT=8080 and AGENTFLOW_HTTP_PORT=8080.
• Create the first account in the browser; the first local account becomes the platform administrator. No default username or password is embedded.
• AGENTFLOW_SESSION_SECRET must remain stable across restarts and is generated with a Railway secret function in the template.
• LoopForge state is persisted at /data; MySQL data is persisted at /var/lib/mysql.
• The MySQL service is private and is referenced through Railway's private domain.
• Railway does not provide a host Docker socket by default. The web UI, API, authentication, and database-backed features work, but Docker-backed SOP sandboxes require a connected runner or separately provisioned execution environment.

Dependencies for LoopForge on Railway

LoopForge requires a persistent MySQL service. The application connects to MySQL over Railway's private network using the root password generated for the database service.

Deployment Dependencies