Odoo or ERPNext on Railway: which open-source ERP to run
Short answer: both are open-source ERPs you can run on Railway from a template. Odoo 20 Community is the smaller deployment, two services, and its README lists CRM, sales, inventory, invoicing, website, e-commerce, project and helpdesk apps. ERPNext v16 runs four services and lists accounting, inventory, selling, buying, manufacturing, projects and CRM. Pick the one whose modules match your first process, then deploy it on Hobby or above. Try it with test data before you move real accounts.
Deploy Odoo on Railway Deploy ERPNext on RailwayHow the two templates compare
This table uses only what Tracklayer’s own template files state.
| Odoo 20 Community | ERPNext v16 | |
|---|---|---|
| Image | odoo:20.0-20260926 plus nginx |
frappe/erpnext:v16.50.0 plus supervisord |
| Services | Odoo (with nginx) and Postgres 18 | ERPNext, MariaDB 11.8, two Redis |
| Licence (NOTICE) | LGPL-3.0 | GPL-3.0 (Frappe framework: MIT) |
| Replicas | One, scales vertically | One, scales vertically |
| Idle RAM, measured locally | Odoo 220 to 300 MB, Postgres about 110 MB | ERPNext 400 MB, MariaDB 300 MB |
| Idle cost, estimated | about 5 USD per month | about 11 USD per month |
| Typical cost, estimated | about 24 USD per month (10 to 30 users) | about 34 USD per month (5 to 30 users) |
| Minimum plan | Hobby recommended | Hobby |
The idle RAM figures were measured on a local machine, not on Railway. The monthly costs are estimates at Railway prices of 10 USD per GB of RAM, 20 USD per vCPU and 0.15 USD per GB of volume per month. Check current prices.
Which one fits a small business
- Start from the process you need first. Odoo’s README lists website and e-commerce apps on the same database as CRM and invoicing. ERPNext’s README lists manufacturing, buying and accounting. Neither list is a full feature comparison, so open each app’s documentation for your must-haves.
- Add apps over time. In Odoo you install apps from the Apps menu as you grow. Only the
basemodule is installed on first boot. - HR and payroll. ERPNext’s template does not include Frappe HR.
- Newness. The template notes that Odoo 20 had been public for about two weeks when it was written, so community and third-party modules may not be ported yet. If you rely on them, the notes suggest starting on 19.0 by changing the
FROMtag before the first deploy.
Deploy Odoo, step by step
Uses Tracklayer’s Odoo 20 template.
- Deploy the template. Secrets, including the administrator and master passwords, are generated.
- Wait about a minute for the database to be created.
- Sign in with
ODOO_ADMIN_LOGINandODOO_ADMIN_PASSWORD, then change the password. - Install apps from the Apps menu and set your company, country and fiscal localisation in Settings.
- Set up outgoing mail under Settings, Technical, Outgoing Mail Servers, or with the
SMTP_*variables.
The public database manager is disabled and the database name is pinned. Filestore and sessions live on a volume at /var/lib/odoo, and Postgres has its own volume.
Deploy ERPNext, step by step
Uses Tracklayer’s ERPNext v16 template.
- Deploy the template. On first boot it creates the site, installs ERPNext and enables the scheduler.
- Wait for the first deploy. Site creation takes a few minutes, and the template sets a long health check timeout.
- Sign in as
AdministratorwithADMIN_PASSWORD. - Complete the setup wizard, change the password and create your users.
- Add an Email Account under Settings to send and receive mail.
The sites folder, MariaDB and the queue Redis use volumes. The cache Redis has no persistence by design.
Limitations
- Odoo: the template notes the attachment round trip was not verified locally, though filestore persistence across restarts was. Moving to a new major version needs a database migration first.
- ERPNext: the first build pulls a large image (about 2 GB compressed), and the template notes the build time on Railway was not measured. Realtime behaviour was verified locally and still needs a two-tab check on Railway.
- Scaling: neither runs several replicas. Raise workers and memory instead.
Upgrades
Odoo: pin a newer 20.0 build in services/odoo/Dockerfile and redeploy. ERPNext: change ERPNEXT_VERSION within the v16 line and redeploy, and the migration runs once on its own. Back up first in both cases.
Other options
If you only need a CRM, see the guide to self-hosting Twenty CRM. For project tracking, see the guide to self-hosting Plane.
FAQ
How do I log in to Odoo and ERPNext after deploying?
For Odoo, sign in at the public URL with ODOO_ADMIN_LOGIN and the generated ODOO_ADMIN_PASSWORD from the Odoo service variables. For ERPNext, wait a few minutes for site creation, then sign in as Administrator with the generated ADMIN_PASSWORD from the ERPNext service variables. Change the password after the first login in both.
What licences do Odoo Community and ERPNext use?
The NOTICE files list Odoo Community as LGPL-3.0 and ERPNext as GPL-3.0, with the Frappe framework under MIT. Odoo Enterprise features are not included. Read the licence before you modify or redistribute either, and ask a lawyer if you are unsure. Both templates are community templates.
Do ERPNext and Odoo include payroll and HR?
The ERPNext template does not. Frappe HR (payroll, leave, attendance) is a separate app that needs a custom image, which the template does not provide. The Odoo template's README does not list an HR app, so check Odoo's Apps menu for what you need.
Can I run more than one replica?
No for ERPNext: its service owns the sites volume and runs as one replica. Odoo's service owns the filestore volume, so it scales vertically as well, by raising ODOO_WORKERS and memory.
How do I back up Odoo and ERPNext?
Odoo: temporarily set ODOO_LIST_DB to True, use the database manager with the generated master password, then switch it back. Railway volume backups of Postgres and the data directory also work. ERPNext: Railway volume backups cover the sites and MariaDB volumes, and you can run bench backup --with-files from a Railway shell.