For ERPNext: Which is better Multi Tenancy or Multiple Instance?

I have a need to setup multiple ERPNext on same VPS, each linked to a separate sub domain and each will have their own SSL using Lets Crypt.

In case of multiple instance we will get multiple Frappe instances but in case of multi tenancy there is only one instance. So logically it feels multi tenancy is resource friendly.

But when it comes to performance over period of time with many users will multi tenancy stand rock solid?

Experts on this please share your insights and help me decide which way to go.


1 Like

You can try with Press

1 Like

There was a PR review system that was running on a Kubernetes cluster [For Developers] Help us develop the PR Review System

I copied the useful parts from PR Review System into a Kubernetes api/operator + Frappe Framework app. It works on Kubernetes only.

In brief,

  • It can create container images from frappe framework, apps and branch combination. (it was used to create a frappe-bench from frappe or erpnext fork branches for PR review system)
  • It can execute any bench commands as kubernetes jobs. e.g. new-site, migrate, set-config, custom-command.
  • It can create ingresses pointing to benches, e.g. it created an ingress route for the sub-domain/domain combination as per the PR to be reviewed.

If you already use Frappe framework apps or ERPNext on Kubernetes, it is as easy as installing a Helm Release on your Kubernetes cluster and then operating the benches and sites from familiar Frappe Framework App (use System Manager role)

K8s Bench Interface - Frappe Framework App (Useful and familiar for frappe framework developers)

Kubernetes API + Operator (FastAPI, Kopf, python kubernetes client):



I know about Press. But my question is whether we should take the route of creating sites or creating separate instances for each different sub-domain?


If each site needs different app or different branch of the app then you will need multiple benches.

If one app is going to run on multiple sites and change in app code specific to site is not required then you can have 1 bench and multiple sites.


@revant_one How do you manage multiple sites when you need to “migrate” database changes? Each site has it’s own database and running “bench --site all migrate” for a few sites is OK, but if you have 100 sites, for example, I think this could take a while, no?

What’s the best strategy to reduce database migration time during updates?

In brief,

  • create new bench. Run old and new bench in parallel
  • backup site
  • move site from old bench to new bench and migrate.
    • if migrate succeeds, repeat for other sites
    • if migrate fails, move back the site to old bench and drop and restore to backed up database

After this you’ll have set of sites with issues on old bench and migrated sites on new bench.