Cloudsteading
store / builds / Cloudsteading, the directory that lists itself

Cloudsteading, the directory that lists itself

FEATURED BUILD architecture
Cloudflare-native SaaS escape

A Steam-like public build lab for SaaS escapes, running on Cloudflare Workers, Pages, D1, KV, R2, and Workers AI.

Architecture
Loadout
Cost delta
Tradeoffs
Get Cloudsteading, the directory that lists itself
Save $145/mo · 30× cheaper
Launch demo View repo
was renting
$150
now owning
$5
escape value
$145
external services replaced
$175/mo mapped
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
Architecture map

How this site runs on Cloudflare

detected + curated loadout
Domains 2
cloudsteading.com
www.cloudsteading.com
Routes SSR
/directory
/projects/:owner/:repo
/submit/*
/api/*
Cloudsteading app
runtime
Astro SSR on Workers / Pages
api endpoints
auth · submit · import · subscribe · moderate
Bindings 6
D1
catalog + submissions + moderation
KV
sessions + fast state
R2
screenshots + generated media
Workers AI
GitHub import + teardown assist
Cache API
public page/cache layer
Turnstile
anti-spam for submits
Implemented features
AI-assisted importDirectory catalogMagic linkModeration queueOpen graph imagesRSS feedSubmission flow
Teardown notes

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.

Discussion · 0

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