Worried about devolutions licensing changes
Every new major release that devolutions promotes got a little statement with "Special license x required". Devolutions for a Service Provider/MSP isn't a cheap product. You need RDM & DVLS licenses. For the future you will also need "PAM, Gateway, etc." I can't see any prices yet on the main page, but if we going to implement this features we will depend on this in 2-3 years. I liked DVLS as a single license fit's all thing. why are you guys doing this and how far will this go? are there prices to see for current customers? I don't wan't to implement a feature now that i can't afford when i need to relicense.
Kind regards
Jannis
All Comments (1)
Hello,
If you use DVLS to store connections and credentials in vaults as they have existed for close to ten years, and use our authentication layer, AD cache, etc. (lets call this DVLS Core...), you haven't been impacted by any of our changes.
To this Core, we've added OAuth, scheduled reports, alerts and notifications, syslog, etc. over the last years, and that is a good demonstration of the intent we have with the product. We continually improve it, and the team that works on core features has even increased in size.
For the newer modules, we are going in an area reserved for those customers with the utmost needs in security, an area that most of our users have to pay astronomic prices for a product in that market. We call those our Tier 1 customers. The current SKUs for modules/features are for the PAM Module, and for the Gateway. I feel that we are justified in marketing those features separately.
By choosing to charge for advanced modules, we can keep the core product at an affordable price, and that is critical in my view. Most of our customers pay between 40-125$ per YEAR per user. If you have used our products for a while, you will know that, paired with RDM, your productivity gain pays for that in a matter of a few weeks. We are not trying to get more money from the same feature set, but rather by satisfying a set of totally different needs.
I hope this clarifies our strategy and reassure you that the core features you use will not be subject to being introduced as a licensed feature.
Best regards,
Maurice