Where We Left Off
In my last post, I talked about why I decided to start building on the platform I sell. The site you’re reading is live on Cloudflare Pages — deployed from GitHub, running on the edge, zero hosting cost. That was Phase 1 and 2. The foundation is set.
But here’s the thing: Pages is just the starting line. The conversations I’m having with customers right now aren’t about static hosting. They’re about compute at the edge, persistent state, zero-egress storage, and AI inference happening in milliseconds. That’s where Cloudflare’s developer platform is headed, and that’s what I need to understand — not from a slide deck, but from actually building it.
The roadmap includes Cloudflare Workers for edge logic, Durable Objects for persistent state, R2 for storage, and Workers AI for intelligent features. Each one maps directly to a real customer use case I’m pitching right now.
The Five Builds
I’ve mapped out five builds, each layering a new Cloudflare product onto this site. They’re ordered deliberately — each one builds on the last, and each one teaches me something I can use in a customer conversation the next day.
Build 1: Cloudflare Workers Serverless compute at the edge
The first build is a Worker — an API endpoint running on saltwaterbrc.com/api/. No origin server. No containers to manage. Just code running in 300+ cities worldwide, responding in milliseconds. This is the foundation of everything else on the developer platform, and it’s the product I pitch most often. When a gaming company needs real-time matchmaking logic closer to their players, or an automotive company needs connected vehicle APIs responding globally without a centralized backend — that’s Workers. I need to have deployed one myself before I walk into those rooms again.
Build 2: Durable Objects Persistent state at the edge
Workers are stateless by default. But what happens when you need to remember something — a session, a counter, a game state? That’s Durable Objects. I’m building a live visitor counter on this site. Simple concept, but the underlying technology is what powers real-time collaboration, multiplayer gaming sessions, and financial transaction coordination at the edge. When I’m talking to a gaming company about how they manage millions of concurrent player sessions, or a financial services firm about real-time fund administration — Durable Objects is the answer. And I’ll have built one.
Build 3: R2 Storage Zero-egress object storage
Every enterprise I talk to is paying egress fees to AWS. Every single one. R2 eliminates that. I’m going to store and serve files from R2 — images, assets, downloads — all integrated with this site. The pitch writes itself: S3-compatible storage with zero egress costs. But I want to understand the developer experience firsthand. How does it integrate with Workers? How does it feel to mount R2 as a filesystem? When a healthcare company asks about storing and serving medical imaging at the edge, or a media company wants to deliver content globally without bleeding money on bandwidth — I’ll have done it myself.
Build 4: Workers AI AI inference at the edge
This is where the platform gets exciting. Workers AI runs machine learning models directly on Cloudflare’s network — no external API calls, no cold starts, no data leaving the edge. I’m building an AI-powered feature on this site. Maybe a chatbot. Maybe a content summarizer. Maybe a smart form that understands what you’re asking before you finish typing. The point is: AI at the edge is the pitch I’ll use with every customer. Data analytics companies running risk models closer to the data source. Healthcare organizations processing sensitive information without it ever leaving the edge. This isn’t theoretical anymore — it’s production-ready, and I’m going to prove it on my own domain.
Build 5: Sandbox SDK Interactive code execution at the edge
This is the one that ties it all together. Cloudflare Sandbox lets you run untrusted code in isolated containers on the edge — Workers, Durable Objects, and Containers in a single product. I’m building an interactive code playground on this site where visitors can spin up a sandbox, write code, and deploy a Worker live in the browser. No local setup. No accounts to create. Just code, build, deploy. This is the ultimate demo. When I’m talking to a company about secure code execution environments, or developer tooling at the edge, or AI agent sandboxing — I’ll point to this site and say “try it yourself.”
Why This Order Matters
These aren’t random. Each build layers on the last. Workers is the foundation — you can’t do anything on the developer platform without understanding Workers. Durable Objects adds state to that foundation. R2 adds storage. Workers AI adds intelligence. And Sandbox SDK wraps it all into an interactive experience that showcases the entire platform.
By the time I’m done, saltwaterbrc.com won’t just be a website. It’ll be a live demo of Cloudflare’s entire developer platform running on a single domain. Pages for hosting. Workers for compute. Durable Objects for state. R2 for storage. Workers AI for intelligence. Sandbox for interactive execution.
No one on the sales floor is running the entire Cloudflare developer platform on their own domain. That changes now.
The Customer Connection
Every build I do here maps to a conversation I’m having in the field. When I sit across from a VP of Engineering at a gaming company and talk about edge compute for player experiences, I won’t be reading from a solutions brief. I’ll be talking about what I built, what I learned, and what surprised me.
When a financial services firm asks how Durable Objects handles concurrent state, I won’t defer to an SE. I’ll explain it — because I built one.
When a healthcare organization asks about data residency and processing at the edge, I’ll understand the architecture — because I deployed it.
That’s the difference between knowing the pitch and knowing the platform. And in enterprise sales, your customers can tell which one you are in about thirty seconds.
What’s Next
Build 1 starts now. A Worker on saltwaterbrc.com/api/ — my first piece of serverless compute running at the edge. I’ll document everything: the setup, the mistakes, the lessons. Same format as always — written for salespeople, by a salesperson.
If you’re following along, this is where it gets technical. And that’s exactly the point.