Deploy and Host OpenCut Video Editor on Railway

OpenCut Video Editor is an open-source, web-based video editor designed for creating and editing videos directly in the browser. It provides a self-hostable alternative for browser-based video editing, allowing users to work with media and create video projects through a modern web interface.

About Hosting OpenCut Video Editor

Hosting OpenCut Video Editor on Railway uses three services: the OpenCut application, PostgreSQL, and Redis. The application runs from the reesmorris/opencut:latest Docker image, while PostgreSQL provides persistent relational data and Redis handles application caching and runtime data. Railway connects these services through its private network, so the database and Redis services do not need to be publicly exposed. The OpenCut service can be given a Railway-generated domain for public access, with Railway handling HTTPS and external networking. Using Railway service references for PostgreSQL and Redis keeps credentials and internal connection details within the project and makes the deployment easier to manage.

Common Use Cases

Browser-Based Video Editing: Provide users with a self-hosted web application for creating and editing video projects.
Private Video Workflows: Run OpenCut on your own Railway infrastructure when projects and application data should remain within your deployment environment.
Collaborative Content Creation: Provide a centralized video-editing application for teams creating social media, marketing, educational, or other video content.

Dependencies for OpenCut Video Editor Hosting

OpenCut — reesmorris/opencut:latest, the main video-editing application.
PostgreSQL — Required application database.
Redis — Required runtime/cache service using hiett/serverless-redis-http:latest.

Implementation Details

The Railway deployment consists of three services:

Service	Image	Purpose
OpenCut	`reesmorris/opencut:latest`	Video editing web application
PostgreSQL	Railway PostgreSQL	Persistent application database
Redis	`hiett/serverless-redis-http:latest`	Redis HTTP interface and application caching

Keep PostgreSQL and Redis private. The OpenCut service should be the publicly accessible application service.

Docker

Use the published OpenCut image:

reesmorris/opencut:latest

Redis uses:

hiett/serverless-redis-http:latest

Railway deploys both services from their Docker images, so no custom Dockerfile is required for these services.

Database

Add a Railway PostgreSQL service and connect OpenCut using Railway reference variables.

The PostgreSQL service should not be exposed publicly. OpenCut should connect to it through the Railway private network.

Redis

Add the Redis service using:

hiett/serverless-redis-http:latest

Keep Redis private and connect OpenCut to it using the service's private networking variables.

Networking

Generate a Railway domain for the OpenCut service through:

OpenCut → Settings → Networking → Generate Domain

Railway provides HTTPS for the generated domain.

The exact application port is not documented in the supplied deployment information. Therefore, the Railway target port should be taken from the EXPOSE instruction or runtime configuration of the deployed reesmorris/opencut:latest image rather than assuming a port.

Persistent Storage

PostgreSQL provides the persistent database layer for OpenCut.

No separate Railway Volume should be added unless the OpenCut deployment explicitly requires persistent filesystem storage for uploaded media or project files. The supplied template information does not document a required volume mount path, so none is specified here.

Environment Variables

The exact OpenCut PostgreSQL and Redis environment-variable names are not provided in the supplied template information. Configure them according to the OpenCut documentation rather than inventing variable names.

Use Railway private service references for database and Redis connections wherever the OpenCut configuration supports them.

Why Deploy OpenCut Video Editor 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 Video Editor 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.