How xiisuma/tinyvmos works
TinyVMOS turns a physical computer into a host for isolated, single-purpose micro-VMs, managed through a central control plane. The documented flow is host installation and hardware detection, then Go control-plane management through a replaceable Firecracker VMM, with service images running in micro-VMs. CLI, web, and mobile interfaces are documented product surfaces. The tree and README establish these capabilities, but no implementation excerpts were available, so uncertain call wiring is omitted.
Main entry points: api REST and WebSocket API · controlplane Go control plane · installer Host installer · os Buildroot host OS
Components 17
Host platform
- Hardware detection
os/hardware-detect - Host installer
os/installer - Buildroot host OS
os - Linux KVM
- Zone networking
os
Control plane
- Go control plane
controlplane - REST and WebSocket API
controlplane/api - VMM interface
controlplane
User interfaces
- CLI client
cli - Web interface
web - Mobile app
mobile
VM workloads
- Service image catalog
images - Apache guest image
images/web-apache - Service micro-VMs
Other components
- Operator
- Physical computer
- Firecracker
Connections 18
- Operator → Host installer: installs host
- Physical computer → Hardware detection: detects hardware
- Host installer → Buildroot host OS: installs
- Operator → CLI client: manages via
- Operator → Web interface: manages via
- Operator → Mobile app: manages via
- CLI client → REST and WebSocket API: uses API
- Web interface → REST and WebSocket API: uses API
- Mobile app → REST and WebSocket API: uses API
- Go control plane → REST and WebSocket API: provides API
- Go control plane → VMM interface: manages VMs
- VMM interface → Firecracker: controls
- Buildroot host OS → Linux KVM: provides
- Firecracker → Linux KVM: uses
- Service image catalog → Apache guest image: includes image
- Apache guest image → Service micro-VMs: provides guest image
- Firecracker → Service micro-VMs: runs
- Zone networking → Service micro-VMs: connects zones