0 Get started
An inbound inbox in your own D1, classified on your own Workers AI binding, with every sender linked to the account and purchases you already know about.
Two seams in core, built the same way and defaulting opposite ways — because one of them is a gate and the other is a record.
A management client reaching into your Worker with no data plane between — asymmetric keys you can revoke, 60-second scoped tokens bound to their own body, and rotation that cannot lock you out.
Four payment rails converging on one entitlement in your own D1 — through an idempotent projection that makes a dropped call free and a replayed webhook harmless.
Durable jobs on Cloudflare Workflows, and a duplicated line that reported adding five bindings it had silently declined to write.
Sign-in, OTP, paywall, pricing, subscription — scaffolded into your repo as source you own, and only the ones your Worker actually composes.
Every route declares what it accepts and who may call it, on the route line. Two gates make that structural rather than a habit — and the second one had to resort to a probe.
One virtual module per capability, projected from the Worker's own config at build time — and a capability you did not compose resolving to `{ enabled: false }` instead of failing the import.