How updates work

reMaestro updates as two independent things, on purpose — so an app fix doesn’t wait on the OS, and an OS security update doesn’t disturb your setup.

App updatesThe application itself. Staged, health-checked, switched over in seconds. No reboot.

OS updatesThe operating system, as a signed A/B image. Writes the spare slot and reboots — with automatic rollback if it doesn't come up.

Both are described by one small signed manifest the box fetches from releases.remaestro.app/beta.json. It’s signed with a release key your box trusts, so a box only installs a release it can prove is genuine. The large artifacts (the app tarball, the OS bundle, the container image) live on object storage and GHCR; the manifest just points at them with a hash.

Nothing installs on its own without you choosing it in the console (on the channel you’ve opted into).