Why we chose Git as the backend

Every CMS makes a bet about where your content lives. We bet on the place your code already is: your Git repository.

Content as files

Each entry is a small file committed to your repo. That means history, branches, pull requests and rollbacks come for free — you already know the tools.

There is no separate database to back up, no export to fight with the day you want to leave. The content is right there next to the code that renders it.

Drafts are just branches

Editing happens on a working branch. Publishing is a merge. It is the workflow your team already trusts, applied to words and images instead of source.