Vibeleaderboard
Index / tool
Visit github.com
Category
Developer Tools
Rank

Previous survey · No. 849 ·

Pricing
Open Source
Type
TOOL
Use case
Deployment & Operations
Interfaces
Client SDK
Latest release
v1.35.5
Date

About

A portable, self contained virtual machine for shipping software with isolation by default. It is a Rust project built on libkrun, with SDKs, packaging and deployment paths, so a workload runs in a lightweight VM rather than a container.

What it does

smolvm runs each program inside its own small virtual machine with a separate Linux kernel, booted from an ordinary container image pulled from Docker Hub or any other registry. A running machine can be saved mid-execution, copied into live branches, or packed into one file that starts as a standalone executable. It works as a command-line tool, as a library embedded in Node, Python, Rust or Go programs with no background daemon, and as an HTTP API server. Underneath, the open-source libkrun monitor drives the native hypervisor on macOS, Linux and Windows.

Why it's ranked here

The pitch to agent builders is hardware isolation at close to container cost, and the repository backs it with specifics. Networking is off by default, outbound traffic can be pinned to named hosts, and a credential can be substituted at the network edge so the guest only ever sees a placeholder. Apache 2.0, written in Rust, with installers for macOS, Linux and Windows and SDKs in four languages. The project's own comparison table lists it as the only option against Firecracker, Kata, QEMU and Colima with both an embeddable SDK and a portable machine file. Its security notes are candid about the gaps, unsigned releases included.

What's good

Checkpoints capture memory, CPU state and disks, and one taken on an Apple Silicon Mac resumes on arm64 Linux. Memory is elastic through a balloon device, so the default eight gigabytes is a ceiling rather than a commitment. A Smolfile declares image, ports, mounts, egress rules and secrets in one checked-in file and rejects unknown keys, so a typo fails at creation instead of being silently ignored. On Linux the process that boots each VM is confined with Landlock, plus seccomp system-call filtering on x86_64. The limitations page names exact error messages and the fix for each.

Tradeoffs

The security model states that releases are not signed, carry no provenance attestation, and that the installer proceeds when the checksum file cannot be downloaded. The tool runs with the invoking user's permissions, so hostile local co-tenants need separate accounts around it. GPU acceleration is unavailable on Windows, and CUDA remoting isolates only at the process level, which the docs say is not a multi-tenant boundary. The default network backend exposes no real interface, so ping fails while HTTP works. Intel Macs get no release build. S3 mounts drop symlinks, permissions and timestamps, and renames there are not atomic.

How to use it well

Best fit: running code an agent wrote, or a dependency you do not trust, on a laptop or your own servers, with egress allowlisted and secrets passed as placeholders. Branching suits agents that explore several approaches from one starting state. Keep mounts narrow, since every folder, open port and forwarded SSH agent becomes something the workload can use. Pick a glibc image if you need CUDA. It is not a hardened multi-user control plane, and the hosted smol cloud's tenant isolation is outside what this repository documents. Check release downloads against the published checksums yourself.

Technical notes+

Cargo.toml declares a workspace of seventeen member crates beside the root (checkpoint, agent, network, credentials, pack, registry, s3fs, smolfile and a family of CUDA shims) and builds one smolvm binary plus a library. libkrun is loaded at runtime through libloading rather than linked; the HTTP API uses axum with utoipa for OpenAPI and axum-server over rustls for mTLS on the fleet serve API, with x509-parser reading the client certificate CN; rusqlite is pulled in with its bundled SQLite. seccompiler and landlock are Linux-only target dependencies, seccomp further gated to x86_64. src/vm/mod.rs defines the VmHandle trait (id, state, wait, stop, kill) and a VmBackend trait whose default_backend returns libkrun on both macOS and Linux. src/cli/mod.rs registers modules for machine, pack, pack_run, serve, serve_tls and smolfile. docs/gpu.md describes two guest shims: one replacing libcuda for the Driver API and one replacing libcudart that lowers Runtime API calls to the Driver API and remotes them over vsock, executing async calls synchronously host-side. docs/security-model.md places the host user, hypervisor, libkrun and smolvm in the trusted computing base.

Observed

License
Apache-2.0
Language
Rust, Cargo workspace
Interfaces
CLI, embeddable SDKs (Node/TypeScript, Python, Rust, Go), HTTP API with OpenAPI docs
Install surface
Homebrew tap, curl install script, Windows release zip; SDKs on npm, PyPI, crates.io
Platform support
macOS Apple Silicon (11+), Linux x86_64 and aarch64 with KVM, Windows x86_64 with Windows Hypervisor Platform; no Intel Mac release build
Virtualization layer
libkrun VMM, libkrunfw guest kernel, OCI images
Release signing
SHA-256 checksums published; releases not signed, no provenance attestations (docs/security-model.md)
Default resources
4 vCPUs, 8 GiB RAM, memory elastic via virtio balloon

Read from README.md, Cargo.toml, LICENSE, docs/security-model.md, docs/limitations.md, docs/smolfile.md, src/vm/mod.rs, src/cli/mod.rs, docs/gpu.md.

Intel on smolvm

More in Intel

Tags

virtualizationsandboxrustisolationopen-source

Tech Stack

Rust

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.