A git-based CMS stores content as files — Markdown, JSON, YAML — in your repository, and gives editors a UI that commits on their behalf. Your content gets the same history, branches and reviews as your code.
TinaCMS, Decap and Keystatic are the main players. The appeal is real ownership: content is plain files in the repo, readable forever, versioned by the same tool that versions everything else.
Prelo takes the ownership idea and swaps the storage: content lives in a single SQLite file inside your project folder. It travels with the repo and backs up as one file — but edits are instant database writes, so clients publish in seconds and never meet a merge conflict. Comparison with the visual git option: Prelo vs TinaCMS thinking, in the roundup.
Close cousins. Flat-file CMSs (Grav, Kirby) store content as files and render server-side; git-based ones add the commit workflow and usually pair with static builds.
Yes — the SQLite file lives in the project and can be committed, snapshotted or synced like any other artifact.
Free and open source. One command, and the client gets a login instead of a Loom.