Boot metal as a service
Your workload, built once as a golden image on ZFS and delivered to bare metal running on first boot: from a USB stick, over the network, or as a file you can upload anywhere. An update is a new image promoted beside the old one. The way back is one reboot.
BootMASS is a consulting company. Its tool turns bare metal into a ZFS-on-root machine from a signed image, keeps it able to roll back, and installs over the network: a rack armed with one command, no packet from the internet. It is not sold on its own; you get it by working with BootMASS, and it ships inside every Zettarack appliance.
The image is the artifact
The usual way builds a machine, configures it into a workload, and keeps configuring it for life. BootMASS starts from the other end: build your artifacts, include them in the image, configure them to run, and cast the whole thing as one golden image. Nothing is applied, managed or upgraded on the machine afterwards.
This is immutable infrastructure, done on ZFS: no pet, no configuration tool, no package manager on the machine. It works with every build system and needs none. Your code stays in git, your CI builds and tests it, and the golden image is the step after that: the whole running system as one artifact.
The argument in slides, today's way and this one side by side: What if ZFS wasn't a plug-in?
bootmass cast makes it a golden image, one ZFS stream with its digest; bootmass release signs it. A snapshot: it clones and replicates at will.From deploying a mess to promoting a known good
A deploy stops being a procedure and becomes a promotion. The image that passed is received into a new boot environment beside the running one and switched to whole; blue/green is choosing which is active, and going back is choosing the one before. No apt or dnf upgrade, no drift, no update that fails halfway: rollback, reboot, done.
Unbreakable, and what that means
The claim is about the system, not the data: you cannot brick a machine built this way with an upgrade, and the way back from anything wrong in the system itself is one reboot. Your data has snapshots and backups, a different thing.
Three ZFS layers: the signed image, read-only; a boot environment cloned from it per release; the machine's own state, kept across them. A release is received whole or not at all; the running environment is snapshotted first; the new boot menu is tried once. Five minutes into the first boot, bootmass doctor checks the machine, and if it does not pass, the environment before is booted into and that release is never installed automatically again. A check that could not run counts as failed.
bootmass be activate names the one before. The last five stay on the disk.Not a provisioning stack
Metal-as-a-service and infrastructure-as-code tools deploy a target, usually from a vendor's image or installer, and then rely on management to turn it into a workload and keep it that way. Each does its job well; together they are a stack to run before the first workload does.
BootMASS is one binary with no service and no vendor image. It assembles the distribution from its own packages, seals it with your workload as a golden image, and delivers it running on first boot; an update is a new image beside the old, undone by choosing the one before.
ZFS from the first block
The machines are yours to look after, and ZFS makes that small: pooled disks, a checksum on every block, snapshots, clones, encryption and replication in one layer. Elsewhere it is a storage plugin on a system that boots from something else. Here the root is ZFS, the machine's settings are a dataset in the pool, encrypted with it when you choose, and boot environments are chosen by a menu that reads the pool directly, with no GRUB.
What BootMASS does for you
Work à la carte, by the engagement. Each of these is something I have built and run.
$ dig +short txt hire.bootmass.com | tr -d '"' | base64 -d | rev
The appliance company, Zettarack
Zettarack, the sister company, makes whole machines for your own hardware, each with one job, built on ZFS from the disk up and installed with the bootmass tool. The method above is proven on them today: vmx, the hypervisor, and zxp, the storage server, both in testing.