Deploy and Host GreenLight Dash on Railway

The private creative workspace your AI agents can work in. Moodboards, mockups and a full video editor, on your server, with your own cloud and your own keys. It includes a social media parser, agentic workflows, a motion-design video editor, a mockup builder, AI actions such as making shorts, captions, reframes and a transcribe editor, and media generation through WaveSpeed, Pika or any custom model. Every part has a full API for agents and can be synced with your desktop boards.

About Hosting GreenLight Dash

GreenLight Dash Server is one long-running Linux container with a persistent disk: a Python API, SQLite, your media, ffmpeg and headless Chromium for server-side rendering. This template deploys the official image ghcr.io/wpsoul/greenlight-dash:latest with a Volume mounted at /data for boards, media, renders and secrets, a public domain, a health check on /health and restart on failure. The owner password is generated for you as GL_AUTH_PASSWORD; read it in the service's Variables or type your own and redeploy, the server stores it hashed. The instance URL follows the service's public domain. Enlarge the volume before uploading real media. One owner per installation; your data stays on your volume unless you configure an AI provider.

Common Use Cases

A private, always-on moodboard and media library you and your AI agents share, reachable from any browser
Making videos, previews, tutorials and stills on the server from the GreenLight Dash desktop app or from an agent through the API
Screen recording with a full agentic workflow
Collecting references from social media and websites into boards, then turning them into edits with the built-in video editor
Managing large amounts of media
Visual editing of HTML, Markdown and CSV files

Variables

GL_AUTH_PASSWORD — Owner password for signing in (8+ characters). A random one is generated on deploy; keep it and read it back in the service's Variables tab, or type your own. The server stores it hashed. Change it and redeploy to change the password.
GL_INSTANCE_URL — Public HTTPS address of this server, used for login cookies and links. Pre-filled from the Railway domain; replace it with your own domain if you attach one (https://boards.example.com).
RAILWAY_RUN_UID — Must stay 0. Railway mounts the volume owned by root while the image runs as user 1000, so the container runs as root to write /data. Leave the generated value as it is.
GL_PREVIEW_ORIGIN (optional, add it yourself) — A second domain attached to the same service; HTML cards render from it on an isolated origin. Without it the server reports preview isolation as off and everything else works.

Dependencies for GreenLight Dash Hosting

A Railway Volume mounted at /data (the template attaches a 5 GB one; enlarge it before uploading real media)
4 GB RAM for browsing boards and short renders, 8 GB for effect-heavy 1080p renders

Deployment Dependencies

Image: https://github.com/wpsoul/greenlight-dash-web (self-hosting package, Compose file, hosting guides)
Product site and licence: https://greenlightdash.pro

Implementation Details

The image runs Chromium without its user-namespace sandbox (Railway's runtime blocks it) and runs as root on Railway so the root-owned volume is writable (RAILWAY_RUN_UID=0). The server trusts Railway's edge proxy for TLS automatically. Optional: attach a second domain and set GL_PREVIEW_ORIGIN to it so HTML cards render on an isolated origin. Agents connect with bearer tokens minted in Settings ▸ Server ▸ Agent tokens; the same token links the desktop app under Web version ▸ Sync with web.

Why Deploy GreenLight Dash 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 GreenLight Dash 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.