A managed database vendor changed its pricing model again and called it 'simplification'

A managed database vendor rolled out a new pricing tier structure this week, announced under a blog post titled, I am not kidding, “Simplifying pricing for our customers.” Read the actual change: they collapsed four billing dimensions into two, and the two that remain both scale worse for the exact workload profile most of their mid-market customers run.

I’ve been doing this long enough to have a Pavlovian response to the word “simplify” in a pricing announcement. It has never once, in my experience, meant the bill goes down. It means the bill becomes harder to predict in a direction that favors the vendor, wrapped in language that makes complaining about it feel like you’re the one who doesn’t get it.

The actual pattern, every time

1. Usage-based pricing launches generous, because generous pricing is how you win the initial adoption. Nobody churns off a database at month three over pricing.
2. Once migration cost is sufficiently painful — and for a database, it’s always sufficiently painful, that’s the whole reason you picked a managed one — the pricing model “simplifies.”
3. The new model is announced with a calculator that makes your specific workload look fine, because the calculator’s default assumptions never match your specific workload.
4. Six months later finance asks why the database line item doubled and nobody remembers agreeing to that.

This isn’t a conspiracy, it’s just how lock-in economics work once the switching cost is real. You don’t need bad faith from the vendor, you just need customers who can’t easily leave, and a database is the single hardest thing in most stacks to easily leave.

What actually protects you

Not “avoid managed databases,” they solve real problems and I use several. What protects you is knowing your exit cost before you need it, not discovering it during a pricing dispute:

• Keep a documented, tested path to export your full dataset in a portable format. Test it quarterly, not “whenever we get around to it.”
• Track your actual usage against the vendor’s billing dimensions yourself, independently, so a pricing change is a five-minute recalculation instead of a fire drill.
• Read every pricing announcement assuming it’s adversarial until proven otherwise. Not because the vendor is evil — because “simplification” is doing a lot of load-bearing work in that sentence, and load-bearing words deserve scrutiny.

Every vendor eventually optimizes for the customers who can’t leave over the customers who can. The only defense is staying in the second group.