Multi-Tenant ERP
Multi-tenant ERP is an architecture where a single application instance serves multiple customer organisations (tenants), with logical data separation. The opposite is single-tenant, where each customer runs their own dedicated instance. Public-cloud SaaS ERPs (Oracle NetSuite, SAP S/4HANA Cloud public edition, Microsoft Dynamics 365 Business Central SaaS, Odoo Cloud, weclapp, Xentral) are predominantly multi-tenant. Private-cloud or on-premises ERPs are typically single-tenant.
Tenant isolation models
- Shared database, shared schema: all tenants in one database with tenant-id as a column on every table. Cheapest, most efficient. Risk: query-leak bugs cross tenants.
- Shared database, separate schema: each tenant gets its own schema. Mid-cost, better isolation, harder to maintain at scale.
- Separate database per tenant: each tenant has a dedicated database. Highest cost, strongest isolation, easiest backup/restore per tenant.
SaaS-ERP vendors choose based on volume economics. NetSuite uses shared-database-shared-schema; SAP S/4HANA Cloud uses dedicated databases per customer.
Practical implications for customers
Multi-tenant ERPs enforce upgrade discipline: all customers are on the same version, upgrades happen on the vendor's schedule (typically quarterly), and you cannot defer them. This eliminates technical-debt accumulation but reduces customisation flexibility. Customisations must be additive (configuration, extensions, app marketplace) rather than core modifications. For mid-market companies, this is usually a net positive: lower long-term TCO, automatic security patching, less in-house IT effort. For highly customised enterprise workflows, single-tenant (private cloud or on-premises) remains the choice.
Related Topics
Frequently Asked Questions
Is my data safe in a multi-tenant ERP?
For reputable vendors, yes. Multi-tenant SaaS providers like SAP, Microsoft, Oracle and Salesforce invest heavily in tenant isolation, encryption-at-rest, encryption-in-transit, and intrusion detection. Their compliance certifications (SOC 2, ISO 27001, BSI C5) verify these controls. Smaller multi-tenant vendors warrant deeper due diligence on isolation and security practices.
Can I customise a multi-tenant ERP?
Yes, but with constraints. Configuration changes (form layouts, workflow rules, custom fields) are fully supported. Extensions via the vendor's app platform (SAP BTP, Microsoft Power Platform, NetSuite SuiteFlow) are encouraged. Core code modifications are not possible. The customisation surface area is typically smaller than in single-tenant or on-premises deployments, but newer platforms close the gap each year.
How does multi-tenant differ from multi-mandant?
Different concepts. Multi-tenant is about the vendor serving multiple customers from one technical instance. Multi-mandant (multi-company) is about one customer running multiple legal entities or business units in the same ERP instance. Most ERPs support multi-mandant regardless of whether they are multi-tenant or single-tenant.