This article is based on reporting originally published on TechTarget (techtarget.com) in June 2018, covering Puppet’s acquisition of Reflect and the competitive configuration management landscape at that time.
Why Puppet Bought Reflect
Puppet’s acquisition of Reflect, a data visualization startup based in Portland, Oregon, was a signal that the company recognized a fundamental shift underway in DevOps tooling. As containers increasingly pull engineering attention away from traditional configuration management, Puppet needed to expand its portfolio and provide greater visibility into complex, distributed infrastructure.
Data visualization — the ability to represent system state and pipeline health in an easily understood graphical form — has moved from a convenience to a necessity. As Charles Betz, analyst at Forrester Research, noted at the time: “The ability to paint pretty pictures [of data] is not just a ‘nice to have’ feature. It’s important as microservices become more difficult to visualize and manage.”
Puppet already held substantial configuration data assets within Puppet Enterprise’s core data repository. The strategic logic for Reflect was to surface that data in meaningful ways for operators and engineers managing increasingly heterogeneous environments.
The Integration Gap
At the time of the acquisition, Puppet had not specified how Reflect’s visualization capabilities would integrate with its existing product lineup — Puppet Enterprise, Puppet Discovery, and its continuous delivery tooling. Competitors such as Electric Cloud and XebiaLabs had already begun adding monitoring and pipeline visualization features to illustrate pipeline health, establishing a pattern Puppet would likely need to follow.
One gap analysts highlighted was the absence of a data warehouse or analytics layer to feed Reflect’s visual tooling. Puppet CEO Sanjay Mirchandani declined to confirm at the time whether this layer would be filled through another acquisition or internal development.
Containers and Infrastructure as Code Are Reshaping Configuration Management
The competitive pressure Puppet was responding to is real and structural. Enterprise IT teams increasingly adopt Docker-based, immutable infrastructure deployments, which reduce the need for runtime configuration management tools like Puppet or Chef to manage individual server state.
Ernest Mueller, then director of engineering operations at AlienVault, described the shift plainly: “As we move to Docker and immutable infrastructure deployments, our goal is to cut the lines of Puppet code we use in half. We’re trying to shift configuration management left — adding it at the end just creates problems, because if you try to do the same configuration operation on a thousand different servers, it’s bound to fail on one of them.”
Mueller’s team was evaluating CI/CD processes for infrastructure as code broadly. He found Puppet’s reusable manifests preferable to Chef’s community-maintained cookbooks for day-to-day use, but noted Chef InSpec’s continuous integration-style security and compliance testing as an area of particular interest for infrastructure code validation.
Why Infrastructure CI/CD Is Still Immature
One important nuance Mueller raised is that applying standard application CI/CD practices to infrastructure code is not straightforward. In application unit testing, best practice is to avoid calling live external APIs. But infrastructure code — for example, code that creates an Amazon Machine Image — is inherently dependent on live infrastructure responses. There is no clean equivalent to application unit testing mocks when the artifact being tested is the infrastructure.
As Mueller put it: “The nature of infrastructure as code means there’s no one answer for CI/CD today, and figuring out how to stitch together multiple tools takes a lot of work, without a good reference architecture.”
Puppet’s Continuous Delivery for Puppet Enterprise (released in early 2018 from technology acquired via Distelli) addressed CI/CD for Puppet-managed infrastructure code specifically, but did not at that time extend to other infrastructure-as-code tools such as HashiCorp’s Terraform — a gap noted by practitioners managing polyglot infrastructure automation environments.
Puppet’s Acquisition Strategy Under Mirchandani
Puppet’s response to container-driven disruption under CEO Sanjay Mirchandani, who joined in 2016, was primarily acquisitive. In 2017, Puppet acquired Distelli, a CI/CD and container orchestration vendor. Distelli’s technology was repackaged into Continuous Delivery for Puppet Enterprise and released in early 2018. The Reflect acquisition extended this pattern into the data visualization and observability layer.
As Forrester’s Betz summarized: “Puppet hasn’t had much choice but to develop a strategy that moves into some adjacencies — otherwise Kubernetes is an existential threat.”
A Crowded and Consolidating Market
Puppet’s expanded portfolio competed in a market analysts described as fragmented and under pressure. Beyond direct configuration management rivals like Chef, Puppet contended with Red Hat (Ansible), Docker, HashiCorp, AWS, and Microsoft Azure — all competing for wallet share in infrastructure automation and DevOps tooling.
Forrester estimated the total DevOps tools market at approximately $1 billion at the time — small compared to adjacent markets like application performance monitoring ($2–3 billion) and substantially smaller than IT service management. The relatively modest market size, combined with the number of competing vendors, set the stage for consolidation.
Some former Puppet users had already moved on. Andy Domeier, then director of technology operations at SPS Commerce, who had migrated from Puppet to Red Hat’s Ansible, described his team’s focus as being on tools that integrated natively with Kubernetes — specifically citing Netflix’s Spinnaker for multi-cloud continuous delivery. He acknowledged that Puppet’s Distelli-based CI/CD tooling might appeal to committed Puppet shops, but that the proliferation of available tools made re-evaluation unlikely for teams that had already moved.
Betz’s assessment of the broader market was direct: “It’s a game of musical chairs, and many of those chairs will be suddenly pulled out, especially if the economy even hiccups. There’s no question this market will further consolidate.”
Key Takeaways for DevOps Teams
- Data visualization is becoming infrastructure-critical. As microservices and distributed systems grow, readable dashboards and pipeline visualizations shift from nice-to-have features to operational requirements.
- Configuration management is being pushed left. Immutable infrastructure and container-native deployments reduce the role of runtime configuration management. Teams should evaluate where in the delivery pipeline configuration is applied and whether traditional agents still make sense.
- Infrastructure CI/CD tooling remains immature. No single reference architecture existed in 2018 for testing and deploying infrastructure as code across heterogeneous tool sets. Practitioners should expect to integrate multiple tools.
- Vendor consolidation in DevOps is ongoing. Teams relying on niche DevOps tool vendors should assess vendor financial health and strategic positioning when making long-term toolchain decisions.
- Kubernetes compatibility is a key evaluation criterion. Tools that integrate cleanly with Kubernetes-based workflows have a structural advantage as container orchestration becomes the default deployment target.