Playbooks suddenly require an enterprise license

I’m writing this with deep concern and disappointment regarding the recent change to the Playbooks plugin, which now requires an Enterprise license.

As a company that has committed heavily to open source tools, Mattermost being a core part of our infrastructure, this change feels like a major setback. We’ve relied on the Playbooks feature for years, and its sudden restriction has not only disrupted our workflows but also undermined the trust we’ve placed in the open source nature of this platform.

Removing an existing feature and placing it behind a paywall without prior warning goes against the principles many of us associate with open source development. It’s not just a technical issue; it sends a discouraging message to your open source user base and contributors. Features that users depend on being taken away overnight creates operational problems and hurts long-term adoption. At least I have not got any notice or info, that this will happen!

Right now, we are unsure how to even access our previously created playbooks. This is not just frustrating, it puts us in a difficult spot operationally.

I hope the team seriously reconsiders how changes like this are rolled out in the future. Transparency, stability, and respect for the open source community are essential values that should be preserved if Mattermost wants to remain a trusted platform for open source-oriented organizations.

Looking forward to a response and a potential solution on how we can recover our playbooks or continue using this functionality without being forced into a sudden license upgrade.

Best regards,
Nico Grienauer

4 Likes

I fully aggree regarding Mattermosts’ decision. There are a few posts in this forum that discuss these kind of changes made by Mattermost in the last few months. Unfortunately, Mattermost decided to fully ignore all questions and criticism and fully denies to write an official statement about that (including what direction Mattermost wants to go in the (near) future).
Indeed, very disappointing and a shame.

Regarding your problem with the plugin: in the major version 10.x.x, the Playbook plugin version 1.x.x should work like before. Only version 2.x.x is the enterprise-only edition. 1.x.x will be supported until v11.x.x (according to Mattermost).

If the screenshot was taken right after an update, you should try to disable and enable the plugin or remove and reinstall it. We had the exact same error message (after going from v9.11.x esr to v10.5.x esr)

2 Likes

thx for your reply!
Yes, it was after an update. We have these updates automated, so we have now to rebuild processes etc. which is quite annoying. think a downgrade help, but I should not have been forced into that in my opinion and understanding, what Open Source stands for.

2 Likes