Multi-Company Hosting
ERPNextCalc Multi-Tenant Frappe v15 Bench Isolation Blueprint
ERPNextCalc models both shared multi-site Frappe benches and isolated per-tenant bench containers so agencies avoid unexpected Python dependency collisions.
Sharing one Gunicorn + Redis + Supervisor pool across 5 low-traffic subsidiary sites saves ~2.4 GB of duplicate worker RAM compared to running 5 separate containers.
ERPNextCalc Shared Bench vs Isolated Bench Trade-offs
All sites on a single Frappe bench share identical app versions (Frappe, ERPNext, HRMS) and one Supervisor worker pool. One heavy tenant import can temporarily saturate the shared long queue.
We recommend DNS multi-tenancy on one bench for subsidiary companies under one group, and separate Linux users/benches when clients require staggered version upgrades.
ERPNextCalc Redis Key Prefixing & MariaDB Schema Separation
Each Frappe site receives its own isolated MariaDB database (_hash) and prefixes Redis Cache keys by site hash, guaranteeing strict financial data isolation.
We advise budgeting +1,024 MB of InnoDB buffer pool for every additional 25 active multi-tenant users.
ERPNextCalc DNS Multi-Tenancy Activation
bench config dns_multitenant on
bench new-site subsidiary-b.erp.internal --mariadb-user-host-login-scope='%'
bench --site subsidiary-b.erp.internal install-app erpnext
bench setup nginx && sudo systemctl reload nginx
Architecture Shared App Code RAM Overhead per Extra Site Upgrade Independence
1 Bench / 5 Sites Yes (Identical) ~150 MB (DB tables) Coupled upgrades
2 Isolated Benches Independent +2,500 MB per bench Full version autonomy
Dedicated VDS per Tenant Independent Full VM isolation Zero noisy neighbors
Evaluating multi-tenant bench isolation with ERPNextCalc prevents agency hosting headaches before onboarding your second entity.
Adjust user counts on ERPNextCalc to reflect combined concurrency across all active tenant sites.
ERPNextCalc Multi-Company Hosting FAQ
DIRECT ERPNEXTCALC HOSTING VERDICT — 8000 DAILY ERP VOUCHERS
Target sites/common_site_config.json
RECOMMENDED HOST
UltaHost Dedicated EPYC VDS
$37.50/mo
ERPNextCalc 16GB pick (116,000 IOPS) — Dedicated VDS RAID-10 NVMe + 150Gbps DDoS
Claim 2026 Discount →
SUBSEA ROUTE PICK
Hostinger KVM NVMe
$10.49/mo
Low-RTT node for frappe-bench gunicorn (105 ms ledger post)
Start Cloud Trial →
FIXED TARIFF TIER
InterServer Price-Lock KVM & ZFS
$6.00/mo
Steady ERPNextCalc secondary tier (1500–8000 daily ERP vouchers)
Review Fixed Slice →
ERPNextCalc Partner Voucher (UltaHost): 40% Off Annual VDS + Free Managed Migration
Copy [ULTA20] & Open UltaHost
Chart 1: tabGL Entry & tabStock Ledger Entry InnoDB pages throughput (116,000 IOPS) for ERPNextCalc nodes.
ERPNextCalc FAQ: Can two sites on the same Frappe bench run different ERPNext versions?
No. Because all sites in one bench import the same Python virtualenv and apps/ directory, differing versions require separate benches.
frappe-bench gunicorn + python-rq + MariaDB Host Selection — IOPS & Monthly Spend
UltaHost Dedicated EPYC VDS
142,100 IOPS ($37.50/mo)
Hostinger KVM NVMe
133,400 IOPS ($10.49/mo)
InterServer Price-Lock KVM & ZFS
124,700 IOPS ($6.00/mo)
ERPNextCalc I/O comparison (2026-11-12) | sites/common_site_config.json
Packet-to-Disk Path for frappe-bench gunicorn + python-rq + MariaDB on ERPNextCalc
1. EDGE
ERPNextCalc
8000 daily ERP vouc
2. ENGINE
frappe-bench gunicor
8/16/32GB
3. LIMIT
gunicorn_workers=5
sites/common_site_con
4. DISK
116,000 IOPS
105 ms ledger post
9.7
/ 10
INFRA AUDIT
[+] Key Infrastructure Pros
Stabilizes tabGL Entry & tabStock Ledger Entry InnoDB pages cache at 8000 daily ERP vouchers within 16GB.
Sustains 116,000 IOPS on tabGL Entry & tabStock Ledger Entry InnoDB pages while preserving 105 ms ledger post.
Trims ERPNextCalc 3-year infrastructure bills 70%–85% versus metered SaaS seats.
[-] Trade-Offs & Watchouts
Deepest UltaHost Dedicated EPYC VDS rate ($37.50/mo) requires selecting a 12m or 24m term.
Base OS templates need sites/common_site_config.json tuning ( gunicorn_workers=5 & background_workers=3) before peak load.
Deploy This ERPNextCalc Stack If
Lean teams managing 8000 daily ERP vouchers via declarative sites/common_site_config.json files.
Builders needing root access to set gunicorn_workers=5 & background_workers=3 in sites/common_site_config.json.
Skip This Setup If
Weekend throwaway demos under 72 hours (use hourly Hostinger KVM NVMe billing instead).
Teams unwilling to edit sites/common_site_config.json or run basic Ubuntu maintenance.
More frappe-bench gunicorn + python-rq + MariaDB Sizing Guides
ERPNextCalc FAQ: Does multi-tenancy increase Gunicorn worker memory linearly?
Only slightly (~15–25 MB per site for cached doctype metadata) because core Python modules are already loaded.