---
title: "Website Maintenance Automations | Unolia"
description: "Ready-made maintenance recipes for client sites: update every server in one run, pause for a human yes, keep the full record. By hand, on a schedule or on events."
url: "https://unolia.com/features/automations"
locale: "en"
---

# 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.

## 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.

## 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.

## From chore to schedule

### Pick a recipe

Server updates, kernel reboots, a named fix, uptime monitors. The steps are already written.

### Scope it and run

Choose the projects or the whole team, press Run, watch the output live server by server.

### Let it earn a schedule

When the runs get boring, hand it a Tuesday. It still asks when a decision is yours.

## 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.

## 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.

## 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.

## How this grows with your plan

| Plan | Value |
| --- | --- |
| 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](/features/security-maintenance)
- [Monitoring Overview](/features/monitoring)
- [Agency Activity Log](/features/agency-activity-log)

## Stop doing the rounds by hand.

Join the waitlist and let the repetitive maintenance run itself. You keep the say.

[Join the waitlist](https://app.unolia.com/register)