In short: A GEEKOM MiniAir 11 with Ubuntu is my control centre for everything that should run regularly without me. It runs the Hermes agent, my watchers and several pipelines. The key lessons from running it: services belong under systemd, access is only via SSH with dedicated, restricted keys, and a service isn't set up until it survives a reboot.

Why a separate small computer?

Three computers with clearly separated roles work in my office:

  • TUXEDO notebook: my workstation for development
  • ASUS Ascent GX10: the AI server for large language models and heavy computing
  • GEEKOM MiniAir 11: the small, efficient machine that runs around the clock and controls workflows

That sounds like effort, but it has a clear advantage: an automation doesn't have to run on the big AI server, and my notebook doesn't have to stay on for a service that should always be available. How it all fits together is described in My AI Infrastructure 2026.

Ubuntu as the foundation

The GEEKOM runs Ubuntu with a lightweight desktop. Most of the time, though, it works without a screen and I only access it via SSH.

For services that should start again after a reboot, I use systemd. Hermes runs as a user service, separately for different profiles. I check the state like this:

systemctl --user status hermes-gateway.service
systemctl --user is-enabled hermes-gateway.service
journalctl --user -u hermes-gateway.service -n 50

One important point with user services: whether they start without a login depends on whether "lingering" is enabled for the user. An enabled in the status output is therefore no proof. The real test is a reboot.

The service that restarted 73,000 times

One experience I won't forget: during a check, an old user service showed up that dated from an earlier way of installing Hermes. The program it pointed to had long since gone. systemd still tried to start it every ten seconds, and by then had done so more than 73,000 times.

Nobody had noticed, because the actual Hermes service next to it ran perfectly. A single command fixed it:

systemctl --user disable --now hermes-agent.service

Lesson: after a rebuild, old services need to be cleaned up. And a regular look at failed units pays off:

systemctl --user --failed

Remote access only via SSH

A computer without a screen needs reliable remote access. My rules:

  • Only from my own network. The SSH port is not reachable from the internet. When I'm away, I get into the network via VPN.
  • Keys instead of passwords. Automations and tools get their own SSH keys, not my personal one.
  • As few rights as possible. Where possible, a key may do exactly one thing. The key the GEEKOM uses to have videos rendered on the AI server only allows that one command there.
  • Web interfaces only locally. The Hermes dashboard only listens on the machine itself. When I need it, I forward the port to my notebook via SSH.

Working with the AI server

The GEEKOM doesn't need to hold large language models in its own memory. When a workflow needs a model, it requests it over the network from the GX10. The small machine controls, the big one computes.

For that, the network and availability have to be right. If the AI server can't be reached, a job has to detect and report it instead of failing silently. My website monitor, for example, pauses if the GEEKOM itself was offline, so that no false alarm for every site follows afterwards.

What I would recommend

  • Separate roles: a small, efficient computer for always-on jobs, a powerful one for computing.
  • Everything under systemd: services with clear configuration and logs instead of scripts running somewhere in the background.
  • Test reboots: setup is only finished once everything runs again after a reboot.
  • Clean up: remove old services and schedules after every change.
  • Keep access tight: dedicated keys, few rights, nothing open to the internet.

Conclusion

The GEEKOM MiniAir 11 is neither a replacement for my notebook nor a big AI server. It is a small Linux computer that reliably handles tasks that should keep running without me. The interplay of Ubuntu, systemd, SSH and local AI turns individual programs into a small infrastructure of my own, where I decide what runs.

Frequently asked questions

Is a mini PC enough for this kind of automation?

Yes, as long as it only controls and doesn't run large models itself. Scripts, schedules, notifications and small services need little power.

Why Ubuntu?

Ubuntu is widely used and well documented, and there are guides for almost any software. For a machine that should simply run, that is an advantage.

What is "lingering" in systemd?

Normally user services only run while the user is logged in. With lingering enabled, they start without a login too, for example right after a reboot.

Adapt commands to your own system

The service names above belong to my setup. Check a service’s configuration and purpose before stopping it. A healthy status does not replace a functional check. The systemd documentation on lingering explains running user services beyond a login session.