---
summary: User-visible changes to ScaiBunker.
title: Changelog
path: changelog
status: published
---

User-visible changes only. Internal refactors and infrastructure work omitted.

## v0.1 — Initial release

First public iteration.

- Firecracker microVMs with three lifecycle modes: ephemeral, session, persistent.
- Structured execution API: command run (inline and streaming), file read/write/delete/list, staged upload/commit.
- Interactive PTY shell over WebSocket (relay implementation in progress).
- Five network profiles: isolated, registry, allowlisted, unrestricted, plus v0.2 transit appliances with tenant-scoped Linux bridges and per-interface `spoof_guard`.
- Per-bunker egress shaper (`bandwidth_mbit`) on every profile.
- Image system: OCI and tar sources, ext4 size cap, lazy-pull flag, automatic Trivy security scans with daily refresh.
- Availability groups: tenant- and platform-scoped, image / worker membership drives fan-out warming.
- P2P image distribution: workers fetch ext4 bytes from peers in the same group before falling back to the controller storage proxy.
- Snapshots: manual, idle, terminate, checkpoint, failure triggers; tar.gz archives in S3; per-file download without full restore.
- Egress audit batches: NDJSON in S3 for `unrestricted`-profile bunkers, listed and fetched through the API.
- Quota profiles: per-user `individual`, per-group `shared` and `per_user` assignment modes; most-restrictive-wins composition; live `/usage` endpoint.
- Capability tokens for the storage proxy: short-lived JWTs scoped to a specific verb and path; admin-mintable via `POST /storage/capabilities`.
- `SCAIGRID_MODE=bunker_proxy` deployment: stripped-down storage-proxy-only FastAPI app, no DB or Redis, horizontally scalable behind a load balancer.
- ScaiCore integration: cores declare bunker capabilities in their manifest; activation auto-provisions a sandbox bound to the entity.