I’ve been doing some retrospective cost analysis on our Camunda implementation, and the numbers are making me wonder where the real expense actually is.
On the surface, Camunda’s licensing costs are straightforward. You pay per instance, you manage the bill. But when I started adding up developer time—initial implementation, ongoing maintenance, custom integrations, debugging issues that come up when workflows get complicated—the people costs started dwarfing the licensing fees.
I’m trying to figure out if this is just how it works with platform adoption, or if there’s something about Camunda’s architecture that makes it inherently labor-intensive.
Here’s what I’m really asking: if you’ve deployed Camunda at scale, what percentage of your actual TCO would you say comes from licensing versus developer time? And more importantly, is there anything you discovered later that would have changed how you structured the deployment to reduce either of those cost categories?