Automations that stop and ask
Recipes that run the repetitive part of maintenance and stop to ask you before the part that matters.
Most agency maintenance is the same six jobs done by hand, badly, whenever somebody remembers. It stays manual because one step in the middle needs a human to look at a list and decide, and a script that decides for you is a script you cannot trust with a production server.
So Unolia automations pause.
A recipe is a sequence of steps. Some gather facts, some ask you a question, some act. Five ship today: monitor a new domain, restart servers for a kernel update, update Ubuntu servers, sync Oh Dear's real IPs, and mitigate a copy-fail CVE. Each one starts by working out what is actually in scope, then shows you that list and waits. You pick the three servers you meant, not the eleven it found. Nothing acts until you answer.
Runs start three ways: you press the button, a schedule fires, or something happens in your stack and the recipe reacts to it.
Where a recipe needs to reach a server, it generates a temporary SSH key for the run, installs it, does the work and removes it afterwards. Your long-lived keys stay where they are. Secrets a recipe needs live in the run's own store and never land in the log.
Every run keeps its record: the steps that ran, what each one found, the question you were asked, the answer you gave, and the output of every command. When a client asks what you did on their servers last Tuesday, that is the answer, and it is already written.
Every recipe in that list is a job I had already done by hand often enough to know where it needed to stop and ask me something.