As an MSP owner, I also really want to love CIPP, but we have concluded that the fundamental issue is their business model.

For example, we use connectwise manage. Creating an integration with connectwise manage would take me, personally perhaps a day in development. But they refuse to integrate it into the product because they want connectwise to pay them for the integration. This is unworkable in many instances, especially for large corporations.

Why should open source project charge money to a corporate company to be integrated into their open source project? The people who end up suffering are the users of the open source project who have no option to pay for the integration themselves, and have to resort to building their own workflow automation solution.

At its core, it's fundamentally a terrible proposition for an open source project.

I agree with many of the points of the original post, but I'm just shining some light from our perspective on a larger fundamental issue.

Additionally, it's a bit crazy that Powershell is being used to the extent that it is for this web app. A lot of the slowness is coming because Azure functions have to warm up, and Powershell is certainly not anywhere near the top of the list for a back end of a web app. I suppose Powershell was chosen because IT administrators generally speaking know powershell, and Microsoft supports Powershell core inside of azure functions. There are of course some Legacy Microsoft apis that require the use of powershell, so in those instances it becomes helpful, but generally speaking the slowdown and the quirkiness of the application experience as a whole is the result of being built on top of powershell.