SubscribeQR: Design QR codes people actually scan

Your QR code shouldn't break because of someone else's server.

Most QR tools send every scan through their own app and database. When their dashboard is slow, down, or switched off, your printed code suffers.

We built it differently. The part people scan and the part you edit are two separate systems. You make changes in Studio. When you save, we store a ready-to-go copy at the edge, close to your visitors. A scan reads that copy, so a normal redirect never waits on our dashboard or database.

What that gives you

⚡ Fast scans. Answered close to the person scanning. A simple QR is one quick redirect.

🛡️ It keeps working when Studio is down. Scans run on Cloudflare, with accounts and analytics on Supabase. You get the uptime and upkeep of two large platforms, and we don't run scan servers.

🔐 Rules on every scan. Password, schedule, countries, scan limit and sign-in are checked at the scan, along with your plan's limits.

📊 No lost analytics. If a scan record fails to save, it's kept and retried every 5 minutes for up to 48 hours.

💸 Built to run cheaply. No server runs per scan, and template code is stored once and shared, so each QR only stores its own data.

Quick note: in production, edits to template pages can take around a minute and a half to go live. Plain link changes don't have this delay. We're working on shortening it.

	A simple server-per-scan setup	SubscribeQR
Where a scan is answered	One central server	An edge server near the visitor
What a scan reads	A database query	A small stored copy
If the dashboard is down	Scans can suffer	Scans keep working
Simple QR with no rules	Server, database, then redirect	One quick redirect
Logging a scan	Can slow the visitor down	Runs in the background and retries on failure
Custom pages	A separate website builder	Built in, with template code stored once