What’s Happening
Platform Engineering Labs has released a major update to formae, its open-source Infrastructure-as-Code platform, adding native Kubernetes and Helm integration alongside a new Public Hub for plugin discovery and distribution. The update positions formae as a unified system of record for infrastructure changes across cloud-native environments, including vanilla Kubernetes, EKS, and AKS. It also introduces direct consumption of Terraform `.tfvars` files, lowering the barrier for teams migrating away from or operating alongside Terraform. The platform is available today on GitHub under the FSL license.
The Bigger Picture
The IaC Consolidation Problem Is Real
The timing of this release is not accidental. Platform teams have been accumulating tool sprawl at a rate that is becoming operationally unsustainable. ECI Research’s data reinforces the scope of the problem: according to our analysis, 82.9% of respondents use Azure DevOps for CI/CD pipelines, while CloudFormation adoption stands at 76% and Terraform at 55.5%, highlighting a fragmented Infrastructure-as-Code landscape — one identified as a driver of configuration drift and inconsistent governance across environments. The result is that platform engineers are spending disproportionate time reconciling state rather than shipping infrastructure improvements.
The core architectural bet is that auto-discovery and continuous codification can eliminate this reconciliation burden. Rather than requiring teams to define resources from scratch or migrate existing state, formae reads what’s already running and builds a versioned record around it. That’s a meaningful inversion of how most IaC tools work, and it directly responds to one of the most friction-heavy moments in platform engineering: onboarding existing infrastructure into a new system of record.
What This Means for ITDMs
For IT decision-makers evaluating IaC tooling, the value proposition here is risk reduction at scale. Configuration drift between environments is not a theoretical concern. According to ECI Research, only 55.3% of organizations report complete environment consistency across stage, test, and production environments, and 44.7% acknowledge at least some level of inconsistency. That inconsistency is the root cause of a significant share of post-deployment failures, extended incident resolution times, and the kind of audit findings that slow down cloud governance programs.
formae’s approach of codifying every change regardless of which tool made it could address a real operational gap. The Terraform `.tfvars` compatibility is a pragmatic addition: it tells existing Terraform shops they don’t have to choose between their current configuration investments and a better operational model. That removes one of the most common objections to platform tool transitions, which is sunk cost in existing parameter files and resource configurations.
The FSL license also deserves attention from procurement and legal teams. It is not a standard open-source license, and organizations should understand the commercial use terms before building production dependencies on it. The open-core model can offer genuine value, but ITDMs should validate the licensing terms against their deployment scenarios before committing at scale.
What This Means for Developers and Platform Engineers
The Kubernetes integration is the headline for practitioners, and the framing from Platform Engineering Labs is accurate: Kubernetes was the one remaining gap that prevented formae from being a credible alternative to incumbents across the full cloud-native stack. Supporting vanilla Kubernetes alongside managed flavors like EKS and AKS, with native Helm chart integration, means teams may now centralize the operational surface area they actually care about.
The tool-agnostic versioning model deserves particular attention. The promise that formae will codify changes regardless of which tool made them is architecturally significant. Most IaC platforms create a tight coupling between the tool and the state model, which means any out-of-band change (a manual `kubectl apply`, a direct cloud console edit, a change made by a different team’s automation) breaks state consistency. formae’s auto-discovery approach sidesteps this by treating the infrastructure itself as the source of truth rather than the tool’s state file. Whether that holds up at enterprise scale and across complex RBAC configurations will determine how quickly it gains adoption beyond early adopters.
The Public Hub for plugins is the ecosystem play. The January SDK launch seeded developer investment; the Hub is where that investment becomes discoverable and composable. The integrated build and test environment for plugins is the right call — plugin reliability is one of the most common pain points in extensible IaC platforms, and shipping a verification layer before the ecosystem grows large reduces the trust deficit that typically emerges as plugin catalogs expand.
Looking Ahead
Near-Term Adoption Will Track Platform Engineering Maturity
The organizations most likely to adopt formae in the near term are those actively building or rebuilding their internal developer platform practices rather than those maintaining established Terraform or Pulumi estates. Platform engineering as a discipline is still maturing, and teams standing up new golden paths for infrastructure provisioning have fewer migration constraints. For those teams, formae’s system-of-record model offers a cleaner starting point than inheriting the accumulated complexity of a mature Terraform codebase.
The plugin ecosystem will be the medium-term differentiator. ECI Research has consistently observed that platform consolidation decisions increasingly hinge on ecosystem breadth and integration coverage. The Public Hub gives Platform Engineering Labs a mechanism to grow that breadth through community contributions rather than internal engineering investment alone. The quality gate embedded in the Hub’s build and test environment will determine whether that ecosystem grows fast or fast and unreliable.
The Broader IaC Market Will Feel This
The auto-discovery and continuous codification model formae has introduced is not unique to the company long-term. If it demonstrates value at scale, expect established players to incorporate similar capabilities through acquisition or product roadmap investment. HashiCorp (now under IBM) has the engineering depth to respond, and Pulumi’s architecture is extensible enough to move in this direction. The window for formae to establish category leadership on this model is real, but it’s measured in months, not years.
For platform teams evaluating their IaC strategy over the next 12–18 months, the practical advice is straightforward: run a structured proof of concept against an environment that already has Kubernetes workloads and Terraform-managed resources. The claims around auto-discovery and `.tfvars` compatibility are testable. The results of that test will tell you more than any vendor comparison matrix.
SurfaceGX Launches AI Visibility Repair Platform
Equinix Fabric Geo Zones: Network-Layer Data Sovereignty for Multicloud
formae Adds Kubernetes & Helm: A New IaC System of Record
Why Enterprise AI Data Governance Is the Real Bottleneck | ECI Research
Docker AI Governance: Securing AI Agents at the Runtime Layer
