Migration path for MSP delivery model

[Greg_Oliven]

I am a Managed Service Provider (MSP) partner running our own #Qlik Sense Enterprise for Windows in Azure, selling read-only (analyzer license) subscriptions to our Qlik apps with SAML authentication. Our subscribers are all using the same apps, but don't interact with each other, cannot edit our charts, and cannot see our load script

I am looking for a migration path as we scale up that gets us into Qlik Cloud capabilities, but preserves our ability to do  frequent simultaneous updates of our apps to multiple customers, and also protects our intellectual property (i.e. customers shouldn't be able to see load scripts or edit charts). Is there a parallel in the SaaS world for write-once publish-many, to multiple unrelated customers, with easy onboarding for new customers?

[Leigh_Kennedy]

Have you trialled SaaS and found challenges, or are you just wondering if we support this?

Without understanding more about your situation I can't say for sure if we can support this today or not, however a lot of work is going into supporting MSP/OEM type use-cases this year.

@Jeffrey_Goldberg might have some more to add here.

[Greg_Oliven]

Thanks lkn for your response. I have not tried SaaS yet - I am indeed wondering if you support it.  I *think* your multi-cloud distribution would solve the write-once/publish-many side of the challenge. It's the other side of the equation that looks challenging to me:

1. rapid deployment to a new customer who does not already have a SaaS tenant with Qlik, 
2. protecting our IP

You also call out OEM - how does this work in the SaaS context?

[Leigh_Kennedy]

SaaS has built in write-once, publish many support from shared to managed spaces.  Not sure what you are getting at about protecting your IP, but Qlik can not see your apps without you inviting us to your tenant - your content is uniquely encrypted to your tenant.

OEM is not officially support yet, but we are working on that at the moment.

[Greg_Oliven]

My question about IP comes from my assumption that on Qlik SaaS, I would have to help each of my clients set up their own tenant, and publish my apps to them, where I would no longer have control over the apps I'd just sent out to multiple different tenants.  Right now on my own QSE on Windows, as I sell subscriptions to my apps, I just onboard each new client onto my server with an Analyzer license.

Is my assumption wrong - can I actually just establish my own Qlik SaaS tenant and onboard my customers as Analyzer users - effectively replicating my current hosting model on Qlik SaaS?

[Leigh_Kennedy · Accepted solution]

You can create a space for each customer and ensure that each customer can only see their own apps.  you need and IDP set up, but you could have a group per customer and assign view access to the customers space to that group.  That should give you what you need.

[Greg_Oliven]

Leigh - this sounds promising. I'm taking these ideas to my sales team to hammer out the details. Thanks very much for this brainstorming!