Multi-tenant versus Single-tenant ERP – a comparison

June 10, 2010
By djohnson

Warning: customers care about results, not about infrastructure. The focus of this article will be on how different infrastructures can influence customer results.

What is a multi-tenant architecture

Journalists and marketers are proclaiming that multi-tenant cloud architectures are the wave of the future. Let’s start by trying to define multi-tenant SaaS.

Wikipedia sums it up nicely by saying “the principle of multi-tenancy is not universally accepted and supported within the software industry.”

Under a strict definition, a multi-tenant application is a single piece of software that is shared by multiple users. But, there are many components which can be “multi-tenant” – these include the application code, operating system, data storage software, and computing resources. In an ERP application there are many varieties of multi-tenant depending on which of these resources are shared.

Even within the data storage, there are many different options. The ideas of separate databases, shared database – separate schema, and shared database – shared schema are well presented in an MSDN article on multi-tenant data architectures. The article discusses the trade-offs involving development time, economic savings, backups, scalability, security and regulatory concerns.

Multi-tenant ERP


Different multi-tenant architectures are better suited to different types of ERP customers. Complete multi-tenant is best suited to small companies or specific vertical solutions which have highly repeatable and mostly standard processes. Multi-tenant options with single-tenant components are best suited to larger businesses with non-standard processes or significant integration requirements.

In the future, if there are well followed cloud ERP standards and a wealth of applications, the distinction between these models tends to erode. As all clouds interact seamlessly and more applications are available, the need for integration will become less and less. Of course, ERP Cloud News does not recommend waiting for this to happen, as standards and complete cooperation among worldwide vendors is not probable in the near future.

Ideal uses for multi-tenant

Multi-tenant applications, operating systems, data storage, and computing resources are tools that can be used to perform work. In the case of ERP, the work involves running a business with proper automation, accounting, and reporting. A good craftsman has many tools in his bag. Multi-tenancy is one of those tools. Just like a carpenter would not use a chain saw to cut molding, software engineers will not need to use multi-tenant applications in every ERP situation.

Multi-tenant is appropriate for business tasks that are common across many customers or divisions of a company. Just like it does not make sense for a gamer and a business user to share the same application (although there are probably scenarios where the two are not much different), it does not make sense for an at-home craft business to share the same application as a Fortune 100 company.

ERP customers need the following:

  • Features that meet business needs
  • Security and regulatory compliance
  • Ability to modify application if business needs change
  • Lowest possible price for all considerations above

The last point is perhaps the most important because both single and multi-tenant applications can be used to solve most problems, but with comparable features, price and security will be the deciding factors. The security issue is beyond the scope of this posting, but we may get to it in a future article.

Multi-tenant pricing

Multi-tenant ERP systems are generally priced competitively with their legacy system counterparts. This means that multi-tenant vendors are pocketing additional profits, not reaching critical mass, or not realizing the cost savings that have been promised.

Multi-tenant systems can gain economies of scale with regard to:

  • Shared hardware costs (most talked about, least important)
  • Shared IT resources
  • Application and OS upgrades

The most talked about is the infrastructure savings, but the most important is the cost of IT resources and software updates. For many mid-sized ERP implementations the cost of hardware can be only 5% of the overall project cost – meaning that an additional 20% hardware efficiency will only save customers 1% of their overall project cost.

The savings from reducing IT staff by eliminating software installations and upgrades is far more compelling, but only on a case-by-case basis.

Multi-tenant systems are potentially more expensive because:

  • Vendor lock-in – forced to use a single vendor
  • Feature development – custom features have to be developed by specialized resources

Vendor lock-in can come in many forms such as limited support options, price increases, forced upgrades, and lack of customization features. Sometimes these issues can lead to higher out of pocket expenses and sometimes they lead to higher costs in terms of limited business processes.

The diagram below based on research Forrester Research, “SaaS Clients Face Growing Complexity,” April 2008 shows the top 8 reasons why CFOs pass on SaaS ERP.

Forrester CFO SaaS Issues 2008


Ideal multi-tenant applications

From a customer perspective, the ideal multi-tenant application is one where hardware costs are high relative to the application cost and where the application is a commodity to eliminate the opportunity for vendor lock-in.

Utility applications such as email and web-hosting fit these requirements and are well suited to a multi-tenant design. Implementing and maintaining email and web servers can be expensive, and sharing this cost across multiple customers will reduce costs tremendously. However, even simple applications like email and web hosting may require some customization. For example, different customers may want different firewall settings for their web server or different spam filters for email. In these cases, the email application will have to be adapted for multiple customers or a single-tenant component (firewall, spam filter) will have to be added and integrated.

ERP applications (the topic of this blog) have lagged behind others in terms of multi-tenant adoption. Small businesses with simple processes or enterprise departments have started taking advantage of this trend, but in many cases, ERP applications are highly customized programs with interfaces into multiple systems. While attracted approximately 11% of the CRM market in 2008, the entire multi-tenant ERP market only accounted for less than 4%. This could be because the costs associated with customization tend to outweigh the benefits of multi-tenant, or because the larger businesses lag behind when it comes to adoption of new technologies.

Customer size matters – Multi-tenancy in larger businesses

When a customer is large enough to support a full time IT staff and uses enough resources to justify several servers, the benefits of multi-tenant become quite small. A business of this size can benefit from economies of scale without a shared multi-tenant architecture. The customer can install the application in-house or outsource the work depending on security considerations and business requirements.

However, businesses with multiple offices may still benefit from multi-tenant architectures through cost reductions associated application upgrades across different operating entities.

Multi-tenant ERP in the enterprise

Multi-tenant ERP in the enterprise

Businesses running multi-tenant applications only have to update one application, while those running multiple copies of a single tenant version will have to do multiple upgrades. The same principle applies to the operating system. One operating system is easier to patch than multiple operating systems.

For example, a web-based architecture may allow a company to serve all divisions and entities using a single copy of the application. In the case of ERP, this means that the application needs to be able to manage multiple currencies, different business processes, and maintain separate reports for the different operating entities. In this scenario, the definition of multi-tenant is stretched to mean different operating units instead of different companies. By running multiple operating units on a single application, the enterprise can centralize operations and save costs.

Multi-customer versus multi-entity

Multi-tenant ERP versus multi-entity ERP

Multi-tenant ERP versus multi-entity ERP

Vendors offering a multi-customer architecture (multiple non-related entities on one software application) will not be able to provide the same flexibility as a multi-entity architecture (multiple subsidiaries or other related entities). Advances in software are making it possible to customize more through configuration, but a multi-customer architecture will always be limited with regard to building external interfaces, modifying data structures, and building custom processes.

Small businesses with standard processes can use configuration tools, metadata options, and database schemas to customize a multi-customer architecture to their needs. Medium and large sized businesses with complex processes and multiple integration points would be best served by their own multi-tenant software license.

Managing your multi-tenant ERP architecture

There are two primary ways for businesses to purchase and manage a multi-tenant ERP architecture.

  1. Option 1: Outsource everything (hardware, licensing, upgrades, configuration) to a single vendor who rents the software to you and manages all operations.
  2. Option 2: Purchase a software license and enlist the services of a value added reseller (VAR) who understands your business and is an application expert.

This distinction is over-simplified because these options can be packaged many different ways, but this abstraction is useful for the discussion that follows.

The best option for your business depends on your cash flow requirements, operational expense versus capital expense, company IT resources, and your company culture. Companies wanting to preserve short term cash should utilize option 1 while companies who want to own their systems and depreciate them over time should utilize option 2. Companies with spare hardware and IT resources should purchase while companies with little IT expertise should select the rental option 1. For larger ERP customers, option 2 is usually the most cost effective over an extended period of time.

Utilizing a value added reseller (VAR) which understands both your business as well as ERP software is highly recommended. The hourly costs of value added resellers can appear high ($100 – $200/hour in the USA) but the customizations and modifications are critical to running your business properly. Most importantly, you can evaluate customizations on a case by case basis. For example, if it costs $5,000 to implement a customized interface between your bank and your ERP system, you can decide whether or not that is justified based on time savings and the benefit of having real-time information.


Multi-tenancy is a tool to add to your IT toolbox. This tool can save you money when used properly. However, flexibility is critical to your business operations. Your legal, regulatory, business, cost, and customization requirements can change, so make sure that your software can change with you.

Multi-tenancy can be delivered in different ways. When selecting a multi-tenant offering, avoid vendors which lock you in to their support and software because this may lead to rising prices and a lack of flexibility.

Medium and large sized businesses are best served by multi-tenant offerings which are not shared by several customers while smaller business with standard processes may find lower prices when vendors provide a facility for sharing costs across companies. Companies with little IT expertise should look for SaaS solutions with allow for outsourcing of hardware purchasing, software upgrades, monitoring, and backups.

If you have had experience, good or bad, with multi-tenant applications, we would enjoy hearing from you.

Tags: , , , , , , ,

One Response to “ Multi-tenant versus Single-tenant ERP – a comparison ”

  1. Ken Del Gobbo on June 10, 2010 at 3:03 pm

    Great article. This is exactly what I’ve been hearing from our value added resellers (VARs) that work with our customers on a daily basis. Some customers want SaaS and multi-tenant, others want on-premise and multi-tenant, and others want SaaS and single-tenant.

    Having a solution which supports all of these options has been critical for my company ( In our sales efforts, price is not usually the driving factor, instead it’s the customer’s level of IT expertise and process complexity which determines whether they go SaaS or on-premise and single tenant versus multi-tenant.

Leave a Reply