DEV.co
Open-Source CMS · microfeed

microfeed

Microfeed is a lightweight, self-hosted CMS built on Cloudflare's serverless infrastructure (Pages, R2, D1, Zero Trust). It publishes content as web feeds, RSS, and JSON, supporting podcasts, blogs, photos, videos, and documents with a WordPress-like admin dashboard.

Source: GitHub — github.com/microfeed/microfeed
4k
GitHub stars
1.4k
Forks
JavaScript
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorymicrofeed/microfeed
Ownermicrofeed
Primary languageJavaScript
LicenseAGPL-3.0 — OSI-approved
Stars4k
Forks1.4k
Open issues45
Latest releasev0.1.5 (2025-03-14)
Last updated2026-02-13
Sourcehttps://github.com/microfeed/microfeed

What microfeed is

JavaScript-based CMS leveraging Cloudflare's edge platform for hosting and compute, R2 for object storage, D1 for SQLite databases, and Zero Trust for authentication. Deployed via GitHub Actions; generates static and dynamic feeds from a centralized data layer.

Quickstart

Get the microfeed source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/microfeed/microfeed.gitcd microfeed# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Personal or small-team podcast hosting

Publish audio content with RSS feed generation at minimal cost; leverage Cloudflare's free tier for storage and CDN.

Multi-format content feed (blog + images + links)

Curate and publish heterogeneous content (blog posts, photos, videos, external URLs) through a single admin interface with automatic RSS/JSON output.

Headless CMS with public JSON API

Self-hosted content backend with OpenAPI spec; suitable for developers who want content management decoupled from presentation layer and full control over infrastructure.

Implementation considerations

  • Requires active Cloudflare account with API tokens and a custom domain; free tier quotas apply (review R2, D1, Pages limits for your content volume).
  • Setup involves 5 GitHub secrets, GitHub Actions pipeline, and Cloudflare dashboard configuration; expect 30–60 min for experienced devops, longer if new to Cloudflare.
  • AGPL-3.0 license requires source availability if you modify the code; review implications if you plan to integrate proprietary logic.
  • Alpha stability label suggests API/schema changes possible; plan for potential breaking updates when upgrading between minor versions.
  • Data resides in Cloudflare's D1 and R2; no explicit backup or disaster-recovery strategy documented in README; verify Cloudflare's SLA and backup options.

When to avoid it — and what to weigh

  • Vendor lock-in is unacceptable — Tightly coupled to Cloudflare ecosystem (Pages, R2, D1, Zero Trust); migrating data or deployment requires significant rework.
  • Non-technical users with no GitHub/Cloudflare experience — Setup requires forking repo, managing API secrets, GitHub Actions, and Cloudflare dashboard configuration; not suitable for point-and-click deployment.
  • Need immediate production stability and SLA guarantees — Project is marked 'alpha' stability; version 0.1.5 (latest) suggests early-stage software with potential breaking changes.
  • Complex permissions, multi-tenant, or enterprise workflows — Designed for individual/small-team use; no evidence of role-based access control, audit logging, or enterprise content governance features.

License & commercial use

AGPL-3.0 (GNU Affero General Public License v3.0). Copyleft license requiring source code disclosure when the software is used to provide a service over a network. Modifications must be released under AGPL-3.0 if distributed or deployed publicly.

Requires careful review. AGPL-3.0 permits commercial use, but Network Clause (Section 13) mandates source availability if microfeed or modifications are used to deliver a service to end users. If you fork, modify, and self-host a commercial CMS on top of microfeed, you must provide access to modified source code to all users. Pure hosting/SaaS of unmodified microfeed is possible but consult legal counsel. Proprietary extensions or closed-source overlays are prohibited without explicit dual licensing.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Cloudflare Zero Trust handles authentication for admin dashboard; specifics not detailed in README. AGPL-3.0 source available on GitHub for code review. No security audit, penetration test, or CVE history documented. Consider: R2/D1 data encryption at rest and in transit (Cloudflare responsibility), access control to admin dashboard (Zero Trust scope), and CORS/content-security-policy headers for feed endpoints (not mentioned). No mention of rate limiting, DDoS protection, or input sanitization hardening in available excerpt.

Alternatives to consider

Ghost

Full-featured, self-hosted CMS with built-in membership, email, and content management; supports blogs and newsletters; more mature but heavier footprint and steeper learning curve.

Write.as / Writefreely

Lightweight, open-source blogging platform with RSS; simpler than microfeed for text-only content; no built-in podcast/video support but easier setup.

Transistor / Anchor (Spotify)

Managed podcast hosting with built-in distribution; eliminates infrastructure complexity; vendor-dependent and subscription-based but turnkey for audio-first creators.

Software development agency

Build on microfeed with DEV.co software developers

Fork microfeed, add your Cloudflare API tokens, and start publishing podcasts, blogs, and content feeds in minutes. No servers to manage.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

microfeed FAQ

Can I migrate from another CMS to microfeed?
No documented migration tools or guides. You would need to manually export/import data or write custom scripts; plan accordingly if coming from WordPress or similar.
What happens if Cloudflare changes pricing or discontinues a service?
Data locked into D1 and R2; extraction/migration not detailed. Review Cloudflare's long-term product roadmap and have an exit strategy (backup exports) before committing.
Can I use microfeed without owning a custom domain?
Unknown. README suggests custom domain setup in Step 4; verify if Cloudflare Pages subdomains (*.pages.dev) are supported as fallback.
Does microfeed support media transcoding or adaptive bitrate streaming?
Not documented in README. Appears to be a metadata/feed manager, not a media processing service; rely on Cloudflare R2 for direct media serving.

Work with a software development agency

From first prototype to production, DEV.co delivers software development services around tools like microfeed. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source cms and beyond.

Deploy Your Own Feed on Cloudflare

Fork microfeed, add your Cloudflare API tokens, and start publishing podcasts, blogs, and content feeds in minutes. No servers to manage.