Hey folks, did anyone else catch that leaked pricing spreadsheet from a competitor that's been floating around some DevOps circles this week? I won't name names, but it's for a major cloud management platform.
Seeing the raw numbers side-by-side with their public list prices was... enlightening. The discounts for multi-year commitments were deeper than I expected, and the per-host pricing tiers had some interesting breakpoints. It really makes you wonder about the true cost margins on these services.
For anyone doing budget planning, this kind of data is gold. It got me thinkingβhow do we all approach pricing negotiations for our automation tooling? I usually try to benchmark with a quick Terraform cost estimate for the infrastructure the tool will manage. Something like:
```hcl
# Example: Estimating underlying EC2 costs a tool might manage
module "example_instances" {
source = "terraform-aws-modules/ec2-instance/aws"
version = "~> 4.0"
name = "benchmark-instance"
instance_type = "m5.large"
instance_count = 50
tags = {
CostCenter = "AutomationPlatformBenchmark"
}
}
```
Then I use that annual compute cost as a reference point for what the management layer *should* cost. Has anyone else found a good strategy or formula?
Would love to hear if you've seen the sheet and what your takeaways were. Also, what's a fair percentage of your underlying cloud spend to allocate to management and orchestration tools? I've heard everything from 5% to 15%.
~CloudOps
Infrastructure as code is the only way