Cloudsteading
Notion
content planning / internal docs
$20/mo
→ D1 + Astro content routes
GitBook
public knowledge base
$18/mo
→ Pages + Workers SSR
ReadMe
developer docs / changelog surface
$99/mo
→ Astro pages + RSS
Typeform
submission intake
$25/mo
→ Submit flow + D1 drafts
Mailchimp
email capture / audience list
$13/mo
→ Subscriber API + D1
Product Hunt
discovery / voting surface
varies
→ Directory + votes + discovery queue
$175/mo of rented services mapped

How it works

The shape of Cloudsteading, the directory that lists itself on Cloudflare, and how it stacks up against the rented tools it replaces.

Architecture

Public interface
Domains 2
cloudsteading.com
www.cloudsteading.com
Routes 6
GET
/directory
browse builds
GET
/projects/:owner/:repo
build page
GET
/alternatives/:saas
SaaS landing
GET
/submit
auth-gated form
POST
/api/vote
cast a vote
POST
/api/import/github
AI-assisted import
↓
App
Cloudsteading app
entry
Astro SSR on Workers / Pages
renderauthsubmitimportsubscribemoderate
↓
AI-assisted importDirectory catalogMagic linkModeration queueOpen graph imagesRSS feedSubmission flow

Cloudsteading lists its own loadout

Cloudsteading is the site you are looking at: a public directory, media surface, and build lab for replacing rented SaaS with small Cloudflare-native systems.

It deliberately includes itself in the catalog so people can inspect the infrastructure behind the platform.

Architecture

  • Astro + Cloudflare adapter — server-rendered pages deployed to the Workers runtime.
  • Pages / Workers — the web app, routing, API endpoints, and server-side rendering.
  • D1 — canonical data for targets, builds, primitives, tags, subscribers, drafts, moderation, and news.
  • KV — session storage and small fast-moving state.
  • R2 — media bucket for screenshots, future stream assets, and generated build artifacts.
  • Workers AI — used for GitHub import and future teardown assistance.
  • Cache API — edge caching for public catalog pages and generated assets.

What it replaces

The platform replaces pieces of a hosted CMS, directory builder, form backend, newsletter capture tool, and lightweight community voting system.

What it does not replace

It is not trying to be a full CMS, full video platform, full email platform, or hosted SaaS marketplace. Those may remain external until the owned version is worth building.

Why this belongs here

Every Cloudsteading entry should answer the same question: what is the target, what is the loadout, what did it cost, and what do you lose by owning it?

This entry is the reference implementation for that model.

Frequently asked about Cloudsteading, the directory that lists itself

What is Cloudsteading, the directory that lists itself? +

Cloudsteading, the directory that lists itself is an open-source GitBook/Mailchimp alternative built on the Cloudflare developer platform. A Steam-like public build lab for SaaS escapes, running on Cloudflare Workers, Pages, D1, KV, R2, and Workers AI.

What does Cloudsteading, the directory that lists itself replace? +

Cloudsteading, the directory that lists itself replaces GitBook, Mailchimp, Notion, Product Hunt, ReadMe, Typeform. Replacing the SaaS saves approximately $145/month at the listed self-host cost.

What Cloudflare primitives does Cloudsteading, the directory that lists itself use? +

Cloudsteading, the directory that lists itself is built on Cache API, D1, KV, Pages, R2, Turnstile, Workers, Workers AI.

How much does Cloudsteading, the directory that lists itself cost to run? +

Cloudsteading, the directory that lists itself runs at approximately $5/month self-hosted on Cloudflare. Equivalent SaaS pricing is around $150/month.

Is Cloudsteading, the directory that lists itself open source? +

Yes. Cloudsteading, the directory that lists itself is open source under the MIT license. Source code is at https://github.com/cloudsteading/cloudstead.

Discussion · 0

sign in to comment →
No comments yet — be the first.