Deploy and Host OpenCut on Railway

OpenCut is a free, open-source video editor for web, desktop, and mobile that prioritizes privacy by keeping your videos on your device. It offers timeline-based editing, multi-track support, real-time preview, and no watermarks or subscriptions - providing all the basic features that are now paywalled in CapCut.

About Hosting OpenCut

⚠️ OpenCut does not currently offer an official image. The image used by this template is a fork made by the template author, with minimal changes to make it work in a Docker environment. Once an official image is released, this template will be updated to work with that out of the box.

Deployment Steps

Import the template - there are no configuration values to fill out.
Once the deployment is ready, click on the OpenCut deployment and the pre-generated .railway.app domain to view the instance. It will take you to the “waitlist” page.

Note: The "waitlist" page you see is actually OpenCut's landing page - this is normal behavior and doesn't mean you need to wait for access. You already have full access to your deployment and can navigate directly to the editor using the routes listed in the Post-Deployment Steps.

If you see a Railway error page instead of the waitlist page, it’s likely Railway hasn’t automatically added the port to your domain. Go to Settings → Networking, click the Edit button next to the domain and click “edit port”, then select or enter port 8080.

If you wish to use a custom domain, you simply need to click on the deployment, go to Settings → Networking and click on the + Custom Domain button. Enter your domain and select or enter port 8080.

Post-Deployment Steps

From your app’s domain, you can then visit:

/projects — create and work on your projects (no account is needed currently)
/signup — create an account*
/login — sign in to an existing account*

*At this stage, accounts seem largely redundant; projects and files are stored in your browser locally, and accounts don't currently add any benefit or additional features. This is the current state of development and may change as OpenCut continues to evolve.

Dependencies for OpenCut Hosting

Deployment Dependencies

Service	Version	Purpose	Source Image
OpenCut	latest*	Main app	GitHub
Postgres	16	Database	GitHub
Redis	7-alpine	Rate limiting	Docker Hub
hiett/serverless-redis-http	latest	RESTful access to the Redis database	Docker Hub

*there is no current official image, so this uses a fork which is maintained by this template’s author

Resource Requirements

Memory: 512MB minimum, 1GB recommended
CPU: Minimal
Storage: Minimal (small database schema, user files are stored locally in the browser)

Troubleshooting

For common issues and community support, visit the Railway Community Forum.

Template Changelog

16 July, 2025

Initial template release

Common Use Cases

Personal Video Editing: Host your own private video editor without relying on third-party services
Team Collaboration: Provide a shared video editing platform for your organization
Educational Institutions: Offer students a free, privacy-focused alternative to commercial video editors
Content Creation Studios: Deploy a customizable video editing solution that can be tailored to specific workflows

Why Deploy OpenCut 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 OpenCut 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. OpenCut's privacy-first approach combined with Railway's seamless deployment makes it an ideal solution for individuals and organizations who want control over their video editing infrastructure without the complexity of traditional hosting.