Building a Firecracker VM Orchestrator in Go — Part 1: Provider Interfaces

Building a Firecracker VM Orchestrator in Go — Part 1: Provider Interfaces Introduction I'm building Flames, an open-source control plane for managing microVMs powered by Firecracker and Jailer. The goal is a straightforward API to spin up, orchestrate, and tear down lightweight VMs — the kind of ephemeral, hardware-isolated environments that are becoming critical infrastructure. Especially in the AI ecosystem, where you're running untrusted code, agent workflows, or sandboxed execution, container-level isolation isn't enough. You need real VM boundaries with Jailer-enforced security, and you need it to be fast and programmable. That's what Flames is for. I've been coding with AI agents for a while now, but what's different this time is that I'm using ContextPin as my main AI coding workspace — organizing specs, context, and decisions in one place so the AI always has what it needs. Spec-Driven Development, essentially. I'm documenting the whole journey