Edge-first on Cloudflare
You want your app and data close to users everywhere, a bill that stays near zero at low traffic, and no egress fees — and you're happy to build on one platform's primitives.
1 makers' products and 44 open-source projects use at least half of these 8 tools.The picks
Workers run your code in hundreds of locations with no cold-start penalty worth noticing, and static assets are free to serve.
Chosen for hosting by 374 makers' products we track · the alternatives →A small, fast TypeScript framework built for edge runtimes, with the same API on Workers, Bun and Node.
Chosen for backend framework by 3 makers' products we track · the alternatives →SQLite as a managed service beside your Workers — cheap, simple, and read-replicated close to users.
No maker's product we track shows it for database yet · the alternatives →Typed queries and migrations with first-class D1 support, and small enough for a Worker bundle.
Chosen for database access & ORMs by 10 makers' products we track · the alternatives →S3-compatible storage with no egress fees, bound directly to your Worker.
Chosen for file storage by 4 makers' products we track · the alternatives →Sessions and OAuth as a library that runs on Workers, with users in your own D1 database.
Chosen for authentication by 6 makers' products we track · the alternatives →A plain HTTP API that works from a Worker — no SMTP connections at the edge.
Chosen for transactional email by 942 makers' products we track · the alternatives →Called from a Worker with streaming; route through a gateway later for caching and spend limits.
Chosen for LLM API by 734 makers' products we track · the alternatives →What this costs you
One platform for compute, data and files means Cloudflare's limits are yours — D1 caps each database's size, Workers cap CPU time per request, and some Node libraries don't run on the edge runtime. Great for read-heavy apps with users worldwide; heavy write workloads or long jobs fit a regular server better.
Who builds this way
Using at least half of these tools, each with a source: makers' products from their own words, customer stories, subprocessor lists or websites; open-source projects from their code.