ERPNext Hosting im Jahr 2026: Frappe Cloud vs. selbstgehostet vs. verwaltet – Kosten und Kompromisse

There are exactly three sensible ways to host ERPNext in 2026: Frappe Cloud (the official platform-as-a-service from Frappe Technologies, starting around $25/month and scaling past $500), self-hosting on your own VPS or bare metal ($25–$150/month in server costs plus your engineering time), or managed hosting through a partner who runs the infrastructure for you ($100–$400/month, all-inclusive). The right choice is determined less by budget than by one question: do you have someone in-house who can confidently administer a Linux server, a MariaDB database, and a Frappe bench — and do you want them spending time on that?

This guide breaks down the real costs, the performance characteristics, the failure modes, and the decision criteria for each path, based on running ERPNext workloads across all three models.

Key Takeaways

• Frappe Cloud is the lowest-friction option and directly funds ERPNext development, but per-site pricing scales up and custom apps require paid tiers
• Self-hosting is the cheapest on paper ($25–$60/month for a 50-user instance) but the real cost is 4–10 hours/month of DevOps time — $400–$1,000/month at loaded rates
• Managed hosting buys self-hosting's freedom (custom apps, full access, region choice) without the operational burden — typically $100–$400/month
• A production ERPNext server needs minimum 4 GB RAM and 2 vCPU for 10–25 users; 8–16 GB and 4 vCPU for 50–100 users
• Backups are the non-negotiable: daily automated database + files backups, stored off-server, with restore drills actually performed
• The most expensive hosting decision is the $10 VPS with no backups — one database loss exceeds five years of proper hosting costs
• Version upgrades (v15 to v16) are where self-hosters get stuck most often; budget 4–8 hours per major upgrade or pick a host that does it for you
• For businesses without a Linux-capable engineer, managed hosting has the lowest true total cost of ownership

---

What ERPNext Actually Needs to Run

ERPNext is not a single binary — it is a stack. The Frappe bench environment includes Python (Gunicorn workers for web requests), MariaDB or Postgres (MariaDB is the standard), Redis (three instances: cache, queue, socketio), Node.js (real-time events and asset builds), and a worker pool for background jobs (emails, scheduled tasks, report generation). Nginx fronts the whole thing.

This matters for hosting because each component has its own failure modes. Redis memory exhaustion silently breaks background jobs. MariaDB misconfiguration causes the slow-creep performance decay that users report as "ERPNext is getting slow." Skipped bench updates pile up into upgrade cliffs. Whoever hosts your ERPNext needs to understand all of it — not just keep a VM powered on.

Sizing guide for production instances:

Heavy manufacturing usage (MRP runs, large BOMs), big file attachments, and long transactional history push you up a tier. Undersizing RAM is the most common self-hosting mistake — MariaDB and three Redis instances compete for memory, and swapping turns a 200ms page load into 4 seconds.

Option 1: Frappe Cloud

Frappe Cloud is the official managed platform run by Frappe Technologies, the maintainers of ERPNext. Sites deploy in minutes, backups and updates are handled, and — importantly — your subscription directly funds ERPNext development.

Pricing structure (2026): Frappe Cloud prices per site based on plan tier. Entry plans suitable for evaluation and very small teams start around $25/month. Production-grade plans with more RAM, dedicated workers, and support run $50–$200/month per site. Larger dedicated-server arrangements scale past $500/month. Custom app deployment (your own Frappe apps from private repos) requires the higher tiers.

Strengths:

• Zero DevOps. Updates, backups, SSL, monitoring — all handled by the people who wrote the framework
• Press-button major version upgrades with automatic pre-upgrade backups
• The marketplace installs Frappe ecosystem apps (HR, Insights, CRM) in one click
• Best-in-class understanding of the stack — when something breaks, the platform team can read the traceback

Trade-offs:

• Per-site pricing accumulates if you need separate staging, training, and production sites
• Custom apps and server-level access are restricted to paid tiers; deep server tuning is off the menu
• Data residency options are growing but still narrower than picking any VPS region on earth
• You are on shared infrastructure unless you pay for dedicated servers

Best for: teams with no Linux capability who want the official path, evaluation projects, and standard deployments without exotic customization or compliance constraints.

Option 2: Self-Hosted

Self-hosting means renting a VPS (Hetzner, DigitalOcean, AWS Lightsail, Contabo, Vultr) or using your own hardware, installing the Frappe bench, and operating everything yourself.

The visible cost is the server. A Hetzner CPX31 (4 vCPU, 8 GB) at roughly $16/month comfortably runs 25–40 ERPNext users. Even a 100-user instance rarely needs more than $100/month of compute. On paper, self-hosting wins every cost comparison.

The invisible cost is operations. A production ERPNext instance demands:

Call it 4–10 hours per month of competent work. At a loaded engineer cost of $50–$100/hour, the "cheap" option costs $400–$1,000/month in time — unless that engineer already exists, already maintains other servers, and has slack capacity. That is the honest test for self-hosting: not "can we afford a VPS" but "do we already employ this person."

Failure modes we see in the wild: no off-server backups (the catastrophic one), Redis and MariaDB on default configs, SSL certificates that expire on a weekend, bench environments so far behind that upgrading requires a migration project, and the single engineer who knew the setup leaving the company.

Best for: companies with real in-house DevOps capability, strict data-residency or compliance requirements, deep customization needs, or many sites where per-site PaaS pricing would compound.

Option 3: Managed ERPNext Hosting

Managed hosting is the middle path: a partner provisions and operates dedicated infrastructure for your ERPNext — handling updates, backups, monitoring, security, and upgrades — while you retain everything self-hosting offers: custom apps, full data ownership, choice of region, and server-level flexibility when needed.

Typical 2026 pricing runs $100–$250/month for small-to-mid instances and $200–$400/month for larger deployments, usually including daily off-site backups, uptime monitoring with alerting, security patching, bench updates, and assisted major-version upgrades.

The economics work because a specialized provider amortizes one operations team across many instances. The 4–10 hours/month you would spend self-hosting becomes minutes of their standardized tooling. You pay more than raw VPS rent and dramatically less than DIY time cost — with an SLA instead of hope.

ECOSIRE offers managed ERPNext hosting through ECOSIRE.IO, our managed-hosting platform for open-source ERPs (ERPNext and Odoo), with daily verified backups, monitoring, and upgrade management included. Because the same team handles ERPNext support and maintenance, hosting and application support come from one accountable party — no "it's the host's fault / it's the app's fault" ping-pong.

Best for: SMBs and mid-market companies without a Linux team, businesses running custom Frappe apps that exceed PaaS constraints, and anyone who wants self-hosting freedom with someone else carrying the pager.

Head-to-Head Comparison

How to Decide in Five Questions

1. Do you employ someone who administers Linux servers today, with capacity to spare? No → eliminate self-hosting immediately. The romance of the $20 VPS dies at the first 2 a.m. outage.
2. Do you need custom Frappe apps, unusual integrations, or server-level tuning? Yes → self-hosted or managed; Frappe Cloud only on its higher tiers.
3. Do you have data-residency or compliance constraints (specific country, private network, audit requirements)? Yes → self-hosted or managed in your required region.
4. Will you run multiple sites (production + staging + training)? Yes → per-site PaaS pricing compounds; a single self-hosted or managed server running multiple benches is usually cheaper.
5. Is ERP downtime expensive for you? If an hour of outage costs more than a month of hosting, pick whichever option gives you a real SLA and tested restores — that is Frappe Cloud or a credible managed partner, never the unattended VPS.

A pattern we recommend often: start on Frappe Cloud or managed hosting for go-live (minimize variables during the riskiest phase), and revisit after a year once your usage profile, customization depth, and data volumes are known. Migrating a bench between hosts is a well-understood, low-risk operation — typically 2–4 hours of work with under 30 minutes of downtime — and something our ERPNext migration team does routinely.

The Backup Paragraph You Should Not Skip

Whatever you choose, verify these five things in writing: backups run daily and automatically; backups include both the database and the files volume (attachments live outside the DB); backups are stored off the production server; someone has actually performed a restore in the last quarter; and you can download a full backup yourself at any time (it is your data). Every horror story we have been called in to rescue — and there have been several — failed at least three of these five.

Talk to Our ERPNext Team

If you are weighing these options for a new implementation or an existing instance that has outgrown its setup, our team will give you a straight recommendation — including "stay where you are" when that is the honest answer. We handle ERPNext implementation end to end and provide managed hosting via ECOSIRE.IO when that is the right fit.

Get a hosting recommendation for your ERPNext →

Frequently Asked Questions

What is the cheapest way to host ERPNext?

A self-hosted VPS is the cheapest in raw dollars — a capable 4 GB/2 vCPU instance costs $12–$25/month. But it is only genuinely cheapest if you already employ someone with Linux and Frappe bench skills who has spare capacity. Factoring labor at market rates, managed hosting ($100–$250/month) is usually the lowest true total cost for companies without that person on staff.

How much RAM does ERPNext need?

Minimum 4 GB for a small production instance (up to ~10–15 users), 8 GB for 25–50 users, and 16 GB+ for 50–100 users. The stack runs MariaDB, three Redis instances, Gunicorn workers, and background workers concurrently, so undersizing RAM causes swapping and the characteristic "everything is slow" complaint. RAM is the cheapest performance upgrade in the entire stack.

Can I move from Frappe Cloud to self-hosted later (or vice versa)?

Yes. ERPNext backups are portable — a database dump plus the public/private files archive restores onto any bench. Frappe Cloud lets you download full backups, and any competent partner can execute the migration with under 30 minutes of cutover downtime. Hosting choice is not a lock-in decision, which is one of open-source ERP's underrated advantages.

Is Frappe Cloud better than self-hosting for production?

For most businesses without dedicated DevOps staff, yes — automated backups, managed updates, and one-click major upgrades remove the failure modes that hurt self-hosters most. Self-hosting wins when you need unrestricted custom apps, specific data residency, multiple benches on one server, or server-level tuning. Managed partner hosting covers that same ground without you operating it.

How much downtime should I expect during ERPNext version upgrades?

On Frappe Cloud or with a managed host, a major version upgrade (e.g., v15 to v16) typically means 15–45 minutes of scheduled downtime, preceded by a staging test. Self-hosted upgrades take the same downtime when rehearsed — but 4–8 hours of preparation work, and materially more risk if custom apps have not been tested against the new version first. Never upgrade production without a staging pass.

Does ERPNext run on shared cPanel-style web hosting?

No. ERPNext requires a full stack (Python workers, MariaDB, Redis, Node.js, background workers) that shared PHP hosting cannot provide. The minimum viable environment is a VPS with root access — or skip the server entirely with Frappe Cloud or a managed provider.