![]() |
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
It’s been 20 years since Puppet planted the seeds of today’s Infrastructure as Code (IaC), and it hasn’t gotten any easier — in many ways, it’s more complicated than ever.
The early entrants, Puppet and Chef, gave way to tools like Ansible, Terraform and Pulumi, which brought new capabilities for infrastructure provisioning. Then cloud computing emerged and turned IaC into a fundamental software development practice. Now, we have OpenTofu stepping in to fill Terraform’s no-longer-open-source shoes, and GitOps integrating IaC with version control.
Despite the volatility, organizations clearly understand the value of IaC. According to Firefly’s 2025 State of IaC report, the vast majority of organizations — 89% — are using IaC, but only about 6% have fully codified their cloud. The result is severe complexity, characterized by inconsistency, poor stability, tooling fragmentation and slow development pipelines.
So where does this leave us? According to Firefly’s research, presented in a recent webinar with The New Stack, the 2025 State of IaC, we’re spiraling into self-inflicted complexity: adding more clouds, more tools and more automation — and then doing it all over again when things become unmanageable.
👁 Firefly webinar on demand image
During our webinar, Inside the 2025 State of IaC: Tools, Trends, and Tactical Solutions, Ido Neeman, CEO and co-founder of Firefly, and Chris Pirillo, TNS host, dove into the reasons IaC is so difficult but doesn’t have to be. They reviewed findings — published and unpublished — from the State of IaC survey, and discussed what they indicate about the challenges and opportunities ahead.
During their wide-ranging conversation, Ido and Chris discussed: