Terraform challenger Formae expands to more clouds

Late last year, startup Platform Engineering Labs made waves in the world of Infrastructure as Code (IaC) by introducing a new IaC platform, called Formae, available initially on Amazon Web Services.

This week, Platform Engineering Labs‘ platform gets (beta) support from additional cloud platforms, including Google Cloud Platform, Microsoft Azure, Oracle Cloud Infrastructure, and OVHcloud.

The company has also released new AI-enhanced software for managing infrastructure tooling, called the Platform for Infrastructure Builders.

“This release is for and about infrastructure builders,” says Pavlo Baron, co-founder and CEO of Platform Engineering Labs, in a statement. “From here forward, you don’t need to wait on us or anyone else. Build for your own infrastructure. Launch fast. Iterate fast. Extend fast. Do it hands-on or with help from your Al agents.”

The company is pitching the platform for organizations that may have some components managed by IaC but want to expand operations to older, legacy resources that may have been previously thought too ornery to be managed under IaC.

Schema-safe change management

The new platform, with the accompanying software development kit (SDK), will allow users to extend their infrastructure with new components, offering schema safety and an easy-to-understand plug-in interface.

“Engineers can now use AI agents to quickly produce and modify plugins that are reliable by design,” says Zachary Schneider, co-founder and CTO of Platform Engineering Labs, in a statement.

The Formae software was built to automatically discover and codify system resources and system changes into a single unified source of truth.

The founders claim that this approach offers superior state management and easier migration paths than the industry-leading IaC solution, HashiCorp’s Terraform.

Infrastructure as Code

Infrastructure as Code is the practice of saving your system’s configuration in a file, usually using YAML or JSON, which IaC orchestrators then use as an instruction set to roll out infrastructure.

The advantages IaC promises are automated deployments — a real time saver — and a guard against system drift, which is when systems fall out of alignment from their desired state (usually due to manual intervention).

Yet after everything is set up once, Day 2 operations with IaC can be a headache, Baron contended in an earlier interview with The New Stack. IaC files are brittle things. They quickly get complex and difficult to understand, are easy to corrupt with shadow IT work, and are easy to make mistakes with. They offer no guidance as to whether the values they hold are even correct.

Within the Formae environ, an individual IT resource is extracted into a versioned, declarative code artifact called a “forma” (which is the Latin singular for “form”) that can then be programmed against.

Unlike Terraform or Pulumi, state management in Formae is handled not by the clients themselves, but by agents, to guard against system drift. Changes are made in the same way security patches are rolled out, minimizing the blast radius of each update.

The code is written in an unusual language, Apple’s Pkl, which that company developed in-house to manage its own system deployments.

Pkl is different from JSON and YAML in that it forces users to develop a schema for each type of resource, along with a type annotation. With type annotation, the type values — and sometimes even a range of permissible values themselves — are already established for the variable itself. So fewer typos can sneak in and disrupt the operations.

The open source version of Formae is available today on GitHub.