AI-Native Infrastructure Engineering
AI assists. A human signs. The ledger remembers.
Adds a primary Postgres instance with a read replica in a second availability zone, plus a settlement queue holding four days of messages. The existing security group gains one ingress rule scoped to the new database, so nothing becomes publicly reachable. Both instances sit inside the existing VPC.
From intent to signed reality
Each step leaves a record. Months later you can walk any resource back through all four and see what happened, and who decided it.
Author
Write it in Go, TypeScript or Python, or describe it to an assistant. The SDK describes infrastructure and never executes anything.
Plan
Resolved against live state into a typed, hashed proposal. Every assumption an assistant made is listed for you to read.
Accept
One signature, bound to that exact hash. Nothing can change between review and apply, and there is no path around this step.
Ship
The only command that reaches a provider. It applies what was signed, then appends the result to the ledger.
No state file. An append-only record.
Current truth is folded from the record rather than stored, so there is nothing to lock, corrupt or lose. Each entry names its parent, so history cannot be quietly rewritten.
vpc created
signed by roozbeh · 12 Aug
primary database
signed by roozbeh · 14 Aug
read replica, queue
awaiting signature
Why does this exist
Walk any resource back to the proposal that created it, the intent behind it, and the person who signed it.
What changed underneath
Compare live state against the ledger, and turn any difference into an adoption or revert proposal.
Who set this attribute
Per-attribute provenance: which proposal last set each field, and who signed that one.
Built for assistants, open by construction
An assistant can do the work but never the signing. Providers are generated from each vendor’s published API, so coverage is broad on day one and stays current on its own.
Bring your own model
ubx speaks the Model Context Protocol, so Claude, ChatGPT or any MCP client can read your ledger, explain a resource and draft a blueprint. Eight tools, none of which can ship.
Generated from the vendor’s own API
No hand-written provider to wait on. Schemas come from CloudFormation, OpenAPI, Smithy and Discovery Docs, so coverage tracks the API rather than a maintainer’s backlog.
Ship your first stack
Install ubx, write a stack in the language you already use, and read the proposal before anything reaches a provider.
