Changelog

2026-06-16 — log into your instances + new CLI controls (CLI v0.5.0)

You can now open a shell inside your running instance — bootload shell <service> drops you into an interactive prompt, and bootload exec <service> -- <command> runs a one-off command. It's a secure, proxied session over bootload's own channel — no SSH to set up, no key to manage, and nothing exposed on your container to the public internet. Production services ask for --confirm first, and every session is audited.

This release also brings a batch of CLI controls that mirror the portal:

• bootload compose plan -f docker-compose.yml — preview exactly how a Compose file maps to bootload services before you deploy it.
• bootload exposure <service> public|internal — make a service public or reachable only by its project siblings over internal DNS.
• bootload production / bootload idle-harbor — toggle production protection and scale-to-zero from the terminal.
• bootload token create|list|revoke — mint and manage scoped API keys for CI and scripts, so automation never carries a full-access login token.
• bootload destroy <service> — tear a service down (production deletes are still confirmed by an emailed link, now also via bootload confirm-delete).

Your hosted-hub image list (bootload image list and the resources page) now shows each image's size and push date. On mobile, the portal menu is a clean top bar again instead of crowding the screen.

2026-06-15 — push and manage your own images

Bring your own container images to the hosted registry from the CLI: bootload image login logs Docker in with a scoped token, bootload image push <local-image> puts it in your org's namespace, and bootload image list shows what you've pushed. You can now also delete images you no longer need — bootload image delete <name:tag> or the new hub images card under resources — which stops their storage billing. Deletes are refused while a service still deploys the image, so you can't pull the rug out from under a running app.

2026-06-12 — private test fleet live

The whole platform now runs end to end on our test fleet: customer portal with signup and deploys, the one-click app library (n8n first), multi-node scheduling with least-loaded placement, encrypted volumes and verifiable backups, managed SMTP with DKIM, real TLS at the edge, support tickets, and per-second billing with runway warnings. Public launch preparations underway.

2026-06-11 — vertical slice complete

First real path through the platform: signup → wallet → deploy an OCI image → a genuine Firecracker microVM boots in ~3.4 seconds → HTTPS route → logs → metered billing. From there the build sprint added secrets, volumes, backups, TLS, domains, the image hub, metrics and logs, MCP, and the dashboard — all gated by integration and e2e tests on real microVMs.