Every site we build starts from the same simple, fast and almost-free engine. Visitor → Cloudflare Worker → static assets + D1 database. That's it.
The parts
- One Worker. A small program on Cloudflare's network that builds the pages, answers the site's own requests and guards the admin area. No server to pay for or patch.
- Static assets. Styles, scripts and images, served from Cloudflare's network close to each visitor, so pages are fast on phones, even with weak signal.
- A D1 database. Stores users, articles, messages, settings and an activity log. The same engine that publishes also collects the data.
- Your domain. Connected to the Worker, with HTTPS set up automatically.
Why it's fast
- No framework bloat. Hand-written styles and no heavy front-end framework keep pages light.
- Served from the edge. Pages come from Cloudflare locations near each visitor.
Why it's safe
- Secure accounts. Salted password hashes, secure session cookies, optional sign-in with Google and two-factor login with an authenticator app.
- Rate limiting on log-ins and forms, and security headers on every page.
- Every version is kept. A bad change can be rolled back with one command.
How changes go live
Changes are made and tested on a private copy first, then published with one command (wrangler deploy). Database changes always go first, then the code that needs them.
For the full step-by-step, see How we build a whole business site with no servers.