How I built a production QR platform

QRinst started as a weekend script to generate a single QR code for an event flyer. The workspace it grew into needed three things a one-off script doesn't: codes that stay editable after printing, scan analytics, and a UI simple enough that a non-technical user could manage a batch of codes without a manual.

The core design decision was to make every code a redirect, not a static payload. A printed QR code points at a short MDXTORA URL, and that URL's destination can change without reprinting anything. That single choice is what makes the analytics and the editability possible.

Everything else — the dashboard, the scan tracking, the tagging — is built on top of that redirect layer.