Skip to main content

FluxVM — Product Positioning

One control plane. Four backends. A real API.

FluxVM is a Rust-native control plane for creating and managing secure, isolated virtual machines on Linux via Firecracker, Cloud Hypervisor, QEMU/KVM, or the in-tree FluxVM hypervisor. Short-lived and disposable workloads (TTL cleanup, cheap CoW clones) are a first-class use of FluxVM — not the product’s identity.

It is not positioned as "the VM engine under Fabric" first and a standalone product second — that gets the emphasis backwards. FluxVM is a complete, independently useful control plane on its own. It's also the VM engine other Zyvor products (Fabric, Ragnarok) build on, the same way a database is both usable directly and the thing an ORM sits on top of.

Part of the Zyvor product family from Zyvor AI Labs.


Elevator pitch​

FluxVM manages secure, isolated virtual machines — via Firecracker, Cloud Hypervisor, QEMU/KVM, or its own in-tree hypervisor — from one Rust-native control plane with a real REST API. Run it standalone, or as the VM engine under another Zyvor product; it's the same binary and the same API either way. Use TTL and CoW when you want disposable compute; leave them off for longer-lived guests.

The strongest concrete hook is a real REST API and a JSON VM spec on every backend. Everything else in this doc builds on that.


Who this is for​

PersonaRoleWhat they care aboutWhere FluxVM fits
CI/platform engineer building ephemeral infraNeeds VM-per-job isolation that actually cleans upTTL-guaranteed cleanup, no network path for untrusted code, cheap CoW cloningOptional ttl_seconds, network.mode: "none" + vsock exec, qcow2 overlays — see Use cases
Kubernetes platform engineer wanting VMsRuns a K8s cluster, needs real VMs for some workloadsA lightweight path that still feels Kubernetes-nativeDisposableVm CRD + fluxvm-kube operator, or fluxvm-microvm for scheduler-driven placement — see docs/microvm.md
AI-agent builder who wants a disposable machine per task, on a MacRuns coding agents (Claude Code, Cursor, Codex) locally or on a few MacsCode and prompts that never leave the machine, a clean VM per attempt, trying several fixes in parallelfluxctl mcp install plus offline sandboxes that fork into running copies in about 4 s (measured on an M4 mini; agent-sandbox-demo)
Mac team lead with a shelf of Mac minis and StudiosRuns CI and shared dev machinesOne API, tenants and leases, quotas, volumes, SSH without exposing the Macs, graphsThe fleet platform (mac-cloud-tenancy.md); tested against simulated Macs, not yet a real multi-Mac fleet
Economic buyer evaluating build-or-adopt for a host-local VM layerDeciding whether to build this in-house or adopt FluxVMWhether the maturity level matches the use case, whether it's a maintained project or a dead endZyvor Production License v1.0 (non-production use permitted; commercial license for production), actively developed, but read the maturity caveat honestly before committing — this is not yet a finished multi-tenant security boundary

The economic-buyer row matters here specifically because FluxVM is explicit about not being finished in one dimension (multi-tenant security hardening) while being solid in others (core VM lifecycle, Network Fabric GA, k3s-verified Kubernetes operator). A buyer should read the maturity caveat as the actual scoping tool, not a boilerplate disclaimer.


What FluxVM Is​

DimensionPositioning
CategoryHost-local VM control plane
AnalogyA host-local VM engine with a REST API and JSON specs — also strong for short-lived VMs when you opt into TTL/CoW
Runtimefluxvm CLI + fluxctl serve daemon — one binary, direct netlink networking
ScopeVM lifecycle across 4 backends, image build/catalog, per-VM networking (incl. eBPF dataplane), Kubernetes CRDs, multi-host fleets
InterfacesCLI (fluxvm), REST API, Kubernetes CRDs (DisposableVm, MicroVM)

Standalone vs. via another Zyvor product​

FluxVM is designed to be adopted standalone first. The two other Zyvor products that use it as their VM engine — zyvor-fabric and Ragnarok — are optional orchestration/UX layers on top of the same REST API, not a requirement for using FluxVM.

Run FluxVM directlyRun it via FabricRun it via Ragnarok
What you getfluxvm CLI + REST API, full control over VM JSON specsFabric's CLI/Web/K8s-operator/Terraform UX, plus auth/RBAC/network-policy layered on topAI-assisted VM management, OIDC/SSO, RBAC via Ragnarok's FluxVM Hub
When to pick itYou want the smallest possible footprint, or you're building your own orchestration on topYou want a private-cloud control plane with multi-tenant auth and a web consoleYou want DisposableVm CRs created and managed through an AI-assisted hub with enterprise SSO
Does it require the others?No — this is the base layerFabric talks to a local fluxctl serve over REST; it doesn't fork or vendor FluxVMRagnarok creates DisposableVm CRs against fluxvm-kube; same relationship

If you're not sure which layer you need: start with FluxVM directly. Both Fabric and Ragnarok are additive — adopting FluxVM standalone never locks you out of adding either later, since they talk to the same unmodified API.


When to look elsewhere​

  • You need a finished multi-tenant security boundary today — see the maturity caveat.
  • You need full CDI or non-QEMU Secure Containers VMM parity — Secure Containers is GA with documented scope boundaries; see secure-containers.md.
  • You need published boot-latency/density/throughput numbers for capacity planning — measure with capability-figures.md / benches; don't cite unpublished SPECs as product claims.

Messaging Guidelines​

Say​

  • "FluxVM — Rust-native VM control plane, standalone or as another product's VM backend"
  • "A host-local VM control plane with a real REST API"
  • "A throwaway computer for every agent task on your Mac: offline by default, forked into running copies in seconds" (cite the measured demo and its caveats)
  • "The same binary and API whether you run it directly or through Fabric/Ragnarok"
  • Supports disposable / short-lived workloads via TTL and CoW when you need them
  • "Firecracker isolation layering for production hosts; density figures optional for microVM packing" (capability-figures.md)

Avoid​

  • Leading with "Disposable Compute Engine" or defining FluxVM as disposable-only — disposable is a use pattern, not the category
  • Leading with "FluxVM is the engine under Fabric" — that undersells it as standalone-adoptable
  • Claiming the Mac cloud platform is proven at fleet scale: it was run against simulated Macs, not several real ones
  • Advertising self-service sign-up or Stripe billing as proven: both are off by default, sign-up confirms the address through the operator's mail webhook (not run against a real mail service), and Stripe has only been run against a mock
  • Citing unpublished boot-latency, density, or throughput numbers — measure first; see capability-figures.md
  • Softening the MVP/multi-tenant-security-boundary caveat to sound more finished than it is
  • Claiming unrestricted hostPath for Secure Containers — GA with documented scope boundaries

License​

Zyvor Production License v1.0 (SPDX LicenseRef-Zyvor-Production-1.0), applied to the entire repository: non-production use is free, production use requires a commercial license (sales@zyvor.dev). See README.md — License and NOTICE. Fabric and Ragnarok, which use FluxVM as their engine, are separate products with their own licensing.