How manageqrcodes.com works under the hood — for users evaluating trust, and for developers working on the open-source repos.
Manage QR Codes (manageqrcodes.com) lets you create and download QR codes in the browser for free, with no account required. Sign in with Luckee only if you want a saved list you can reopen later.
This page explains how Manage QR Codes is built: what runs in your browser, what happens when you save to My codes, and which open-source repos you can clone. It is not a tutorial for designing a QR code — use the generator on the home page for that.
| Reader | What you are trying to learn | Where to start on this page |
|---|---|---|
| Anyone making a QR code | Understand privacy (local generation) and when sign-in is optional. | Read the lead below, then Trust and Data flow — or skip to the generator. |
| Shop, event, or product owners | Confirm commercial use, file formats (PNG/SVG/PDF), and that downloads do not expire. | You might use this if… and the Features section. |
| Developers cloning the OSS repos | See the web + Express split, env vars, and HTTP contracts without internal repo names. | Repositories, HTTP, Stack, and Web code sections. |
| Coding agents | Onboard to the right repo and ADRs before changing code. | Agent callout at the bottom of this section, then .cursor/rules/AGENTS.md. |
Luckee sign-in syncs your profile and unlocks My codes. It does not gate generation, downloads, or commercial use.
For coding agents
Reference: Web ADR 013 — Browser Supabase auth
| Capability | In the UI | Backend |
|---|---|---|
| Live preview + download PNG/SVG/PDF | #generator on / | Browser only (qr-code-styling, jspdf) |
| Many payload types | Generator tabs | Redux currentQrCode + buildPayload |
| Save to My codes | /codes | POST /api/qr-codes (JWT) |
| Reopen / edit | /code-detail-page | GET/PATCH /api/qr-codes/:id |
| Account profile | /login, /signup | Supabase + POST /api/account/sync |
| Marketing page analytics | All pages | @vercel/analytics (site traffic only, not your QR payloads) |
Two different kinds of “analytics”
Your QR content: stays in the browser until you choose to save form fields to the hosted save API.
This site: optional @vercel/analytics on the Vercel deployment for manageqrcodes.com page views.
Public OSS pair on GitHub org Luckee-Core. Hosted save infrastructure is not listed here.
| Repository | Runs on | Owns | Does not own |
|---|---|---|---|
| qr-code-generator-web | Vercel + local dev | Landing generator, auth UI, My codes UI, browser rendering | Server-side QR PNG generation for the main app |
| qr-code-generator-open-source-express-server | Self-host / local (default port 3023) | Stateless POST /api/generate-code (PNG), /docs, api-docs.json | Luckee sign-in, saved My codes rows |
Full env and route tables: docs/oss/wire-contract.md in the web repo.
Browser-first generation, optional hosted save API, and an optional self-hosted OSS Express API for integrators.
Generation and downloads run client-side. Nothing is sent to generate a download. Logos you upload apply to the current session only; reopened saved codes ask you to add a logo again.
When you save, form fields and design metadata go to NEXT_PUBLIC_CMS_URL with a Supabase JWT. The browser never receives the service role key. Auth email is delivered through Luckee-hosted infrastructure, not composed in the web app.
Self-hosted server with no auth in the default OSS build. Any client that can reach the port may call POST /api/generate-code. Tighten CORS and add rate limits before exposing beyond localhost.
| Secret / data | Allowed | Never |
|---|---|---|
SUPABASE_SERVICE_ROLE_KEY | Hosted save API (server env only) | NEXT_PUBLIC_* or the browser |
SUPABASE anon key | NEXT_PUBLIC_SUPABASE_ANON_KEY in the web app | Service role in the web app |
Saved QR rows | Postgres behind hosted save API | Local-only without save |
Sign-up and password-reset email are sent through Luckee-hosted auth infrastructure. See operator notes in SECURITY.md when published for the web repo.
There is no separate cloud/local surface flag. Guests use the full generator; My codes requires a Luckee session.
| Path | Guest | Signed in |
|---|---|---|
/ | Full generator + download | Same + save to My codes |
/login, /signup | Auth forms | Auth forms |
/codes, /code-detail-page | Redirect to /login (signed-in layout) | List and edit saved codes |
/learn | Static documentation | Same |
| Variable | Purpose |
|---|---|
NEXT_PUBLIC_SUPABASE_URL | Luckee Supabase auth |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Browser auth client |
NEXT_PUBLIC_CMS_URL | Hosted save API base (default http://localhost:3042 in dev) |
From typing in the generator to optional save in My codes.
Is generating really free?
Yes. Creating and downloading on manageqrcodes.com does not require an account or payment.
Is my data private when I only download?
The image is built in your browser. Nothing is sent to generate a download. Saving sends form fields to the hosted save API for your account.
Web CMS client: ApiResult with success, data or error, and httpStatus (see src/api/_shared).
OSS Express: { success: true, data } on JSON routes; POST /api/generate-code returns raw image/png bytes on success.
| Method | Path | Purpose |
|---|---|---|
GET | /api/health | Liveness |
GET | /api/account | Account summary (JWT) |
POST | /api/account/sync | Upsert user from JWT |
GET | /api/qr-codes | List saved codes |
POST | /api/qr-codes | Create saved code |
GET | /api/qr-codes/:id | Load one code |
PATCH | /api/qr-codes/:id | Update saved code |
DELETE | /api/qr-codes/:id | Delete saved code |
| Method | Path | Purpose |
|---|---|---|
GET | /api/health | Liveness |
POST | /api/generate-code | PNG body from JSON { url } |
GET | /api-docs.json | API catalog |
GET | /docs | HTML API reference |
Full env and route tables: docs/oss/wire-contract.md in the web repo.
Versions follow each repo package.json at release time.
Luckee Next.js template conventions. ADRs live in .cursor/architecture/.
| ADR | Summary | This product |
|---|---|---|
| 001 | Redux: flat layers; manual thunks; no selector functions | Yes |
| 002 | Thin app routes; features in src/packages/ | Yes |
| 003 | Styles object + Tailwind template literals | Yes |
| 004 | src/api clients; thunks only; ApiResult | Yes |
| 008 | Static /code-detail-page + currentQrCode | Yes |
| 012 | Form inputs under packages; zero-prop modals | Yes — generator |
| 013 | Browser Supabase + CMS Bearer JWT | Yes — core auth |
Stateless PNG generation for integrators. Not wired into the manageqrcodes.com browser generator.
| ADR | Summary | This product |
|---|---|---|
| 001–002 | Services + router factory; handlers → processX() | Yes |
| 006 | Emoji logging; success/error JSON | Yes |
| 008 | API docs catalog + /docs HTML | Yes |
Same Next.js and Express template families as other Luckee apps; this product adds browser QR generation and optional hosted save APIs.
| Term | Meaning |
|---|---|
| Hosted save API | Backend at NEXT_PUBLIC_CMS_URL for account sync and saved QR rows; not the browser generator. |
| SaveQrCodeBody | name, type, payload, content, and design fields sent when saving — not raw image bytes. |
| Payload | Encoded string placed inside the QR (e.g. URL or WiFi config) from buildPayload. |
| OSS Express API | Optional self-hosted POST /api/generate-code PNG server on port 3023 by default. |
| ApiResult | Web API boundary type from src/api/_shared (success + data or error + httpStatus). |
Agents: after this page, open .cursor/rules/AGENTS.md in the repo you are editing.