Deploy ERPNext

Deploy and Host ERPNext on Railway

ERPNext is a comprehensive open-source ERP platform built on the Frappe Framework. It provides integrated modules for accounting, CRM, sales, purchasing, inventory, manufacturing, HR, payroll, projects, assets, support, and other core business operations from a single self-hosted application.

About Hosting ERPNext

Hosting ERPNext requires more than running a single web application because the platform depends on several supporting services for database storage, caching, background jobs, realtime communication, and scheduled tasks.

This Railway template runs ERPNext using the official frappe/erpnext image and consolidates its main application processes into a single ERPNext service. MariaDB stores the primary application data, Redis Cache handles transient cache data, and Redis Queue supports background jobs and realtime operations. Persistent Railway storage is mounted to the ERPNext sites directory so site configuration and uploaded files survive redeployments.

Common Use Cases

• Run accounting, invoicing, purchasing, and financial operations
• Manage CRM, sales pipelines, customers, and quotations
• Track inventory, warehouses, stock movements, and procurement
• Manage manufacturing, bills of materials, and production workflows
• Handle HR, employees, attendance, leave, payroll, and recruitment
• Manage projects, tasks, timesheets, and internal operations
• Build a self-hosted ERP platform for small and medium-sized businesses

Dependencies for ERPNext Hosting

• ERPNext application service using the official frappe/erpnext image
• MariaDB for ERPNext application and business data
• Redis Cache for application caching
• Redis Queue for background jobs and realtime communication
• Railway persistent volume mounted at /home/frappe/frappe-bench/sites
• Railway private networking between ERPNext, MariaDB, and Redis services
• Railway public networking for the ERPNext web interface

Implementation Details

This template uses a Railway-friendly consolidated deployment model.

The ERPNext service runs the primary Frappe processes inside a single container:

ERPNext
├── Nginx frontend
├── Gunicorn backend
├── Socket.IO
├── Queue Short
├── Queue Long
└── Scheduler

This allows all Frappe processes to access the same persistent sites directory:

/home/frappe/frappe-bench/sites

The supporting architecture is:

Internet
   │
   ▼
Railway Public HTTPS
   │
   ▼
ERPNext
   │
   ├── Persistent Volume
   │   └── /home/frappe/frappe-bench/sites
   │
   └── Railway Private Network
       ├── MariaDB
       ├── Redis Cache
       └── Redis Queue

MariaDB should remain private and use persistent storage at:

/var/lib/mysql

Redis Cache does not require persistent storage, while Redis Queue can use:

/data

for persistence.

Only the ERPNext service should be publicly exposed. MariaDB and both Redis services should remain accessible only through Railway's private network.

ERPNext vs Alternatives

ERPNext is particularly suitable for organizations that want a comprehensive ERP platform with accounting, CRM, inventory, manufacturing, HR, and project management integrated into a single self-hosted system.

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