1
Pick a recipe
Server updates, kernel reboots, a named fix, uptime monitors. The steps are already written.
Automations
Maintenance that runs itself. And asks before it reboots.
Pick a recipe, choose your projects, press Run or hand it a schedule. Unolia works through every server in one go and pauses when a decision is yours.
Apply kernel patch
every Tuesday · 06:00
Monitor a website
the moment it goes live
Fix a vulnerability
when you press Run
Look
Assess
Act, with your yes
Verify
It ran at 06:00. Nobody was awake.
What are Automations in Unolia?
Automations are ready-made maintenance workflows for client sites. Unolia ships recipes for the work agencies repeat: updating every server, rebooting when a new kernel waits, fixing a named vulnerability, creating and aligning uptime monitors. One run works through every server in scope, pauses when a step needs a human decision, and keeps every step, output and answer in a timeline. Recipes run by hand, on a schedule, or from events like a newly imported domain.
Recipes
Real maintenance, ready to run.
No blank canvas, no flowchart to draw. Each recipe is real maintenance work with its steps and safety checks already built in. Pick one, point it at your projects, press Run.
- Servers on Forge and Ploi, one single run.
- Live output, server by server, as it happens.
- Nothing pending? The run skips and says so.
Recipes · Studio Méridien
ready to run
Update Ubuntu servers
Servers
Run
Restart for a pending kernel
Servers
Fix the Copy Fail CVE
Security
Monitor new domains
Monitoring
Keep monitors matched to DNS
Monitoring
Scoped to the projects you choose
How it works
From chore to schedule
2
Scope it and run
Choose the projects or the whole team, press Run, watch the output live server by server.
3
Let it earn a schedule
When the runs get boring, hand it a Tuesday. It still asks when a decision is yours.
Levels of trust
By hand today. On its own when you trust it.
Every automation starts as a button you press. Give it a schedule once the runs look routine, then let events fire it when you stop thinking about it: a new client domain lands in Unolia and its monitor exists before your coffee.
Schedules ship with Startup. Event triggers with Business
You press Run
any recipe, any day
It runs on a schedule
every Tuesday · 06:00
It reacts to events
Run record · Update Ubuntu servers
Completed
06:00
Started on schedule
06:01
8 servers found on Forge and Ploi
06:04
23 updates waiting on 6 servers
06:09
Upgraded server by server, output kept
06:12
Reboot approved by Nadia Roche
06:41
Every server back online and checked
Forward it as is. It reads like a receipt
The record
Maintenance you can prove.
Every step keeps its output. Every question keeps its answer, and who gave it. Failures are loud, declines are recorded, and servers are reached with a key created for the run and removed right after. When a client asks what their maintenance fee bought, you forward the record.
In real life
The chores this retires
The Tuesday round
The run started at 06:00 and worked through every server before the office opened. You read the summary with your first coffee and closed the tab.
The scary headline
A vulnerability makes the news and a client emails within the hour. One recipe assesses every server, patches the exposed ones, reboots and verifies. You reply with the run record before lunch.
The forgotten monitor
A new client domain arrives in Unolia. The event fires, the uptime monitor is created and checked. Nobody wrote a ticket, nobody forgot.
How this grows with your plan
See pricing →Developer
Not included.
Freelancer
Configure the recipes and run them by hand.
Startup
Schedules, as often as daily.
Business
Schedules every 30 minutes and event triggers.
Related feature pages
Security and Maintenance
Continuous checks across DNS, email, dependencies and uptime, with fixes and the proof on the record.
Monitoring Overview
Uptime monitors, Unolia’s own findings and soon application errors, gathered under each client project.
Agency Activity Log
Everything that happens across client projects, signed by whoever did it and filtered in one click.
Stop doing the rounds by hand.
Join the waitlist and let the repetitive maintenance run itself. You keep the say.
Join the waitlist