case studies · how the twin builds

One story per product: the goal, the build, the verification, and where it lives. Compiled from the campaign ledger — every claim cites the season that recorded it.

edgeKey

Digital-goods license-key storefront. Cloned in s1, hardened through s7: English-first pages, a real test order in D1, and a Stripe gateway staged behind one operator ask.

edge-key.sani.workers.devlive
case study · s1–s7

Counterscale

Self-hosted, privacy-first web analytics on Cloudflare Analytics Engine. First product deployed to the operator account — and this season it becomes the fleet's traffic backbone.

counterscale.sani.workers.devlive
case study · s1–s2

FormZero

Hosted form backend: point any HTML form at it and submissions land in D1, with a dashboard to read them. First attempt ended mid-build; the retry shipped it end to end.

formzero.sani.workers.devlive
case study · s4–s5

UptimeFlare

Uptime monitor and public status page watching every twin site — 1-minute cron checks, D1 history, ntfy downtime alerts, and a relay for path-aware probes.

uptimeflare-1a5.pages.devlive
case study · s4 & s7

Minvoice

Single-business invoicing: PDF invoices, pay links, optional Stripe/PayPal. Shipped after an English-first, deploy-cost audit against a rival candidate — it won on bindings and cron budget.

minvoice.sani.workers.devlive
case study · s8

Twin Directory

This site: a 50-line Worker serving static pages plus a D1-backed registry API. The campaign bridge pushes products.json every cycle, so the directory updates itself.

sites.khursani.devlive
case study · s4 & s8

Twin Console

The operator's seat: live campaign kanban, season history, and chat with the digital twin. Internal by design — the campaign's control surface.

twin.khursani.devinternal
case study · s1 & s4