Use case

A CMS for static sites — without migrating anything

Your static site doesn't need a rebuild to become editable. Unfreez connects to the repo, finds every text and image in your files, and gives your client a safe visual editor. Every change is a clean commit.

Try Unfreez for free See how it works

boulangerie-aurore.fr

Artisan bakery — hand-coded

Sourdough is what we do, since 1987

Naturally leavened breads and pure-butter pastries, kneaded every night in our bakehouse.

Order for tomorrow

Butter croissants and pastries, freshly baked

✓ content: update Headline & Photo (via Unfreez) main · just now

A static site is the fastest, cheapest thing on the web — until the client needs to change the opening hours and can't. A CMS is the usual fix, and the wrong one.

The static tradeoff

A hand-coded static site is fast, cheap and nearly unbreakable. The unspoken cost: every content change routes back through you, and the quick-fix email waits until you have a spare moment.

Editing in place, not through a database

Unfreez finds the text, images and list items in your files and anchors each to a precise spot in the source. When your client publishes, the value is written exactly there and committed — no regeneration, no database, and no AI anywhere near the write.

Your client edits; you keep control

You decide what's editable and lock the rest. Your client edits on a live preview and hits Publish — one clean commit, reversible in a tap — and your own pushes are never overwritten.

CMS-grade editing, static-grade site

No build to rethink

No schema, no data source, no admin panel. Unfreez reads the text, images and list items straight from your files, exactly as they are today.

Surgical, never fuzzy

Each edit is written at the exact byte where it belongs. At any ambiguity Unfreez refuses rather than risk your markup — and every publish rolls back in one tap.

Your deploy stays yours

A publish is just a commit on your branch. Netlify, Cloudflare Pages, a manual rsync — however you deploy today keeps working, untouched.

Any static setup

Plain HTML, Astro, Hugo, or a framework export — the same editor. Unfreez meets your files where they are.

Three steps, zero migration

1

Connect the repo

A GitHub App scoped to the repos you pick. Unfreez scans them and lists every text, image and list.

2

Curate the fields

Choose what the client can change, name it in plain words, lock the rest.

3

Invite your client

They sign in with Google, edit on a live preview, and publish — one clean commit each time.

Unfreez vs a traditional CMS for a static site

	Traditional CMS	Unfreez
The site itself	Regenerated by the CMS	The exact files you shipped
Setup	Templates, schema, content import	Connect and curate — minutes
Hosting	Often tied to the CMS platform	Wherever you host now
Content	In their database	Commits in your repo
Performance	Runtime rendering and plugins	Still a static site — nothing added

Static site editing, answered

Which static setups work?

Plain HTML, Astro, Hugo, and framework exports. Unfreez reads the source where your content actually lives.

Does it change how my site is built or hosted?

No. A publish is a commit; your existing build and deploy run exactly as before.

What can my client break?

Only what you unlocked — and even then, ambiguous edits are refused, not guessed. Every publish has a one-tap rollback.

Does the client need GitHub?

No. Google sign-in, a live preview, and Publish. They never see git.

What if I keep editing the code?

Push freely. Unfreez re-anchors around your changes and holds any conflicting client edit for review.