Deploy and Host Embykeeper on Railway

Embykeeper is an automation tool for Emby media-server accounts and related Telegram-based services. It supports scheduled check-ins, Emby account keep-alive tasks, site monitoring, messaging, and other automated workflows. It is distributed as a Python application and Docker image, with configuration stored through its configuration file and persistent application data.

About Hosting Embykeeper

Hosting Embykeeper on Railway requires a single application service running the project's Dockerfile and a persistent Railway Volume mounted at /app. The Docker image includes the Python runtime, application dependencies, and startup entrypoint. For deployments using the web console, Railway should expose port 1818, while EK_WEBPASS enables the web interface. Persistent storage is important because Embykeeper uses files such as config.toml and cache.json under /app. Railway replaces the Docker Compose host-networking and port-mapping configuration with its own networking and public-domain configuration.

Common Use Cases

Automating scheduled Emby account keep-alive and playback tasks
Automating Telegram and supported-site check-ins
Monitoring supported services and sending notifications or messages

Dependencies for Embykeeper Hosting

Embykeeper application — deployed from the project's Dockerfile or Docker image
Persistent storage — a Railway Volume mounted at /app for configuration and application state
External Emby/Telegram services — required when configuring the corresponding Embykeeper features

Deployment Dependencies

Official Embykeeper documentation: https://emby-keeper.github.io/
Original Embykeeper repository: https://github.com/emby-keeper/emby-keeper-dev
Railway deployment repository: https://github.com/bilalnawaz072/emby-keeper

Implementation Details

For a Railway deployment using the web console, configure the service with the following variables:

EK_WEBPASS=YOUR_STRONG_PASSWORD
PORT=1818

Mount a Railway Volume at:

/app

The application Docker entrypoint uses EK_WEBPASS to select web-console mode, while the web application listens on the configured PORT. The /app directory should remain persistent so configuration and authentication/cache data survive container replacements.

Do not carry over Docker Compose's host networking or host port mapping to Railway. Railway handles public networking and port routing at the service level.

Why Deploy Embykeeper 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 Embykeeper 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.