← all systems
DevOps / Infra
ROLE // CORE SYSTEMS ENGINEER

Fleetform

Infrastructure as code with a memory-safe core and a live graph.

Rust coreGo/Fiber UIpetgraphHCLS3/Consul state
the problem

IaC planners are powerful but opaque. You apply and hope the ordering is right. And the dominant engines run on a garbage-collected runtime where a state-graph bug becomes a footgun.

the solution

A Rust core engine that plans and applies infrastructure with a memory-safe state and dependency model, paired with a Go and Fiber web dashboard that streams plan progress and renders the dependency graph in real time. HCL config, a module system, and multi-backend state across file, S3 and Consul.

the system

The Rust core owns parsing, the resource graph and apply. The Go and Fiber layer serves the dashboard and pushes live updates over WebSocket. Proto definitions bridge the two.

the hard part

The heart of the planner is a resource dependency DAG with topological sort via petgraph toposort and cycle detection, so apply order is provably correct and cycles fail loudly instead of corrupting state.

why this stack

Rust for the safety-critical graph and state engine where a bug means broken infrastructure, and Go with Fiber for the real-time web layer where iteration speed matters.

the innovation

A live dependency-graph dashboard over a compiled, memory-safe core. An IaC tool that shows you the shape of your infrastructure as it plans.

the potential

An open-source IaC alternative for teams that want safety and visibility, not just parity.

next system
Cowri