Home / Articles / Cloudflare as Lego blocks / Versions / v1.2.0
Cloudflare as Lego blocks: what changed in v1.2.0
From v1.1.0 (2026-10-18, e9fbb78e9) to v1.2.0 (2026-10-18, this release), paragraph by paragraph.
0 paragraphs added, 0 removed, 4 changed in place, 80 unchanged. About 3 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
1 unchanged paragraph
Summary: I keep my domains at Cloudflare, and Cloudflare keeps shipping good things, but I do not want to learn Cloudflare. I wantwould like to use it, the way a non-specialist would, with an agent doing the one-time setup. So this maps its developer platform, as of 18 October 2026, as the smallest blocks a person could put together, each with what it is for and what is free: static hosting with unlimited free requests, Workers at 100,000 requests a day, R2 storage with no egress fees, D1, KV and Durable Objects, 71 models running on Cloudflare's own GPUs with 10,000 free neurons a day and a promise not to train on what you send, inbound email, Zero Trust access for up to 50 users, and domains at cost. Then it tests the question I most wanted answered: can an sgit vault live on Cloudflare? A read-only vault needs no code at all. sgit publish writes a folder any static host can serve, and the real sgit client cloned it back identically. A read-write vault needs one Worker of 83 lines, one R2 bucket and one Durable Object per vault, all on the free plan. We wrote it and ran it in Cloudflare's own local runtime with the real client: create, push, clone, a stale push that merged, two pushes at once where one was told "nothing was overwritten", a read-only clone that could not write, and no plaintext anywhere on the server. The catch for non-specialists is setup: Cloudflare's API cannot be called from a web page, so the one-time setup is a Deploy to Cloudflare button, a temporary account, or an agent with the command line. That is fine, because it happens once.
9 unchanged paragraphs, under In short {#in-short}
What I wantwould like {#want}
I am technical, and I could learn Cloudflare. I do not want to. I wantwould like to use it,it the way I want to use a good tool: put a site on a domain I already own there, keep a vault, run a small API, call a model, receive mail, and not think about any of it again. And I wantwould like the smallest pieces that do each job, the same argument as the minimum code below: the least code and the least configuration that does exactly the thing.
53 unchanged paragraphs, under The blocks {#blocks}, Which models stay inside Cloudflare {#models}, An sgit vault on Cloudflare {#vault}…
The pattern I wantwould like is the first and third together: a published repository per package, with a button for people and a skill for agents, so that "host my vault on my Cloudflare account" is one sentence to an agent, done once, with a scoped token that can be revoked.
17 unchanged paragraphs, under Five packages {#packages}, What I would watch {#watch}, What this does not claim {#limits}…