How are you handling the Camunda 8.6 licensing changes?
The single licensing model for self-hosted Camunda 8.6 removes the previously available free option. Using just Zeebe and the process engine in production (without Operate and Tasklist) was previously possible, but the 8.6 update appears to prevent this.
The AWS self-hosted plan costs nearly $330,000 annually, and pricing for self-hosting on your own infrastructure is currently unavailable on the Website.
How are you addressing these costs for commercial projects?
Or Are you already using tools like Operate in production with an existing enterprise license and nothing really changes for you?
Hi @lirav27 - I replied to another thread you had commented one, but wanted to share some information here as well:
The link to the AWS pricing doesn’t work for me, can you DM me some additional details? I’d like to share it with our sales and AWS teams to make sure we have accurate information online! While it is certainly possible that enterprises need to scale their Camunda deployment to that size, that is not a base cost! That cost would be for running hundreds of thousands - if not millions - of processes across multiple tenants, which not every enterprise needs.
To get an idea of what C8 would cost to run, the best approach is to reach out to our sales team here: Contact Us for Camunda Enterprise
We do offer free, non-commercial licenses to non-profits, academic institutions, for personal/private use, and for development and testing. If you believe your use case qualifies for a free license, you can reach out to us here: Camunda 8 Self-Managed for Non-Commercial License
The team is working on building a pricing calculator to launch on the website to help provide more accurate price estimates without needing to contact sales, but the calculator is currently in development.
Thanks @lirav27 - I’ll share this feedback with our AWS Partner Manager and sales team. That pricing reflects a more highly scaled and powerful Camunda deployment and is not a minimum/baseline price.
Additionally, I must point out that this is a significant change. For anyone using Camunda in customer projects or as a foundation for process orchestration, this move essentially forces users to either purchase a license or remain on version 8.5, facing potential security risks in the future. Projects that don’t require Optimize, Tasklist, or similar features are now also forced to buy a license for features they don’t use.
@nathan.loding I’ve read those posts. Maybe it makes sense for Camunda as a Company but It doesn’t change anything due the fact that you can’t use the engine anymore without a licence like I mentioned.