li

After building several small bootstrapped SaaS tools on Cloudflare Workers, I put together a clear decision framework for its three core edge storage services:

• D1 for relational structured business data

• KV for global low-latency caching and sessions (with caveats around eventual consistency)

• R2 for file uploads and binary assets with zero egress cost

I also covered common pitfalls like misusing KV for user persistent data, ignoring TTL rules, and mixing up blob storage locations.

Would love to hear how other indie founders architect their data layers on the Cloudflare edge runtime.

I ve been developing my SaaS platform built fully on Cloudflare Workers edge infrastructure.

Edge computing offers huge benefits for solo founders: zero idle server costs and global low-latency performance.

However, I ran into many undocumented hurdles during development:

• Auth.js adaption issues for edge runtime

• Tricky differences between wrangler dev and production environment

• Stripe webhook validation & Resend email domain DNS configuration

Nice to meet all the builders here.

I m an indie developer exploring low-cost edge deployment solutions on Cloudflare.

I ve assembled an integrated stack supporting user login, subscription billing and automated emails, aiming to provide a lightweight foundation for AI tools and small SaaS products.

I d love to connect with other creators building serverless applications.