
Deploy DramaClaw
Self-hosted AIGC video engine: script to finished film in one pipeline
dramaclaw-web
Just deployed
dramaclaw-api
Just deployed
/data
dramaclaw-gateway
Just deployed
Just deployed
/var/lib/postgresql/data
Deploy and Host DramaClaw on Railway
DramaClaw is an open-source AIGC video engine that takes a script to a finished film in one pipeline: story breakdown, characters and scenes, keyframes, video shots, voice and final edit. It is used for short dramas, ads, product videos and otome games. This template runs DramaClaw Community Edition 2.1.3.
About Hosting DramaClaw
DramaClaw CE runs as three containers: an nginx web front end, a Python API that stores projects, settings and generated media under /data, and a bundled OpenAI-compatible model gateway. This template builds all three from pinned official images, keeps /data on a Railway volume and stores the gateway's data in Railway Postgres. CE has no user accounts, so the web service asks for a username and a generated password on every page; the password is in the dramaclaw-web service's Variables tab. The models themselves run outside Railway: after deploy you add an official DramaClaw (RelayClaw) key or your own provider keys in Settings.
Common Use Cases
- Turning a short-drama or novel script into storyboards, keyframes and video shots
- Producing ads and product videos from a written brief
- Running a private, self-hosted AIGC video studio with your own model provider keys
Dependencies for DramaClaw Hosting
- An API key for the models: an official DramaClaw (RelayClaw) key, or your own OpenAI-compatible or other provider keys
- Railway Postgres (included) for the bundled model gateway
Deployment Dependencies
- DramaClaw source and docs: https://github.com/dramaclaw/dramaclaw
- Template source (wrapper Dockerfiles, changelog): https://github.com/aalfath/dramaclaw-railway-template
- Licence: Elastic License 2.0 (source available). Self-hosting is allowed; offering DramaClaw to third parties as a hosted or managed service is not. This template is not affiliated with the DramaClaw project.
Implementation Details
dramaclaw-webis the only public service. Log in withDRAMACLAW_USERNAME(defaultadmin) andDRAMACLAW_PASSWORD(generated)./healthzstays open for Railway's health check.dramaclaw-apianddramaclaw-gatewayare reachable only on the private network. In Settings → Models, choose Official and paste a DramaClaw key, or choose Custom and initialise the bundled gateway, then add your provider keys.- Upstream recommends at least 2 vCPU and 4 GB of RAM. Generated media is stored on the API's volume, so size it for your projects.
- Updates: every service builds from the template repo. When it moves to a new DramaClaw release, Railway offers you the update; read the repo's CHANGELOG.md before applying it.
Why Deploy DramaClaw 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 DramaClaw 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
dramaclaw-web
aalfath/dramaclaw-railway-templatedramaclaw-api
aalfath/dramaclaw-railway-templatedramaclaw-gateway
aalfath/dramaclaw-railway-template
