So far, speaking from experience, we saved loads of money DIY’ing it, even when deploying to the cloud, and we saved loads of time, in the long run.

First, I’m glad its working for you up to now. I’ve been in similar orgs. It works great, until it doesn’t. Have you had an production outage yet from a datacenter or hardware failure yet?

Should I ask home much did your Broadcom licensing renewal cost you this year?

If you hire talented workers, you save money and time, by DIYing the approach, as long as it’s done in a sane, and controlled manner.

Talented workers that know the systems are great, and if you’ve built your own systems and processes finely tuned to your specific applications performance needs and profiles, it also means you’ve got a highly specialized infrastructure and app stack. You’ve possibly built yourself a scaling problem because the skill needed to understand and maintain your well performing one-off solution isn’t ubiquitous. As your organization’s needs scale it will be tied directly to the additional limited specialized and expensive staff needed. Again, this may not be an issue with your org today, but it may not have hit this need yet. This is the “Only time will tell” component that is so important. As in, your sample size may not be large enough to know if your org made the right decision or not yet.