...
Since Mathias Kettner founded tribe29Checkmk, it has been a customer-driven company. Many features, even components, were designed to address specific problems of our customers. And for all these years, customers with a support contract with us could open feature requests for Checkmk.
...
As a result, we are shifting to a process, which focuses more on bringing in the most important customer ideas with a lot of community involvement, rather than on a bilateral customer-tribe29 checkmk interaction regarding a specific request. Our approach here is to implement a publicly available feature voting portal. This allows all customers and users to see currently requested features from all other customers and users and vote for them. Benefits of this approach are:
...
For our support customers, we will migrate all feature requests that are not checks & agents features in a sanitized form from our ticket system into this portal. After the migration tribe29 checkmk will stop accepting requests via the service desk.
...
Q: In the past, I paid for features to be implemented. How is this done in the new process?
A: tribe29 checkmk will not charge for the features selected from the feature portal
...