Leave the clouds
without losing a byte.

Bring your Takeout, your 20 years of email and your unsorted photos. With undo.

What this actually is

Self-hosted suites already exist — Nextcloud, Umbrel, CasaOS — and best-of-breed apps already solve today: Immich for photos, Home Assistant for the house. NoClouds doesn't compete with those; it runs on top of them.

What's missing everywhere else is the layer that deals with your past: two decades of email, a Google Takeout export, a phone full of unsorted photos, a decade of bank statements — digested once, reversibly, into one normalized database you can actually query, instead of ten apps each holding a fenced-off slice of your life.

Reversibility is the point

Leaving a cloud is a one-way door for most people: you export, you import, and whatever got mangled on the way is gone. Here the pipeline that got your data in can always be run backward.

Snapshot first

Every database write goes through an append-only ledger that snapshots before it touches anything. Any change can be restored.

Nothing vanishes

Nothing is permanently deleted without confirmation. Uninstalling an app quarantines its tables — it doesn't drop them.

Glass box

Curation runs on an explicit vocabulary of reversible operations, not an opaque classifier. You can see why a file ended up where it did.

Local-first, literally

Not a slogan — the mechanism. Your data lives on hardware you own (a Mac and a Raspberry Pi) and is reachable only over your own VPN. There is no account, no tenant, and nothing of yours leaves the house.

Status

NoClouds is being built in the open-ish: it runs, every day, on the author's own Mac and Raspberry Pi. It is not packaged for other people yet — there is no install command to give you that would work today, and putting a fake one here would be a poor start for a project whose whole pitch is that you can trust it with your past.