On-premises: the license model for server-based software

Software manufacturers are increasingly offering the cloud computing model: software-as-a-service. One of the best-known examples is the Microsoft Office suite, which is available for a regular license fee. But until 2010, the on-premises model was standard for the Microsoft Office package and other software providers. On-premise refers to licensees installing the software in their own IT environment – without the cloud or internet access. We explain what exactly on-premises is, what advantages, and disadvantages come with the license model for server-based software, and where on-premises is still relevant today.

On-premises refers to the use of the company’s own servers and IT environment – on site. With this usage model, a customer often buys or rents server-based software as a licensee, which is installed on their own servers or rented servers. Since the licensee runs the software in their own data center on their own or rented hardware, this is also called ‘inhouse’.

In contrast to cloud computing, customers of on-premises models have full control over data and also assume responsibility for the associated risks. Use of the provider’s hardware is not possible with on-premises. This clearly differentiates the model from cloud computing alternatives.

However, licensees not only take on responsibility but also all costs incurred in the use of the software. These typically include maintenance fees and expenses for running software and hardware. In the case of open-source software, a close community often handles further development and bug fixing in practice. The disadvantage here is that warranty claims are not possible. If necessary, support or provision of software updates can be purchased from relevant service providers.

Licensees gain access to the software via a desktop application or a web-based user interface. Companies that manage sensitive data usually opt for a desktop-based application in order to rule out potential security gaps and unauthorised access to the system.

Since 2010, the importance of on-premises has continuously declined as the license model is increasingly giving way to the more modern cloud computing model: software-as-a-service (or ‘SaaS’ for short). With this model, the licensee pays a usage fee that covers operation and maintenance in addition to the software. Unlike the on-premises model, the usage license is not purchased on a one-time basis but needs to be renewed through regular payments. All hardware and software resources are made available by the provider.

Before the switch to cloud computing, well-known examples of established on-premises products included the Microsoft Office package, the Adobe Creative Suite, and SAP. Today, the license model for server-based software continues to be the better alternative to modern SaaS for many companies. The main reasons for this include strong data protection and complete control over data and access.

Another and particularly frequently used benefit compared to cloud-based alternatives is the possibility to customise the software. The standard software forms the underlying foundation and is the basis for software customisation or extension according to special customer requirements and areas of application. However, this also comes with significant costs for the adjustments or an increase in license fees. Moreover, updates that later become necessary will be more difficult and expensive to perform than with the standard software.

The on-premises model has many pros and cons:

• Control: Licensees gain full control over all data and can decide who gets access. The customers are also responsible for the utilisation of internal resources, and for running the software.
• Data protection: With the inhouse model, licensees retain all data in their own data centres; third parties do not receive any access to this data. This makes compliance with statutory data protection regulations easier, since cloud servers are often located in countries with different data protection rules.
• One-time costs: On-premises licensees pay a one-off fee that includes purchase of the software and unlimited use. However, the investment costs are accordingly higher than with subscription-based models.
• Independence: Licensees are independent from external service providers and from the licensor. Access to data is always ensured – even without an internet connection.
• Integration: The licensed software can be integrated deeper into the customer’s infrastructure and interlinked with other programs.

• Hardware: Licensees require the necessary hardware that is compatible with the software. Ongoing maintenance is the responsibility of the customer.
• Workload: Licensees need to install and run updates, patches, and backups to ensure stability and fix errors. This not only requires time, but also technical know-how within the company and among employees.
• License costs: In many cases, a license is limited to a certain number of workstations. Companies with lots of employees may therefore face high costs.
• Ongoing costs: Especially in the case of customised software, high ongoing costs may arise for software adjustments and updates in order to keep the software operational and fix errors.
• Lack of support: Typically, the further development of the software is discontinued by the manufacturer sooner or later. Once this happens, support also tends to come to an end.
• Resources: Although licensees have full control over software use, they are required to commit their own resources.

Although the importance of cloud computing is steadily growing, on-premises is still the better choice in many cases for companies and organisations. In sectors like finance or healthcare, companies are subject to particularly strict data protection requirements. With on-premises, sensitive data can be protected more effectively from unauthorised third-party access since the company itself manages the data and internal processes. The company defines who gains access to which data.