Awesome Cloudflare Self-Hosted lists open-source apps that replace paid SaaS on your own Workers account
Why it mattersFor small teams, the cost floor of a stack keeps falling: a Worker, a D1 database and an R2 bucket can now replace a bill from Calendly, Bitwarden or Canny.
Theo Ephraim published awesome-cloudflare-selfhosted on GitHub on 15 September. The repository is a curated list of open-source applications that stand in for products a team would otherwise pay for, with one condition: the app has to deploy into your own Cloudflare Workers account, not a VPS or a Docker host. It reached 594 stars in three days and is MIT-licensed.
What is in the list
There are 15 categories in the current README. Analytics has a Google Analytics stand-in built on Cloudflare Analytics Engine, and an Ahrefs and Semrush stand-in that keeps its data on D1 and R2. Auth, secrets and security has a Bitwarden-compatible vault server that the official Bitwarden clients talk to unmodified. Business and operations covers a Canny alternative for feedback boards, a Calendly alternative for booking pages, a Zendesk-style helpdesk with shared inbox and email threading, and a Formspree alternative for form backends.
Other sections cover blogs and CMS (a WordPress-style CMS with plugins sandboxed in Worker isolates, a Mintlify drop-in shipped as a Vite plugin), chat and realtime, developer tools, email and inboxes, files and sharing, link shorteners, notes and knowledge, notifications, remote access, and uptime pages. Every entry names the Cloudflare bindings it needs: D1, R2, KV, Durable Objects, Analytics Engine, Cron, Queues, Workers AI, Vectorize, Hyperdrive, Workflows, Email and Images.
The audit approach
The list checks each entry rather than taking the description on trust. According to the README, the licence is read from the project's own licence file and the platform bindings are read from its deploy configuration. Entries carry warning badges for source-available licences and BUSL, so a reader can tell an OSI-approved licence from one that is not. Cloudflare's own Cloudflare OS project, a Notion-style AI workspace, is listed with a "by Cloudflare" tag.
How contributions work
Contributors do not send pull requests. There is an issue form that asks three things: which repository, which category and what SaaS it replaces. A bot fills in the rest by reading the repository, and a maintainer decides whether the project belongs in the list. On approval the entry file is generated and a pull request opens that closes the issue. This is unusual for an awesome list and is stated in the contributing guide as a way to keep entries checked and consistent.
The engagement pattern for a team building software is the piece worth stealing here. A list where entries are read from the source and not written by hand is closer to a data pipeline than to a Markdown file, and it prevents the drift that turns most awesome lists into archaeology within a year.
For a company weighing a build against a purchase, the useful signal is that the platform now has enough primitives, with enough finished open-source software on top of it, that a small team can shift what used to be four subscription lines into one deploy target. The individual apps are early, so pick one, read its issues and read its code before it becomes load-bearing.
Source
Source: GitHub
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
