Workers APIs & backends
Low-latency APIs, auth, webhooks and business logic running at the edge on Cloudflare Workers — globally fast, with no servers to babysit.
Cloudflare Development · Cape Town
Cloudflare development,
built end to end.
I'm a freelance Cloudflare developer building fast, secure, edge-native apps on Cloudflare Workers, Pages, D1, R2 and KV — from API and backend work to fully deployed products. One engineer across the whole stack, no agency overhead.
/ what I build on Cloudflare
The edge-native toolkit, end to end
Everything below runs on Cloudflare's global network — compute and data close to your users, billed per-use, with no servers to maintain.
Pages & edge-rendered apps
Astro, React and Next.js on Cloudflare Pages with edge SSR, preview deploys and a global CDN — from marketing sites to full web apps.
D1, R2, KV & Durable Objects
Edge data done right: D1 (SQL), R2 (object storage), KV (config & cache) and Durable Objects for stateful, low-latency coordination.
Migrations to Cloudflare
Move off AWS, Vercel or Heroku to a Cloudflare-native stack — lower cost, lower latency and far fewer moving parts to maintain.
Queues, Cron & background jobs
Async pipelines with Cloudflare Queues and scheduled Workers for processing, notifications, emails and third-party integrations.
Security & performance
Turnstile, WAF, rate limiting, secure defaults and Core Web Vitals tuning. Fast and safe by default — not bolted on later.
/ ways to work together
Engagements
Whether you're starting fresh, moving to Cloudflare, or rescuing something that's grown fragile — there's a shape that fits.
Greenfield builds
A new product or internal tool, architected and shipped on Cloudflare from the first commit to production.
Cloudflare migrations
Replatforming an existing app onto Workers, Pages, D1 and R2 — without a risky big-bang rewrite.
Rescue & performance
Stabilise, secure and speed up an app you already have. Slow, fragile or expensive infra made boring again.
Architecture & advisory
Short engagements to design an edge-native system, review a stack, or de-risk a Cloudflare decision before you commit.
/ how I work
Pragmatic, secure, shipped.
I care about systems that are simple to reason about, cheap to run and safe by default. The stack keeps latency low and infrastructure boring — so the interesting work goes into the product.
01
Secure by default
Input validation, least-privilege access and sane defaults from the first commit — not bolted on later.
02
Edge-native
Workers, D1 and R2 keep compute and data close to the user. Globally fast without a fleet of servers to babysit.
03
End to end
One person across the whole stack means fewer interfaces to misalign and a tighter loop from idea to deploy.
04
Maintainable
Typed, tested and documented. Code a future maintainer — including future me — can actually live with.
/ questions
Cloudflare development FAQ
What is Cloudflare development?
Cloudflare development means building applications on Cloudflare's edge platform — Workers, Pages, D1, R2, KV and Durable Objects — so your code and data run in data centres close to your users worldwide, instead of in a single region. The result is lower latency, automatic scaling and much less infrastructure to maintain.
Why build on Cloudflare Workers instead of traditional servers?
Workers run your code at the edge on every request, scale to zero and to millions automatically, and bill per-use — so there are no idle servers to pay for or patch. For most APIs and web apps that means lower cost, faster global response times and a dramatically simpler operational footprint.
Can you migrate my existing app to Cloudflare?
Yes. I migrate apps from AWS, Vercel, Heroku and traditional Node hosts onto a Cloudflare-native stack — moving APIs to Workers, frontends to Pages, and data to D1 and R2. Migrations are done incrementally so the app keeps running while it moves.
Where are you based, and do you work remotely?
I'm based in Cape Town, South Africa, and work with clients remotely worldwide. Time zones across Europe, the UK and Africa overlap well; US work is handled async with scheduled overlap.
How do projects and pricing work?
Engagements are project-based or contract. Smaller, well-defined work can be scoped as a fixed price; ongoing or open-ended work runs on a day rate. Either way you work directly with the engineer writing the code — no agency layers.
Have something to build?
Open to contract and project-based engagements — greenfield builds, rescue work on existing codebases, or architecture you just need done properly the first time.