Your server shouldn’t need a wizard.

Why servers needed a wizard.

A traditional server is built by hand. Someone installs Linux, types a few hundred commands over a few years, and ends up with a machine only they understand. When an update goes wrong at two in the morning, that person is the only one who can undo it. When the disk dies, the commands die with it.

That is the real reason small companies pay for hosting. Not the hardware. The babysitting.

Updates like a phone. Undo like a document.

A Grove does not get built by hand. The whole operating system is one file that we build, test and release, the way a phone update is released. Your machine downloads the new version, switches to it at the next restart, and keeps the previous version on the disk.

If the new version has a problem, you go back to the old one. Not a repair, not a rebuild: the previous version is still there, and it still works. There is no half-updated state, and nobody types a command.

The technology behind this is called bootc. What it means for you is simpler: every Grove on the same release is the same machine. When you ask us for help, we are looking at a system we know.

Your stuff lives separately.

The operating system is ours to build and replace. Everything that makes the server yours lives apart from it: your accounts, settings, the apps you installed, your files and their databases. All of that goes into one recovery archive.

The archive is made every night and can be copied to a NAS or to cloud storage. You can restore all of it or just one app, and the machine makes a safety copy before it restores anything. A dead disk, a new machine, a mistake you want to undo: fresh operating system, load the archive, done.

We do not take that on faith. Restoring a full setup is part of the test we run before every release ships.

What that means for you.

• Nothing to learn. Updates arrive, apply on restart, and can be undone. No terminal, no manual.
• An update cannot leave you stuck. The previous version stays on the machine until you decide you no longer need it.
• A broken disk is not a lost business. Your files, apps and settings are in last night’s archive, on your own storage.
• You cannot break it. The operating system is not yours to edit, so if something is wrong, it is a bug on our side, on every Grove on that release. Support starts with fixing it, not with asking what you did.

The operating system and the backup and restore flow are in beta today. A maintenance assistant that watches the machine for you is planned; the repeatable system above is what it will run on.

Been the one fixing a server at two in the morning? Tell us what broke ↗