Preview · Brainstorm / VM

The control plane IS the AI.

BrainstormVM IS the hypervisor, storage engine, network fabric, and reasoning brain — not a management wrapper over someone else's HCI. Cloud Hypervisor + Firecracker + LINSTOR + nftables + WireGuard under a Go control plane that observes, decides, migrates, and recovers.

Open vm.brainstorm.co See the substrate →

14:23:41.082placementPLACE_VM · tnt-a/web-01 → host-3 · score=0.91· evd:8f3a2c…14:23:38.451migrateMIGRATE · tnt-c/db-06 → host-5 (drain host-2)· evd:b7c1d9…14:23:35.108capacityREBALANCE · pool=workers · 78% → 62%· evd:4d8f17…14:23:32.762driftNFT_DRIFT · tnt-b · rule diff detected → auto-reconcile· evd:a52b1e…14:23:30.224snapshotSNAPSHOT · tnt-a/cache-03 · 12.4 GB · sha=c7…· evd:c419fa…14:23:27.984recoveryRECOVER · tnt-c/mq-08 · OOM kill → restart from snapshot· evd:e2b48d…14:23:25.451policyPOLICY_GATE · CHANGE_NETWORK_CIDR · operator review· evd:5740c1…14:23:22.108placementPLACE_FC · tnt-d/batch-09 · cold-start 412ms· evd:9a8d3f…14:23:18.762capacityAUTOSCALE · pool=edge · +2 replicas (CPU 84%)· evd:31b274…14:23:15.451driftIOMMU_GROUP · host-1 · PCI bridge 06:00.0 changed· evd:7e51c2…14:23:41.082placementPLACE_VM · tnt-a/web-01 → host-3 · score=0.91· evd:8f3a2c…14:23:38.451migrateMIGRATE · tnt-c/db-06 → host-5 (drain host-2)· evd:b7c1d9…14:23:35.108capacityREBALANCE · pool=workers · 78% → 62%· evd:4d8f17…14:23:32.762driftNFT_DRIFT · tnt-b · rule diff detected → auto-reconcile· evd:a52b1e…14:23:30.224snapshotSNAPSHOT · tnt-a/cache-03 · 12.4 GB · sha=c7…· evd:c419fa…14:23:27.984recoveryRECOVER · tnt-c/mq-08 · OOM kill → restart from snapshot· evd:e2b48d…14:23:25.451policyPOLICY_GATE · CHANGE_NETWORK_CIDR · operator review· evd:5740c1…14:23:22.108placementPLACE_FC · tnt-d/batch-09 · cold-start 412ms· evd:9a8d3f…14:23:18.762capacityAUTOSCALE · pool=edge · +2 replicas (CPU 84%)· evd:31b274…14:23:15.451driftIOMMU_GROUP · host-1 · PCI bridge 06:00.0 changed· evd:7e51c2…

/ 01 — the stack

From bare metal to tenant microVM.

Bare-metal host runs the Linux kernel with KVM + IOMMU groups + vfio passthrough. Cloud Hypervisor spawns full-VM workloads; Firecracker spawns microVMs for ephemeral and edge processes. Per-tenant isolation enforced at the kernel boundary.

Tenant VMs heartbeat on staggered intervals. Drift, OOM, or scheduling pressure surfaces as a signal into the OODA loop above this layer.

control plane

CHV

full-VM hypervisor

microVM kernel

LINSTOR

storage replication

nftables

tenant overlay

WireGuard

cross-node mesh

OODA

control loop

<1s

microVM boot

/ 02 — storage

LINSTOR + DRBD. Replication visible to the brain.

Synchronous replication across three nodes with quorum 2/3. Dirty-block state surfaces as live telemetry to the control plane — placement decisions account for storage proximity. CSI driver exposes volumes to Kubernetes workloads riding on top.

/ 03 — network

Tenant overlays. Policy at the host kernel.

Per-tenant network isolation enforced by nftables in the host kernel — not in a vendor-proprietary SDN. Cross-node tenant traffic rides a WireGuard mesh. Rule changes are ChangeSets; drift triggers auto-reconciliation.

/ 04 — passthrough

IOMMU-aware device routing.

Per-host IOMMU groups enumerated continuously. GPU, NIC, NVMe devices in passthrough-ready groups are scheduled per-tenant by the control plane. AWS c5.metal nodes show ~200 groups; Hetzner AX hosts vary by hardware revision.

/ IOMMU groups · host-1

8 groups · 10 devices

group 00

00:00.0Host bridge

group 01

01:00.0NVMe SSD · Samsung PM9A3

01:00.1NVMe SSD · namespace 2

group 02

03:00.0NIC · Mellanox CX-6 DX→ tnt-a

group 03

04:00.0NIC · Mellanox CX-6 DX→ tnt-c

group 04

06:00.0GPU · NVIDIA A10 24GB

group 05

07:00.0GPU · NVIDIA A10 24GB→ tnt-b

group 06

0a:00.0SATA controller

0a:00.1USB 3.0 hub

group 07

0d:00.0NIC · Intel X710

/ 05 — migration

Move gradually.

Connectors for Proxmox / VMware / Nutanix let you move workloads onto BrainstormVM gradually. The destination is a new substrate, not a re-skin of the old one — but the path supports cross-stack coexistence during transition.

/ source	VM import	Storage migration	Network mapping	Snapshot lift	Live migrate
Proxmox	✓Yes	✓Yes	◐Partial	✓Yes	◐Partial
VMware	✓Yes	✓Yes	✓Yes	✓Yes	✓Yes
Nutanix	✓Yes	◐Partial	◐Partial	✓Yes	·No

// Partial = capability available but with operator review per migration. v0.12 closes Nutanix live-migrate via incremental snapshot bridging.

/ 06 — vs traditional HCI

Different substrate. Not different UI.

Control plane

Traditional HCI

Web UI + REST API on top of vendor automation engine.

Brainstorm VM

Go service running OODA loop on every signal. Placement, migration, recovery are evidence-chained ChangeSets, not opaque automation.

Storage

Traditional HCI

Vendor SAN or per-vendor HCI block. Replication policy hidden.

Brainstorm VM

LINSTOR + DRBD with brain-visible replication state. ZFS substrate planned for Phase 2.

Network

Traditional HCI

Vendor overlay (NSX, AHV) with proprietary policy engine.

Brainstorm VM

nftables at the host kernel + WireGuard mesh. Policy is code; rule diff surfaces as evidence record.

Migration path

Traditional HCI

Rip-and-replace via vendor migration tooling.

Brainstorm VM

Connectors for Proxmox / VMware / Nutanix run inside the OODA loop. Move VMs gradually; cross-stack workloads coexist during transition.

Open the control plane.

vm.brainstorm.co serves the operator console. Preview access is invite-only during the access ramp.

vm.brainstorm.co Request access