md0 VS
CONTENTFUL
GIT VS API
md0 and Contentful are built on different architectural assumptions. Contentful is an API-first headless CMS. Your content lives in Contentful's cloud database, and your site fetches it via HTTP at build time or runtime. md0 is Git-native. Your content lives as markdown files in your GitHub repository, and your site reads those files directly. The distinction matters for data portability, cost at scale, offline access, and how tightly you want to couple your content to a third-party platform.
TRY md0 FREEBackground
What Contentful Is
API-Based Headless CMS
Contentful is one of the original headless CMS platforms, founded in 2013. It stores your content in Contentful's own cloud database using a structured content model you define through their web interface or API. Instead of reading files from your repository, your site makes HTTP requests to the Contentful Content Delivery API (CDA) to fetch entries. This API returns JSON that you then transform into your rendered output. The editor experience for content teams is polished and feature-rich, with field validation, localization support, scheduled publishing, and a robust role-based access system.
The Fundamental Difference: Where Your Content Lives
With Contentful, your content does not live in your Git repository. It lives in Contentful's infrastructure. This is the most important thing to understand when comparing the two tools. Your blog posts, documentation pages, product descriptions, and all structured data are stored on Contentful's servers. Your repository holds only the code that renders that content. Deleting your Contentful account or having your account suspended means your content is inaccessible. With md0, your content is plain markdown files in your own GitHub repository. Shutting down md0 does not affect your content in any way.
When This Architectural Difference Matters
For many use cases, the difference between API-stored and Git-stored content is academic. Your site builds correctly either way. But the distinction becomes real in several scenarios. Vendor lock-in: migrating content out of Contentful requires their export tool and a manual transformation step. Data portability: your content is not in a format your static site generator can read natively without the API. Cost at scale: Contentful charges based on API calls and users. Offline editing: when Contentful's API is down, your builds may fail. With Git-native content, a git clone gives you everything and builds run offline.
Contentful's Free Tier and Pricing
Contentful offers a free Community plan with 25,000 API calls per month, 2 environments, 5 users, and 1 space. For teams that exceed these limits, Contentful's paid plans start at $300 per month for the Basic plan. Enterprise pricing for large organizations runs significantly higher. If your site receives heavy traffic and uses Contentful at build time for a large number of pages, API call limits become a real operational concern. md0 is free for public GitHub repositories with no API call limits, because there is no API to call.
Side by Side
Feature Comparison
| Feature | md0 CMS | Contentful |
|---|---|---|
| Content location | Your GitHub repo | Contentful's servers |
| Git integration | Native | Via webhook only |
| Free tier | Public repos (unlimited) | 25K API calls/month |
| Offline editing | Files are local | API required |
| Data portability | Full (files are yours) | Via export tool |
| API dependency | None | Required for builds |
| Setup time | 2 minutes | 30 to 60 minutes |
| Markdown support | Native | Via rich text field |
Where md0 Wins
Where md0 Is Better for Developer Workflows
1. Your content stays in your repository
Every blog post, documentation page, and content update lives as a file in your GitHub repository. You can see the full history of every edit in your git log. You can roll back any change with a git revert. You can branch your content alongside your code. Contentful provides version history within its own UI, but that history is tied to Contentful's platform. Your GitHub repository has no record of content changes. With md0, content and code share the same history.
2. No API key rotation, no SDK updates
Integrating Contentful into your build pipeline means maintaining API keys, installing the Contentful SDK, handling API response types, and keeping the SDK updated. When Contentful deprecates an API version or changes a response shape, your build breaks until you update the integration. md0 has no SDK. It writes files to GitHub. Your site reads those files with whatever file-reading logic it already has. There is nothing to update on the integration side.
3. No cost at scale for builds
Sites with hundreds of pages that rebuild frequently can consume Contentful API calls quickly. A site with 500 pages rebuilding 50 times per month runs through 25,000 API calls per month, exhausting Contentful's free tier in one month of moderate activity. With md0, your builds read files from your repository. There is no per-call cost and no rate limit to monitor. As your site grows, your build cost does not grow with it on the content-fetching side.
4. No vendor dependency for your build pipeline
If Contentful has an outage, sites that fetch content at build time fail their builds until the outage resolves. md0 content is in your repository. If md0 is unreachable, editors cannot make new changes, but your existing builds run unaffected. Your repository is the source of truth and it is hosted by GitHub, not by a smaller API provider.
5. Immediate setup for markdown-based sites
If your site already uses markdown files for content, adopting md0 takes two minutes. You connect the repository and start editing. With Contentful, you must first design a content model in Contentful's UI that mirrors your existing content structure, then migrate your markdown files into Contentful as entries, then update your site's data layer to fetch from the Contentful API instead of reading files. This migration effort can take days for large content sets.
Honest Assessment
Where Contentful Has a Genuine Edge
1. Non-technical editors with complex workflows
Contentful's editor experience is built for content teams that have no technical background. Scheduled publishing, content previews, editorial workflows with draft and review states, role-based permissions for different content types, and localization across multiple locales are all first-class features. If your organization has a large editorial team with structured review processes, Contentful's workflow tooling is more mature than md0's current feature set.
2. Structured content with complex relationships
Contentful's content model supports references between entries. A product page can reference a brand entry, a category entry, and multiple component entries. These relationships are queryable via the API. For complex content graphs, like those found in e-commerce, multi-brand, or enterprise documentation platforms, a relational content model is genuinely more appropriate than a flat folder structure of markdown files.
3. Multi-channel delivery beyond websites
Contentful's API delivers content to websites, mobile apps, digital signage, IoT devices, and any other channel that can make an HTTP request. If your organization needs the same content to appear across a website, a native iOS app, and a kiosk display with different rendering requirements, an API-based CMS like Contentful is architecturally well suited. md0 is optimized for the Git-based web publishing workflow.
Also See
- Ready to migrate? Contentful migration guide
- Also looking at Sanity? md0 CMS vs Sanity | Compare all CMS alternatives
YOUR CONTENT. YOUR REPO.
Connect your GitHub repository and start editing markdown with no API setup, no SDK, and no per-call billing. Free for public repositories.
GET STARTED FREE