burner

what's next.

where burner is, what's being built right now, and what's missing. nothing still to come has a date. the later parts are ideas, not promises, and they change as the thing gets used.

v0.1

shipped
v0.1.0
nov 18 2026. burner run, burner shell and burner-tui on linux with kvm. firecracker under the jailer, a uid and cgroup per vm, offline by default, --net web and --net open.
v0.1.1
nov 19 2026. a one-line installer, arm tested on ubuntu 24.04, macs with an M3 or newer through a lima vm, the crates on crates.io, and a round of isolation fixes. releases

v0.2

shipped
macs
nov 19 2026. native on any apple silicon mac, M1 and newer. no linux vm in between: burner boots each vm on hypervisor.framework through libkrun, with a sandboxed network process doing the same blocking linux does.
shell
an outside review of burner shell found 32 bugs, from a guest being able to clear your scrollback to poweroff -f hanging until the time limit. all of them are fixed, along with resize, paste and exit codes. release notes
setup
burner setup checks the guest kernel against a hash built into the binary, not only the release's own checksum file.

v0.3

next
remote
burner -H mini shell starts the vm on another machine over ssh. a host can list a lan address and a tailnet one, and burner uses whichever answers.
log
every connection a vm tried, allowed or blocked, listed after a run. recorded on the host, so the guest can't hide it.
explain
burner explain prints what a vm could reach on this host, and the firewall rules behind it.
probe
burner doctor --probe boots a vm that tries your gateway, the host, the lan and your tailnet.
json
--json on every command, and documented exit codes.
debian
a debian 13 image next to alpine.
small
burner bench with published numbers, shell completions, man pages, a proxmox guide, and fuzzing the parsers that read guest output.

v0.4

planned
report
--report says what a run did: files it created, changed or deleted, every connection it tried, and the processes it started.
fake net
--net fake answers dns and http/https from burner itself. the script thinks it's online, you see where it wanted to go and what it tried to fetch, and nothing leaves.
pwsh
an image with powershell, for cross-platform scripts.
limits
a run shows what something did, not that it's safe. some malware waits, or sits still in a vm. the report will say so.

v0.5

planned
group
a burner group that can run vms without sudo, within limits set in /etc/burner.
yours
ls and kill only see your own vms.
caps
host-wide limits on vms, memory and scratch disk.
profiles
named settings like -p agent. a repo's .burner.toml can tighten them, not loosen them.

v0.6

planned
mcp
burner mcp over stdio, so a coding agent can hand burner a script and get the report back. limits come from your config and an agent can't raise them.
patch
--in-dir . copies a project in and --result patch hands back a diff. the vm never writes to your files.
allow
--net allow=@pypi,@npm,github.com to reach only those.
sessions
burner start, exec, cp and stop, to keep one vm for a whole task.

v0.7

planned
oci
burner image pull docker://python:3.12.
packages
an apt repo, a nixos module, the aur and a github action.
audit
a log of what ran with which network, and node_exporter metrics.
ports
--port 8080 on 127.0.0.1 while a vm runs.

after

later
review
an outside security review of the whole thing.
windows
windows vms on a linux host, fresh from a snapshot each run, with the same report. for scripts that only run on windows.
macos
macos vms on a mac, cloned fresh each run, with the same report.
win host
burner itself running on windows, without wsl.
mac net
splitting the mac network process in two, so the part that reads guest packets has no network access.
maybe
--keep with snapshots, an image that runs docker, ipv6, ping and udp on macs.

no

not planned
gpus
gpu passthrough. firecracker doesn't do it.
intel
intel macs. the mac side is hypervisor.framework on apple silicon only.