Docs ·
API·
Content CLI·
Report Bug·
Request Feature
Email Us Privately Welcome to microfeed, a lightweight content management system (CMS) self-hosted on Cloudflare. With microfeed, you can easily publish a variety of content such as audios, videos, photos, documents, blog posts, and external URLs to a feed in the form of web, RSS, and JSON. It's the perfect solution for tech-savvy individuals who want to self-host their own CMS without having to run their own servers.
Publish content yourself in the built-in admin dashboard, or let an AI agent manage it through the official @microfeed/cli.
microfeed is built by Listen Notes and is hosted on Cloudflare's Workers, R2, and D1.
If you have any questions or feedback, please don't hesitate to reach out to us at support@microfeed.org. We'd love to hear from you!
Since the 1990s, a significant portion of the web has been powered by feeds. People (and bots) publish items to a feed, and others can subscribe to that feed to receive new content.
microfeed makes it easy for individuals to self-host their own feed on Cloudflare, including but not limited to
- a podcast feed of audios
- a blog feed of posts
- an Instagram-like feed of images (e.g., llamacorn.listennotes.com,brand-assets.listennotes.com) - a YouTube-like feed of videos
- a personal website with custom links
- a content curation feed of external news article urls
- a marketing site with updates and press coverage (e.g.,
microfeed.org) - a headless CMS with a GUI dashboard, JSON Feed, and generated API docs. Explore the public demo’s
interactive API reference,OpenAPI JSONandYAML, or agent-readyllms.txtandllms-full.txt. - a themeable publishing platform with immutable D1-backed versions, isolated Admin drafts and previews, GitHub installation through
yarn manage theme
, and the standaloneauthoring CLI.@microfeed/theme-kit
- a list of domain names for sale (e.g., ListenHost.com...) - a website for an entire book (e.g., The Art of War) - a changelog website (e.g., changelog.listennotes.com) - ...
microfeed uses Cloudflare Workers to host and run the code, R2 to host and serve media files, D1 to store metadata, and a built-in email and password login to protect the microfeed admin dashboard. Cloudflare provides very generous free usage quotas, making it an affordable solution for personal or small business use. While you will still need to pay for a domain name, hosting microfeed on Cloudflare is essentially free.
With microfeed, you can publish a variety of content such as audios, videos, photos, documents, blog posts, and external URLs to a customizable website, an RSS feed, and a JSON feed. Check out some examples of microfeed in action:
- Web feed: https://llamacorn.listennotes.com/ - Rss feed: https://llamacorn.listennotes.com/rss/ - Json feed: https://llamacorn.listennotes.com/json/
microfeed provides a simple yet powerful admin dashboard, where you create and edit posts, upload media files, and customize how your site looks. If you've used WordPress before, you'll find it familiar.
For agentic content management, the official @microfeed/cli lets a local AI agent create, update, and delete items; upload media files like images, audios, videos and documents. Inside this repository the same command is available as
yarn microfeed
, without global installation.The simplest way to install microfeed is with a local AI coding agent:
Create a local copy of this Git repository on your computer.
Install Gitfirst if thegit
command is not available on your computer:
git clone https://github.com/microfeed/microfeed.git
Open the new
microfeed
folder in an AI coding agent such as OpenAI Codex, Claude Code, Cursor, or another local agent that can run terminal commands and open a browser. - Give the agent this prompt:
Deploy microfeed to Cloudflare.
That's it. The agent guides the setup, runs the deployment, and verifies the finished site. You only step in for Cloudflare browser authorization, choices that require your approval, and creating your private dashboard password.
1-deploy-walkthrough.mp4 #
microfeed has one supported deployment engine: yarn manage
, run from a local Git copy of this repository. A local AI coding agent can operate it for you, or you can run the same guided commands yourself.
Recommended:deploy with an AI coding agent.** Manual:**deploy with.yarn manage
Every command and option: read thecanonical.yarn manage
reference
Both paths for Cloudflare browser authorization and choices that require your approval. Never paste a Cloudflare token, dashboard password, or private password-setup link into an agent conversation or command.
The documentation site covers advanced setup and ongoing management:
Manage your siteUpdate microfeedAdd a custom domain and manage authenticationManage multiple local, production, and preview instancesCreate snapshots and migrate older Pages installationsCheck status and troubleshoot problemsRemove a deployment safely
For exact CLI behavior and safeguards, use the canonical yarn manage reference.
Once initialization is complete, your microfeed instance is ready to use. Choose the publishing workflow that fits the task:
For people: use the microfeedadmin dashboardto create, edit, or delete posts; upload audio, video, images, and other media files when R2 is enabled; use external URLs in content-only mode;customize themes and shared website code; and choosePublic, Headless, or Offline site access.For AI agents: use the officialto manage the same content through browser-authorized access after you enable the API. The agent may start login, but you sign in and approve permissions in the browser. See the@microfeed/cli
guided CLI workflowor the complete.yarn microfeed
reference
Inside a microfeed clone, ask your agent to use yarn microfeed
. For one-off
use elsewhere, it can run yarn dlx @microfeed/cli
. Never paste an API key or CLI credential into an agent conversation.
Open Settings → Themes in the admin dashboard to change how the public website looks. You can create a new version from any installed theme, edit its feed, item, shared layout, and RSS stylesheet, and preview it without changing the live site. Installing a version and activating it are separate actions, so the current design remains available for rollback.
Themes developed by the community can be installed from public GitHub
repositories with yarn manage theme
. Developers and AI coding agents can initialize a standalone theme repository, work with fixtures or a live public JSON Feed, use tools such as Tailwind CSS, and validate the package before it is installed. See Themes and website code for the complete authoring, preview, installation, and asset workflow. New sites start with a familiar, responsive Classic-inspired default whose colors can be adjusted from a short design-token block in an Admin version draft. Its footer stays at the bottom on short or empty pages without becoming fixed or covering long content.
Every site also exposes JSON Feed data, so you can use microfeed as a headless CMS and build separate websites, apps, automations, or integrations around the same published content.
| Feature | What it gives you |
|---|---|
| Publish many content types | Share articles, podcasts, videos, images, documents, and curated external links from one feed. |
| Website, RSS, and JSON Feed | Reach browsers, podcast and feed readers, developer tools, and AI agents without publishing the same item repeatedly. |
| Friendly admin dashboard | Create and edit posts, upload media, control visibility, manage settings, and preview changes in the browser. |
| AI-agent workflows | Deploy and administer sites with yarn manage , then manage content through the official @microfeed/cli and documented API. |
| Versioned themes | Edit safely in Admin or install community themes from GitHub, preview inactive versions, and activate or roll back explicitly. |
| Headless CMS and generated API docs | Use the public JSON Feed or authenticated API with OpenAPI, interactive reference pages, and agent-readable llms.txt . |
| Your data on your Cloudflare account | Keep content metadata in D1 and optional media and theme assets in R2 under infrastructure you control. |
| Portable backups | Export the database, media bucket, theme versions, and migration history together in an owner-readable snapshot. |
| Custom domains and access controls | Use your own web address and choose public, headless, or offline delivery while protecting the dashboard separately. |
| Serverless operation | Run on Cloudflare Workers without maintaining a traditional application server. |
How can I track podcast / video / image downloads?
To track podcast, video, or image downloads with microfeed, you can use the tracking URLs feature. This allows you to set up third-party tracking URLs for your media files, such as those provided by OP3, Podtrac...
To set up tracking URLs, you will need to go to Settings / Tracking URLs:
From there, you can add the third-party tracking URLs that you want to use. microfeed will automatically add these URLs to the front of the URL for your media files, allowing you to track download statistics.
This is a common practice in the podcast industry and can be a useful way to monitor the performance of your content and understand how it is being consumed by your audience.
Why Cloudflare? Isn't it dangerous to trust a for-profit company?
Many individuals and organizations trust and use Cloudflare's services because it has a reputation for providing reliable and effective services. We (Listen Notes) have been using Cloudflare for many years.
It's convenient to manage all things on a one-stop platform like Cloudflare (e.g., DNS, Cache, firewall, running code, CDN, trustless logins...).
microfeed is still in open alpha phase. Cloudflare is the first platform we support. We may consider supporting other serverless platforms, so you can easily migrate away if needed.
What if Cloudflare de-platforms my microfeed instance?
It is important to carefully review the terms of service for any service that you use, including Cloudflare. It is possible that if you violate the terms of service, the service may take action, such as de-platforming your instance.
To protect against the possibility of being de-platformed, it is a good idea to regularly backup your data from Cloudflare. This will allow you to recover your contents and potentially migrate them to a different platform if necessary. It is also a good idea to use your own custom domain, as this will give you more control over your content and make it easier to move your data to a different platform if needed.
Why should I use microfeed?
If you are already using Cloudflare and are satisfied with its services, then using microfeed may be a good option for you.
If you don't want to manage your own servers, microfeed can be a convenient alternative that allows you to take advantage of Cloudflare's infrastructure and security features.
If you don't want to pay for servers, microfeed can be a cost-effective solution, as Cloudflare provides generous free usage quotas.
If you are looking for something new and are interested in exploring different options, microfeed could be a good choice to consider. It is always a good idea to carefully evaluate any service before using it to ensure that it meets your needs and is a good fit for your use case.
How can I download or back up my microfeed data?
microfeed stores metadata in Cloudflare D1 and media files in Cloudflare R2. Create one portable, owner-readable archive containing the D1 schema and durable data, migration history, the entire R2 bucket, object metadata, and checksums:
yarn manage snapshot create --instance production --output backup.tar.gz
You can also download a Cloudflare site and immediately create a new local copy with its real content:
yarn manage snapshot pull \
--instance production \
--local-instance production-copy
Restore archives only with a checkout whose migration history exactly extends the snapshot's recorded history. Local restore requires a new local instance. Cloudflare restore requires a newly initialized site with nonreused, unchanged D1 and R2 resources, a successful dry run, and exact site-name confirmation. See the canonical snapshot command reference for restore examples, migration rules, maintenance mode, and resume behavior.
The archive contains administrator password hashes and possibly private media. It is unencrypted and created with owner-only file permissions, so store and encrypt it according to your backup policy.
We welcome bug fixes, features, tests, documentation, and other improvements. Read CONTRIBUTING.md for local setup, architecture rules, branch naming, validation, and pull request expectations. For substantial features or architectural changes, please open an issue before starting.
microfeed is licensed under the AGPL-3.0 license. Please see the LICENSE file for more information.