Why this matters
A printed QR code is a promise you can’t take back: menus, posters, packaging, and signage all die the moment their link changes. Dynamic QR makes the printed code permanent and the destination editable: the code points at a stable redirect you control, claimable and re-pointable at any time.
What exists now
- A Cloudflare Workers service handling the redirects at the edge (fast everywhere, nearly free to run)
- A database schema with a claim-secret model: print codes first, claim ownership later
- A test suite around the redirect and claim flows
Infrastructure-shaped and unglamorous, which is exactly why it might quietly become the most-used thing here.
What I’m looking for
Use cases, mainly. If you print things that carry QR codes (menus, event signage, packaging, real-estate signs), tell me what breaks today.
Open questions
- Standalone micro-SaaS, or a utility layer other Venter projects (like the card decks) use?
- What’s the abuse story for claimable codes, and how locked-down does v1 need to be?