Häufig gestellte Fragen
Which ERP systems are operated multi-tenant?
The best-known true multi-tenant cloud ERPs include Oracle NetSuite, SAP S/4HANA Cloud Public Edition, Workday, Sage Intacct and Acumatica, whose vendors serve all customers on one shared instance. Editions of Microsoft Dynamics 365 and Odoo are also operated in this model depending on the variant, while the same vendors in some cases also offer dedicated single-tenant options. The distinction by edition is important: SAP, for instance, clearly separates the multi-tenant Public Edition from the single-tenant Private Edition. For industry-specific requirements it is also worth looking at specialists such as ams.erp (mechanical engineering) or CSB-System (food industry), which do not necessarily operate multi-tenant.
What is the difference between multi-tenant and single-tenant ERP?
In a multi-tenant ERP, many independent customers share a single software instance and usually the same infrastructure, with the data separated logically via a tenant identifier. In the single-tenant model, by contrast, each customer receives their own dedicated instance with its own application and database. Multi-tenancy enables central, uniform updates and lower pro-rata operating costs, but restricts deep customisations. Single-tenant offers more isolation, more freedom to customise and control over update timing, but requires greater maintenance effort and is usually more expensive.
How secure is the data in a multi-tenant ERP?
In multi-tenant systems, data separation is usually logical: each record carries a tenant identifier, and every database query is strictly filtered by this ID, supplemented by encryption and role-based access control. Depending on the architecture, isolation ranges from a shared database schema through separate schemas to a dedicated database per tenant, with isolation increasing in that order. Advocates argue that professional providers secure all customers simultaneously at a high level and thus often offer more security than individual on-premises installations. What remains critical, however, is that purely logical separation is not physical or cryptographic isolation, and configuration errors can theoretically affect multiple tenants.
Is a multi-tenant ERP GDPR-compliant?
A multi-tenant ERP can be operated in a GDPR-compliant manner, provided the vendor offers EU hosting, a data processing agreement (DPA) and verifiable technical and organisational measures for tenant separation. Since several companies share one platform, data location, subcontractors and deletion concepts should be regulated particularly clearly in the contract. With US cloud providers, a residual uncertainty remains due to the CLOUD Act and the legal situation following the Schrems II ruling, which the EU-US Data Privacy Framework addresses but does not fully resolve; a legal challenge against the adequacy decision issued in 2023 is pending before the ECJ. For particularly sensitive data, EU hosting or a provider without US corporate ties is therefore recommended.
Can I customise a multi-tenant ERP individually and control updates myself?
Deep interventions in the source code are not possible in multi-tenant ERPs, because code and runtime are shared by all tenants and a change to the core would otherwise affect every customer. Instead, adaptations are made via configuration, predefined extension points and interfaces; in SAP S/4HANA Cloud Public Edition, for instance, via key-user tools (in-app extensibility) and loosely coupled side-by-side extensions on the Business Technology Platform rather than classic ABAP customising. The vendor rolls out updates centrally and for all tenants at the same time, often in a fixed release rhythm with several updates per year. This relieves the company's own IT team but takes away control over the exact update timing, which can be relevant in highly regulated environments.
Is a multi-tenant ERP automatically cheaper and more powerful?
Thanks to the shared infrastructure, pro-rata operating costs often fall, and resources can be allocated elastically as needed, which is why multi-tenant models are often regarded as cost-effective. A blanket cost advantage is not guaranteed, however, since licence, customisation and integration costs largely shape the total effort. On the performance side, the so-called noisy-neighbour problem can occur when a single tenant overloads the shared platform with very resource-intensive queries or workloads and slows down other tenants. Reputable providers counter this with resource limits, load balancing and in some cases tenant-specific database isolation, which is why service level agreements on availability are a key selection criterion.