Skip to main content

Deploying Qlik Sense Enterprise in a multi-cloud environment

A Qlik Sense Enterprise multi-cloud deployment lets you deploy both Qlik Sense Enterprise on-premises and Qlik Sense Enterprise on cloud so users can develop apps on-premises and access them from the cloud.

The primary components of a multi-cloud deployment are:

  • Qlik Sense Enterprise on Windows, deployed on-premises.
  • Qlik Sense Enterprise SaaS, deployed to a Qlik-managed cloud infrastructure.

After you install your Qlik Sense Enterprise on Windows on-premises, you can chose to configure multi-cloud with Qlik Sense Enterprise SaaS. Once your multi-cloud deployment is configured, you can distribute Qlik Sense apps that you create in Qlik Sense Enterprise on Windows to the cloud for consumption. Users are integrated through the identity provider and consume a single license regardless of whether they connect through the Qlik Sense Enterprise on Windows hub or the cloud hub.

Example multi-cloud deployment architecture

The characteristics of a multi-cloud deployment are:

  • Qlik Sense Enterprise on Windows installed on-premises.
  • Access to Qlik Sense Enterprise SaaS.
  • An identity provider that supports OIDC and SAML to integrate user authentication between on-premises and cloud, or a local bearer token.
  • A license that includes multi-cloud (enabled).

Who should consider a multi-cloud deployment:

  • You have Qlik Sense Enterprise on Windows running on-premises and you want to expand to the cloud.
  • You want to develop apps in a Windows environment and allow users who cannot access your Windows environment to consume apps.
  • You want to scale out the number of users consuming apps using cloud resources.

For an example of how to distribute an app from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS, see Distributing apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!