microvm
AerolVM is a self-hosted platform for creating isolated Docker-backed sandboxes on a single Linux host, or running it as a managed multi-tenant service.
Ficha actualizada 22 sept 2026, 18:34 · upstream 22 sept 2026, 17:12 · release v0.5.5
Qué es microvm
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
AerolVM provides a complete surface for building sandbox-backed products and agent workflows. Each sandbox is a fully isolated compute unit with its own filesystem, network stack, and allocated resources. It ships as a single Go binary backed by Caddy for TLS routing and SQLite for state management, requiring no external dependencies. The platform supports multiple runtimes including OCI containers (containerd), gVisor, Firecracker, WASM, and V8 isolate.
- Running untrusted code safely in isolated environments
- AI agent pipelines with ephemeral workloads
- CI/CD for containerized applications
- Ephemeral compute for microservices
- Multi-tenant SaaS infrastructure on a single host
- Secure sandboxing of sensitive data
- Self-hosted with a single Go binary requiring no external dependencies
- Supports multiple runtimes including OCI, gVisor, Firecracker, WASM, and V8 isolate
- 4ms server-side create latency for Isolate runtime on t3.medium
- TCP + TLS port routing via Caddy with per-sandbox egress control
- Unlimited sandbox lifetime with Raft-coordinated HA cluster support
- Per-sandbox resource limits and GPU support available
- Self-hosted deployments require manual configuration of Caddy, runtimes, and SQLite storage
- Firecracker cold builds can take longer than warm pools (~34ms vs ~22ms)
- gVisor requires user-space kernel boot which adds latency compared to OCI containers
- WASM runtime is host-mediated and does not provide full isolation from the host OS
- Single-writer SQLite WAL mode means concurrent reads can block writes during snapshot operations
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy AerolVM by installing the single Go binary `sandboxd` with optional dependencies (containerd, gVisor, Firecracker). Use Caddy for TLS routing and a separate admin API endpoint. For multi-host deployments, configure Raft cluster membership using SWIM gossip protocol. Enable WASM or Isolate runtime via environment variables to achieve sub-4ms warm create times. External storage is supported via S3, NFS, SSHFS, or rclone.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.