What ERPNext needs from a machine
ERPNext needs room for a database first and everything else second. It runs on the Frappe framework, and a production install is a small family of services: MariaDB for the data, two Redis instances (cache and job queue), the Python backend, short and long queue workers, a scheduler, a websocket service for live updates and an nginx front end. On one server they all share the same processor, memory and disk.
Frappe does not publish one minimum for the whole stack. It does publish guidance for the database, and since the database is what grows with your company, that is the number to plan around:
| What Frappe's database guide says | What it means on one server |
|---|---|
| Start with at least 2 vCPU; add more once use stays above 50% for long stretches | Treat 2 cores as the floor for MariaDB alone, then add room for the workers |
| Start with at least 8 GB of memory, buffer pool around 60% of it | 8 GB for the database, plus headroom for Redis and the Python processes |
| Start with at least 50 GB of disk, plan for about three times the database size | Attachments live on the same disk, so count them too |
| Begin around 2,000 to 3,000 IOPS and adjust from monitoring | Fast local SSD or NVMe keeps reports and month-end closes quick |
| Scale up on one machine for as long as you can, to 64 vCPU and 128 GB | A bigger single server comes before a second one |
Frappe's docs give no figure per user. How hard a site works depends on transactions, reports and custom apps, so watch memory and disk wait in the first month and grow the machine from what you see.
Why a whole server suits an ERP
An ERP is the one system your accounts, stock and payroll all wait on, so it should not slow down because of somebody else's workload. On a dedicated server every core, all the memory and all the disks are yours, with no other customer on the hardware.
- Root access, so you install Docker and Frappe's script exactly as the docs describe.
- An unmetered port. Copying nightly backups and attachments to another location never adds a bandwidth line to the invoice.
- A console of your own on rack servers, blades and the m510 and m710x cartridges: the screen and the power button, even when a firewall rule locks you out of SSH.
- Reinstalls from the control panel, as many as you like, if the first attempt goes wrong.
- Month to month. No contract, and memory or disks can be added to the machine you already run.
The server that fits your books
Pick by the database, not the headcount. The catalogue on the dedicated server page is grouped into classes:
- Everyday servers: one processor and plenty of headroom. This is where a single company's ERPNext usually belongs.
- Compact cartridges with 16 GB or more: enough for a small team that will not outgrow the 8 GB database floor soon. The cartridges with NVMe disks are listed on the NVMe server page.
- Two-processor servers: for several companies on one bench, heavy reporting or custom apps, with room to give MariaDB a large buffer pool. Blade and rack machines add hardware RAID, described on the enterprise server page.
Frappe's install guide asks for Debian 13 or newer, or Ubuntu 24.04 or newer, to avoid package trouble. Both are among the one-click images on the widest lines, and the order page shows what each line offers. A racked server is handed over within 30 minutes of the payment being approved.
Docker or bench: the two ways in
For production, the bench project itself recommends the Docker route. Its easy-install.py script installs Docker, fetches the frappe_docker containers, creates your site with ERPNext on it, and puts Traefik in front to fetch Let's Encrypt certificates for HTTPS.
The manual route installs bench straight onto the operating system. For Frappe v16 that means MariaDB 11.8, Python 3.14, Node.js 24 and Redis or Valkey, plus cron for scheduled jobs. It suits developers who build their own apps; for a company's live books, the containers are easier to upgrade and to rebuild.
The pwd.yml file in frappe_docker is a disposable demo for a quick look. Frappe says it is not meant for production and cannot carry custom apps, so do not keep real data in it.
Up and running in an evening
- Create a DNS record for the name staff will use (for example
erp.yourcompany.com) pointing at the server's IPv4 address, and its IPv6 address too if you publish one. The certificate is issued for that name, so set this up first. - Log in over SSH and set up the firewall. Allow SSH before you switch it on, or you will lock yourself out. ufw writes each rule for IPv4 and IPv6 alike; check that
sudo ufw statuslists the (v6) lines. - Download Frappe's script and run it with your own email and site name. It installs Docker, starts the containers and creates the site with ERPNext installed.
- Read the passwords file the script names at the end of its run (
~/frappe-passwords.txtwith the default project name): it holds the generated MariaDB root password and the Administrator password. Move both into your password manager; once they are saved there, delete that file. The same values also sit in~/frappe.env, which the upgrade command reads, so keep that file and never share it. - Open the site over HTTPS, sign in as Administrator and finish the setup wizard: company, currency, fiscal year, chart of accounts. Then create a named user for each person instead of sharing Administrator.
sudo ufw allow 22
sudo ufw allow 80
sudo ufw allow 443
sudo ufw enable
sudo ufw status
wget https://raw.githubusercontent.com/frappe/bench/develop/easy-install.py
python3 easy-install.py deploy --email=user@domain.tld --sitename=subdomain.domain.tld --app=erpnext
Docker routes the ports it publishes before ufw's rules are applied, so ufw does not guard ports 80 and 443 here. It still closes everything else; just never publish a database or Redis port yourself.
Backups and upgrades you can undo
The script schedules a backup every six hours by default (change it with --backup-schedule). Each run writes a database dump to the site's private/backups folder inside the sites volume. That is the same disk as the live data, so copy the newest set to another machine every day.
- Add
--with-filesto a manual backup to include uploaded attachments, public and private. - If you turn on Encrypt Backup in System Settings, the key comes from the site's config. Fetch it from the Download Backups page with Get Encryption Key and keep it off the server, or an encrypted backup is useless after a rebuild.
- Restore with
bench restoreand the dump's path, adding--with-public-filesand--with-private-filesfor the attachments. Frappe does not support restoring onto an older version, so keep each backup next to a note of the version that made it.
Upgrade only right after a fresh backup has worked. The script pins the release in ~/frappe.env on the ERPNEXT_VERSION line, so first change that line to the release you want and note the old value, since that is the version a rollback returns to. The script's upgrade command then recreates the containers from that file and runs bench --site all migrate for you. The line below takes a full backup first, and the && means the upgrade starts only if the backup succeeded. Run it from the folder that holds easy-install.py, with the default project name frappe:
docker compose -p frappe -f ~/frappe-compose.yml exec backend bench --site all backup --with-files && python3 easy-install.py upgrade --project=frappe
Keep the door closed
- Turn off self sign-up. In Website Settings, tick Disable Signup and save, so nobody can create an account from the login page.
- Retire Administrator for daily work. Give each person their own user and role; keep the Administrator password in the password manager only.
- Mail goes out from your own server. ERPNext sends invoices and alerts through the email account you configure, and outbound mail is allowed here, port 25 included.
- Watch the box. Disk space is the usual surprise, since backups and attachments both grow.
When this is the wrong place
We keep the hardware and the network running; ERPNext, Docker and the operating system are yours to look after. If nobody on the team will apply upgrades and check backups, a self-hosted ERP is a risk.
If you only want to click around the demo for a weekend, a Cloud VPS is sold for jobs too small to need a whole server. And if you are moving an existing ERPNext from another host, read the server migration guide first: it covers running both servers side by side while you test the restore.
Questions people ask
- How much memory should an ERPNext server have?
- Frappe's database guidance starts at 8 GB of memory, with about 60% of it given to the MariaDB buffer pool. On one server, Redis, the workers and the web processes need room on top of that. Start with headroom and size up from what monitoring shows.
- Is self-hosted ERPNext free to use?
- ERPNext is released under the GNU GPL v3, so there is no licence fee to run it on your own server. You pay for the machine and for your own time looking after it.
- Should I install with Docker or with bench?
- For a production site, the bench project recommends the Docker setup, and its easy-install script builds it for you. A manual bench install suits developers working on their own apps. Both run the same ERPNext.
- Can I run several companies or sites on one server?
- Yes. frappe_docker's single-server example runs several sites on one bench, and more than one bench on the same machine. Plan the memory and disk for all of them together.
- What happens if an upgrade breaks something?
- You restore the backup taken just before it, on the version that made it, because Frappe does not support restoring onto an older version. That is why the upgrade line above refuses to start unless the backup succeeds. Keep that backup until you have checked the upgraded site.