Self-Hosting Setup

Your Data, Your Infrastructure

Full ERPNext deployment on your own servers or cloud VMs. Complete data control, no per-user license constraints, and optimized infrastructure tuned for your load.

Plan Your Setup Back to ERPNext
Full Control Data stays on your servers
Unlimited Users No per-seat fees
Production-Ready Backups, SSL, monitoring

What We Set Up

A complete self-hosted ERPNext environment configured for production use — not a quick install, but a hardened deployment built to last.

Server Provisioning

VPS or cloud VM sizing based on your user count and transaction volume. AWS, GCP, DigitalOcean, or your own datacenter.

Right-Sized Infrastructure
Frappe Bench Setup

Clean Frappe Bench installation with ERPNext, MariaDB, Redis, and Nginx configured for production workloads.

Production Stack
SSL & Security Hardening

Let's Encrypt SSL, firewall rules, fail2ban, SSH key authentication, and automated security updates.

Secure by Default
Automated Backups

Scheduled database and file backups with off-site storage (S3 or equivalent). Backup verification and restore procedures documented.

Data Protection
Monitoring & Alerting

Server health monitoring with CPU, memory, disk, and ERPNext queue alerts. Uptime checks with team notifications.

Operational Visibility
Update Management

Controlled ERPNext version upgrade procedures with staging environment testing before production rollout.

Safe Upgrade Path

Self-Hosted vs Frappe Cloud

We support both deployment paths. Here's how to choose the right one for your team.

Complete Data Sovereignty Data stays on servers you own. Required for industries with strict data residency or regulatory compliance requirements.
Unlimited Users at Flat Cost No per-user seat fees. As you grow from 20 to 200 users, your infrastructure cost stays flat — you pay for compute, not seats.
Deep Customization Support Custom Frappe apps, Python hooks, and non-standard configurations that Frappe Cloud restricts. Full server access for advanced tuning.
Performance Tuning Configure MariaDB buffer pools, Redis memory limits, and Nginx worker processes for your specific transaction volume and query patterns.
Controlled Upgrade Timing Choose when to upgrade ERPNext versions. Test in staging, schedule production updates outside business hours, roll back if needed.
Custom Backup Policies Define your own retention schedules, backup destinations, and restore procedures to match your business continuity requirements.
When Self-Hosting Wins
Grow Without Paying Per Seat

Frappe Cloud handles the ops for you — great for teams that want to move fast without DevOps overhead. But once you cross ~30-50 users or need deep customization, self-hosting consistently costs less and gives you more flexibility. We help you evaluate the crossover point.

Flat infrastructure cost regardless of user count
Install any Frappe app, no marketplace restrictions
Data residency in any geography you choose
Full SSH access for advanced configuration

Frequently Asked Questions

Common questions about self-hosting ERPNext.

What server specs do we need for self-hosted ERPNext?
For a small team (up to 20 concurrent users), a 4-core / 8GB RAM VPS is a solid starting point. Medium deployments (20-80 users) typically need 8 cores and 16-32GB RAM. Large deployments benefit from dedicated database servers. We size infrastructure during discovery based on your expected user count, transaction volume, and customization depth — then give you a right-sized recommendation before spending anything.
Can we migrate from Frappe Cloud to self-hosted later?
Yes. Frappe Cloud uses standard Frappe Bench under the hood, so migration is straightforward: export a site backup, provision your own server, install Bench, and restore the backup. We handle this migration regularly and include documentation of the new environment. Many clients start on Frappe Cloud, then migrate once they exceed 30-40 users or need custom Frappe apps that require server access.
Do you support Docker-based ERPNext deployments?
Yes. We deploy ERPNext using both the traditional Frappe Bench approach and the official Docker Compose setup depending on your team's preferences and existing infrastructure. Docker deployments are easier to manage for teams with DevOps experience. Bare-metal Bench setups give slightly better performance and more direct control. We'll recommend based on your team's capabilities and long-term maintenance plans.
What cloud providers do you support?
We deploy on AWS EC2, Google Cloud Compute, DigitalOcean Droplets, Vultr, Hetzner, and on-premise servers. For Southeast Asia, we often recommend Singapore-region deployments on AWS or GCP for low latency. For data sovereignty requirements in Thailand or Myanmar, we can deploy on local cloud providers or your own datacenter hardware. Any Linux server with sufficient resources works.
Who manages the server after setup?
We provide a complete handover with infrastructure documentation, runbooks for common operations, and trained access for your IT team. For teams without in-house DevOps, our ERPNext support retainer includes server management — OS updates, ERPNext version upgrades, backup monitoring, and incident response. You can manage it yourself or let us handle it; both paths are documented and supported.
Ready to Own Your ERPNext Stack?

Tell us about your team size, compliance requirements, and current infrastructure. We'll design the right server setup for you.

Start a Conversation Back to ERPNext