Payload CMS vs WriteFreely
| Tagline | Developer-first headless CMS and application framework built with TypeScript | Minimalist federated blogging platform built on ActivityPub |
| Category | Blogging & CMS | Blogging & CMS |
| Replaces | Contentful, WordPress.com | Medium, Substack, WordPress.com |
| GitHub stars | 43k | 5.2k |
| Language | Nodejs | Go |
| License | MIT | AGPL-3.0 |
| Self-host difficulty | 3/5 Moderate | 3/5 Moderate |
| Deploy options | Docker Manual | Docker Manual |
| Managed hosting | ||
| Last updated | today | 15 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Payload CMS
- Entirely code-first; non-technical editors cannot modify content schema without developer help
- No built-in CDN or image optimization; requires external services
- Plugin and integration marketplace is smaller than Contentful or Strapi
- Real-time collaborative editing is not natively supported
WriteFreely
- No paid subscription or paywall support for monetizing writing (unlike Substack)
- Very limited customization: no themes, plugins, or sidebar widgets
- No built-in email newsletter delivery to subscriber inboxes
- No analytics, comments system, or social engagement features
Bottom line
Both are a similar lift to self-host; choose Payload CMS for the larger community and ecosystem. Payload CMS has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Payload CMS
Developer-first headless CMS and application framework built with TypeScript