Full ERPNext suite
Run modules for accounting, inventory, CRM, sales, purchasing, projects, HR, support, and operations in one workspace.
Self-Hosted ERPNext
Your own open-source ERP suite, running on infrastructure you control.
ERPNext is an open-source business suite built on the Frappe Framework for accounting, inventory, CRM, sales, purchasing, projects, HR, and operations. On Kumo2 you can deploy ERPNext with Frappe Docker Compose in one click. We start ERPNext with MariaDB, Redis, background workers, scheduler, websocket service, and the web frontend, then expose the site on the server IP.
7-day money-back guarantee
Features
Frappe Docker Compose
Kumo follows the Frappe Docker compose approach and starts the ERPNext image, MariaDB, Redis, frontend, workers, scheduler, and websocket service.
Private business data
MariaDB and Redis stay inside the Docker network, with persistent volumes on your VM for ERP records, files, queues, and runtime state.
IP access first
The site starts at http://SERVER_IP:8080. Sign in as Administrator with the password you choose during checkout, then add a domain when ready.
What you can do with it
- Give a small business one place for accounting, invoices, inventory, purchasing, CRM, and operational records.
- Run ERPNext for an internal operations team without putting customer and financial data into a shared SaaS workspace.
- Evaluate ERPNext with a realistic Docker stack before deciding how to customize workflows and roles.
System requirements
CPU
2 vCPU
Memory
2 GB
Storage
40 GB
Runtime
Docker Compose
Versions
v16.26.2
Port
8080
Recommended sizes
Starter ERP
2 vCPU / 2 GB RAM / 40 GB SSD
Evaluation, demos, and very small teams using the full Frappe and ERPNext stack on one server.
ERPNext Recommended
Default2 vCPU / 4 GB RAM / 60 GB SSD
A balanced default for small teams running ERPNext, MariaDB, Redis, workers, scheduler, and web frontend together.
Operations Workspace
4 vCPU / 8 GB RAM / 120 GB SSD
More headroom for accounting, inventory, CRM, HR, background jobs, and multiple active users.
Busy ERP
6 vCPU / 16 GB RAM / 240 GB SSD
For larger datasets, heavier reports, imports, and teams that need more database and worker capacity.
Resources & documentation
How deployment works
- 1
Pick a plan and a region close to you.
- 2
Choose how you'll sign in and confirm your order.
- 3
Kumo provisions a Linux server and starts the app with Docker — ready in minutes.
Frequently asked questions
What is self-hosted ERPNext?
It is ERPNext running on a cloud server that belongs to your Kumo2 account. You control the VM, Docker Compose stack, MariaDB database, Redis services, files, and network exposure.
How do I access it after deployment?
Open http://SERVER_IP:8080 in your browser. Use Administrator as the username and the administrator password you entered during checkout.
What services are installed?
Kumo deploys ERPNext with the Frappe Docker image, MariaDB 11.8, Redis 6.2, backend, frontend, queue workers, scheduler, websocket service, and a default site named frontend.
Can I use my own domain and HTTPS?
Yes. Point DNS to the server, place the frontend behind your reverse proxy and TLS setup, then update the Frappe site and proxy configuration to use your domain.
What size should I choose?
Use Starter ERP only for trials and very small teams. ERPNext Recommended (2 vCPU / 4 GB RAM) is the normal default for real business use on a single VM.
Ready to deploy your own ERPNext?
Spin it up on a server you control. We handle provisioning and Docker — you keep the keys.
Deploy ERPNext7-day money-back guarantee
Not happy within 7 days of deploying? Get a full refund — just ask.