Markdown files in Git vs Payload
Both are alternatives to Contentful. Here's how they stack up — verified facts, no spin.
Also searched as Payload vs Markdown files in Git — same comparison, one verdict.
Markdown files in Git
For developer-owned content, the CMS may be the thing to remove.
Worth asking before choosing any of the above: does non-technical staff actually edit this content? A great many headless CMS deployments serve documentation and marketing pages maintained entirely by developers — content that could be Markdown files in the repository, reviewed in pull requests, deployed by CI, with no server, no API call metering and no vendor. Every modern framework reads Markdown natively. This is not a product; it is a scope check, and it is the right answer more often than the category admits.
Payload
A CMS that installs into your Next.js app rather than beside it.
Payload is a TypeScript-native CMS that runs inside your Next.js application: the config is code, the types are generated, and there is no separate service to deploy or keep in sync. For a team already building in Next.js that removes an entire moving part, and the developer experience is the best in this comparison by a clear margin. MIT licensed with around 44k stars. The constraint is the same as the strength — it assumes Node and, in practice, Next.js, so it is the wrong answer for a team that is not there.
Side by side
| Markdown files in Git | Payload | |
|---|---|---|
| Sovereignty Score | 99 | 93 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first | Yes | Yes |
| License | N/A — plain files in your own repository | MIT |
| Pricing | Free. There is nothing to host. | Free and open source. Payload Cloud is an optional paid hosted tier. |
Markdown files in Git edges it on the Sovereignty Score, but the right pick depends on the trade-offs below.
Markdown files in Git
Strengths
- +No CMS, no database, no API, no per-record billing — nothing to run
- +Content reviewed in pull requests alongside the code it describes
- +Complete version history for free
- +Every modern framework reads Markdown natively
Trade-offs
- −Non-technical editors cannot realistically contribute
- −No media library or scheduled publishing
- −Structured, relational content becomes awkward quickly
- −Wrong answer the moment a marketing team needs access
Payload
Strengths
- +MIT with no carve-outs — the cleanest licence here
- +Installs into your Next.js app; no separate service to run
- +Config as code with generated TypeScript types
- +Excellent admin interface out of the box
Trade-offs
- −Assumes Node and effectively assumes Next.js
- −Younger than Strapi with a shorter enterprise record
- −Smaller plugin ecosystem
- −Not suitable if your front end is not JavaScript
Related alternative guides
Facts verified 2026-08-05. Licenses and pricing change — spotted something out of date? That's a correction we want.