bootload
⚓ portal

Changelog

2026-07-08 — a clearer portal, a smarter deploy form

The portal got a big usability pass. A new Services page lists your whole fleet at a glance — with auto-archive so old experiments stop cluttering the view — and the service page grew a proper action bar with docked states, plus plain-language failure reasons on replicas, so "why isn't it up?" is answered on the page instead of in the logs.

The deploy form now auto-fills the port for well-known images, offers a dedicated-IP picker, and deploys are public by default — no more silently unreachable services when you skip the domain field. Your wallet page groups the ledger by day and writes notifications in human sentences; domains show expiry and renewal at a glance with grouped DNS records and an on-demand check. Rounding it out: cleaner app-library cards, transparent pricing shown where you make choices, tidy toast notifications — and yes, a proper pixel-boat favicon in your browser tab at last.

For the robots among us: our llms.txt now ships an agent skill for deploying on bootload, so your AI copilot can read exactly how to sail.

2026-07-06 — maintenance that doesn't touch your apps

Platform updates on our workers used to restart the microVMs they hosted. No more: the fleet now re-attaches to running instances during agent updates, so your services sail straight through our maintenance — verified across the whole production fleet. Shutdowns also drain gracefully: stop signals reach every guest in parallel with a real grace period.

2026-07-05 — your mail, your DNS, one test button

Managed SMTP grew up. The submission port now speaks STARTTLS on :587 directly — point any client or library at it, no proxy tricks. The portal shows your SPF / DKIM / DMARC records structured field by field with copy buttons, and a test-send button that mails a probe and shows the result in your mail history. And when your domain's zone is hosted with us, the mail DNS records are published automatically — nothing to paste at all.

Under the hood, the private network between your services got markedly sturdier: cross-machine connections between siblings (app → db.internal) are now watched, self-healing, and no longer depend on which machine your replicas landed on. Multi-service apps just work, wherever the scheduler places them.

2026-07-04 — backups without limits

The backup engine was rebuilt end to end. Backups now run as asynchronous jobs — no more timeouts on big volumes — with sub-second freezes for a consistent snapshot, resumable streaming uploads, and room for 100 GB+ volumes. You get retention with automatic cleanup, a per-project quota, backup deletion that immediately stops its billing, and download links for taking an encrypted export off-platform.

Also in this batch: volume resizes now verify and heal the filesystem so the extra space is really there; bootload self-update keeps the CLI fresh (downloads now served from production); and API keys can be scoped to a project and specific resources, so a CI token can deploy one app and nothing else.

2026-07-02 — your domain, end to end

Buy a domain and put it on your boat without leaving the harbor. The domains page shows live registration prices per TLD (excl. VAT), and once a registered domain is linked to a service, the DNS records are written for you — apex or subdomain — and the edge issues its TLS certificate automatically. Plain HTTP redirects to HTTPS everywhere (the certificate plumbing stays reachable). You'll get two emails in your language: one when the domain is registered, and one the moment it's serving end to end — DNS set, certificate hoisted, HTTPS answering.

Reliability got the same attention: internal services now declare the port siblings reach them on (bootload exposure <svc> internal --port 5432 — the CLI guides you), and the gateway tier was hardened so one tenant's dead route or redeploy churn can never ripple into anyone else's traffic.

2026-06-28 — bootload is live: production in France 🇫🇷

The big one: production is open at my.bootload.io, running on our own hardware in France · Zone 1 (fr1) — real Firecracker microVMs, encrypted volumes, TLS at the edge, per-second billing with real card payments. New projects pick their zone at creation, the CLI points at production out of the box, and trust.bootload.io now reports live production status.

Launch-day sweetener: hosted registry storage dropped from €0.20 to €0.03 per GB-month.

2026-06-22 — hosted databases: Postgres, Valkey & MariaDB

Give your apps a managed database in one click. Postgres, Valkey (Redis-compatible), and MariaDB join the library under a new Databases section in the portal — or run bootload database install postgres from the terminal.

They're private to your project: no public URL, nothing exposed to the internet. Your services reach them by name at <name>.internal — and now from anywhere in your fleet, not just the same machine, so a database and the app that depends on it no longer have to land on the same node. Installing one hands you the connection string to drop straight into your app, and the data sits on the same encrypted, backed-up storage as the rest of your services.

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:

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.