💡 Need help deploying or extending this? → hello@volantvm.com

---

Volant

The modular microVM orchestration engine.

Volant lets you spin up fully isolated microVMs as easily as running a container — with real kernels, VFIO passthrough, and cloud-init built in.

Volant turns microVMs into a first-class runtime surface. The project ships a control plane, CLI, and agent that speak a common plugin manifest so teams can run secure, stateful workloads without stitching together networking, scheduling, and lifecycle plumbing themselves.

Runtime-specific behavior lives in signed manifests and their associated artifacts. The core engine stays lean while plugin authors ship the kernels/initramfs overlays and workload processes their runtime requires. Operators decide which manifests to install and must reference one whenever a VM is created.

Together with fledge — the artifact builder — Volant provides a complete solution for building and deploying microVM’s with custom applications embedded in initramfs, or with the regular OCI images we are familiar with.

Cloud-init support makes Volant ideal for dev sandboxes, while VFIO passthrough allows for isolation of GPU and AI workloads.

Batteries Included By Default

Volant ships with sensible defaults out of the box, lowering the barrier to entry while keeping full configurability for power users

However, Volant is built to be modular, scriptable and configurable beyond those defaults, and advanced users can customize it to their own needs.

For instance, the Kestrel agent acts as a robust PID1 and is responsible for setting up the guest environment in multiple scenarios, and also acts as a secure proxy to workloads inside network-isolated VM’s over vsock, providing a frictionless path to maximum isolation.

If you require more fine-grained control, it is possible to override the kernel paths and the fledge artifact builder has configuration settings for using your own init. Refer to the documentation for more details.

---

Overview

Volant provides:

volantd — Control plane (SQLite registry + VM orchestration)

volar — CLI for managing VMs and plugins

kestrel — In-guest agent & init (PID 1)

fledge — Plugin builder (OCI images → bootable artifacts) Two paths, same workflow:

1. Rootfs strategy — Convert OCI images to bootable disk images (Docker compatibility)
2. Initramfs strategy — Build custom appliances from scratch (maximum performance)

---

Quick Start

Spin up your first microVM in under a minute.

---

1. Install the Volant toolchain

# This installs volar (CLI), volantd (control plane), kestrel (guest agent),
# and default kernels to /var/lib/volant/kernel.
# By default, setup creates a bridge (vbr0) at 192.168.127.1/24.

curl -fsSL https://get.volantvm.com | bash

Tip: To inspect or customize network setup later:

sudo volar setup --help

If you prefer to skip automatic setup and handle networking yourself:

curl -fsSL https://get.volantvm.com | bash -s -- --skip-setup

---

2. Install a pre-built plugin

Let’s start with a Caddy initramfs plugin (initramfs-plugin-example)

volar plugins install --manifest \
https://github.com/volantvm/initramfs-plugin-example/releases/latest/download/caddy.json

---

3. Create and run your first VM

volar vms create web --plugin caddy --cpu 2 --memory 512

Check it’s alive:

curl 192.168.127.10
# → Hello from Caddy in a Volant microVM! 🚀

---

4. Try a Docker-based workload (oci-plugin-example)

This example runs NGINX directly from the official Docker image:

volar plugins install --manifest \
https://github.com/volantvm/oci-plugin-example/releases/latest/download/nginx.json

volar vms create my-nginx --plugin nginx --cpu 1 --memory 1024
curl http://192.168.127.11

---

5. Scale declaratively (Kubernetes-style)

cat > web-config.json <<'EOF'
{
"plugin": "caddy",
"resources": {
"cpu_cores": 2,
"memory_mb": 512
}
}
EOF

volar deployments create web-cluster \
--config web-config.json \
--replicas 5

Result: 5 isolated microVMs, each with its own kernel, IP, and lifecycle management.

---

Done — you’ve just deployed a replicated microVM cluster with real kernel isolation, no YAMLs, and zero boilerplate.

Build Your Own Plugin

Use fledge to build custom plugins from OCI images or static binaries.

Examples:

• initramfs-plugin-example — Caddy web server (fast boot, minimal size)
• oci-plugin-example — NGINX from Docker image (Docker compatibility)

---

Why Volant?

Feature	Containers	Volant microVMs
Isolation	Kernel shared	Hardware-level (dedicated kernel)
Boot time	~1s	50-150ms (initramfs) / 2-5s (rootfs)
Image size	80 MB (NGINX)	20 MB (full appliance)
Security	Namespaces	Full VM isolation
Overhead	Shared kernel	~25 MB per VM
Networking	NAT/bridge/overlay	Simple Linux bridge
GPU Passthrough	Limited	Native VFIO for AI/ML

---

Architecture

• Secure multi-tenancy — True hardware isolation
• Edge computing — Minimal footprint, fast boot
• CI/CD — Ephemeral test environments
• Development — Local Kubernetes-style orchestration
• High-density workloads — 50-100 VMs per host
• AI/ML Run machine learning workloads in isolation

---

Documentation

Full documentation: docs.volantvm.com

Quick links:

• Why Volant
• Installation Guide
• Quick Starts · Rootfs
• Networking · Cloud-init · Deployments · GPU
• Plugin Development · Initramfs · OCI Rootfs
• Architecture Overview
• Reference: Manifest · fledge.toml · CLI
• Contributing · Security

---

Roadmap

See ROADMAP.md for the full vision.

2025 Q3-Q4: VFIO GPU passthrough — Native GPU support for AI/ML workloads

• 2025 Q4: PaaS mode — serverless-like workloads, boot from snapshot
• 2025 Q4: Multi-node clustering support

---

Community

• GitHub: github.com/volantvm/volant
• Discord: (coming soon)
• Email: hello@volantvm.com Contributing: See contributing

---

License

Business Source License 1.1 — free for personal, educational, and internal use. Commercial hosting or resale requires a license from HYPR PTE. LTD. Converts to Apache 2.0 on October 4, 2029.

See LICENSE for full terms.

---

Volant — Designed for stealth, speed, and scale.

---

© 2025 HYPR PTE. LTD.