Sisense OEM Architecture

3 Flexible Deployment Options to Fit Any Need

    • Option 1: Service based on identical data sources and reports
    • Option 2: Service from identical copies or customized per customer
    • Option 3: Service based on data for each tenant is completely separate

 

Learn how Sisense provides different OEM architectures to support the way you need to work.

Technical Paper

By submitting this form, I agree to Sisense's
privacy policy and terms of service.

Sisense OEM use-cases: the advantages and disadvantages of each

The type of architecture suitable for a specific customer depends on the use-case, the needs of the customer, the resources that can be dedicated to the deployment (both allocated people, and allocated hardware), and preferences.

In this paper, we will outline the different ways Sisense supports the OEM use-case and describe the benefits and disadvantages of each.

Sisense OEM Architecture

“It’s recommended to review all options to choose the OEM architecture deployment that is suitable to your organization's requirements.”