UNDO

Every change has an undo.
Even the AI's.

Config edits, package upgrades, site changes, database migrations: Cloudnan records what changed, tells you up front whether it can be reversed, and puts an Undo button next to it.

cloudnan.com / servers / web-01 / changes

Changes

Every change on web-01, newest first

Edited /etc/nginx/sites-enabled/shop.conf
Claude Code (MCP) · 2 min ago
Undoable
Upgraded PHP 8.2 to 8.3 for shop.example.com
Rina (dashboard) · 18 min ago
Undoable
Ran database migration on shop_db
Codex (MCP) · 1 h ago
Partial
Sent a test email through Postmark
AI Server Doctor · 3 h ago
Not undoable

How it works

What happens under the hood.

01
Preview before apply
Before anything touches the server you see the plan: files that change, services that restart, packages that move.
02
Honest label
Each change is labelled Undoable, Partial, or Not undoable. Sending an email or calling an external API cannot be taken back, and we say so before it runs.
03
Approval for risky changes
Changes above your risk threshold wait for a human approval, whether they came from a teammate or an AI agent.
04
Snapshot what it touches
Cloudnan captures the before-state of the files, configs and database objects a change touches, on the server itself.
05
Health-checked apply
After the change, Cloudnan runs the health checks you set (a URL returns 200, a service is active). A failed check rolls the change back automatically.
06
One-click undo
Every entry in the Changes timeline has an Undo button. Undo is itself recorded, so you can see who reverted what and when.

What you get

The capabilities that ship.

Works on plain ext4

No special filesystem, no LVM, no ZFS. Full mode runs on any KVM-class Linux server with normal disk.

Full and Limited modes

On container servers (OpenVZ / LXC) or very low disk, Cloudnan's own operations stay undoable but free-form shell commands are labelled Not undoable.

Database-aware

Schema and data changes made through Cloudnan are snapshotted first. An optional undo-ready storage volume makes large database snapshots instant.

AI agents included

Changes from Claude Code, Codex, Hermes or OpenClaw through Cloudnan MCP get the same preview, label, approval and undo as dashboard clicks.

Full audit trail

Who or what made the change, the exact diff, the health-check result, and any undo.

No false promises

Changes made outside Cloudnan (for example over your own SSH session) are not in the timeline. Drift detection flags them instead.

FAQ

Common questions.

Can everything be undone?

No, and Cloudnan never pretends otherwise. Changes on the server itself (files, configs, packages, services, databases) are usually fully undoable. Side effects outside the server, such as sent emails, DNS at a third party, or paid API calls, are labelled Not undoable before you approve them.

Do I need a special filesystem or disk layout?

No. Full mode works on KVM-class Linux servers (Debian and Ubuntu) on ordinary ext4, with some free disk for undo data. Container-based servers (OpenVZ / LXC) and servers with very little free disk run in Limited mode: changes made through Cloudnan's own tools stay undoable, while free-form shell commands are labelled Not undoable.

How long are undo points kept?

Undo points live on the server, so how far back you can go depends on free disk. When an old undo point is pruned, the Changes timeline shows that change as no longer reversible.

What is the undo-ready storage volume?

When you create a server in your own cloud account you can attach a small block volume for undo snapshots. It makes undo faster and database snapshots instant. The volume is billed by your cloud provider, not Cloudnan.

Related capabilities

AI agents via MCP

Let Claude Code or Codex work on servers with undo behind every action.

Read

Drift Detection

Catches changes made outside Cloudnan.

Read

Backups & Snapshots

Off-server backups for disaster recovery.

Read