Skip to content

qod.ing

Client 03 / 21 · product · 2026

Everything behind a printed code: the engine, smart redirects, GS1 links on your own domain, and a code that is never switched off.

on airqod.ing

Read the story

In figures

qod.ing

style combinations tested
810
tests
202
GS1 primary keys
16

The story

  1. Sc. 01 · the brief

    Most QR generators borrow someone else's engine.

    Most QR generators are a thin coat of paint over somebody else's library, or somebody else's server. qod.ing makes the code on the visitor's own device, free and without signup, because not being able to receive your data is an architecture. Underneath sits one promise: new codes can be capped, printed ones are never switched off. Ink is a contract.

  2. Sc. 02 · what we built

    The creator at /qr is the product.

    The studio at /qr is the product: nine kinds of payload, shapes for modules, eyes and pupils, logos, and SVG or PNG downloads without a watermark. Dynamic codes run on a separate short domain with a destination engine: device, country, language, schedule, time window or an A/B split, first matching rule wins. Brands can also print GS1 Digital Links served from their own domain.

  3. Sc. 03 · how we built it

    Our own encoder, proven by someone else's decoder.

    The engine is an in-house ISO/IEC 18004 encoder with no runtime dependencies: all 40 versions, four error-correction levels, eight masks. Tests paint each code to pixels and read it back with jsQR, a decoder we did not write; another suite sweeps all 810 styles for clean, repeatable SVG. Redirects run in a Cloudflare Worker; the site itself holds no secrets.

  4. Sc. 04 · the detail

    A scan never asks whether you paid.

    One test records every request a scan makes on its way through the redirect Worker, and fails if any of them so much as reads a plan, a quota or a subscription. A plan can limit new codes; nothing about a plan can stop a printed one from opening. That is the promise, written as something that can fail.

  5. Sc. 05 · where it stands

    Built in six days, GS1 still open.

    The first commit landed on 27 July 2026; by the end of that day the site had moved to Cloudflare and dynamic codes were routing. GS1 support and the qod.ing name followed on the 29th, short links on their own domain on the 30th. Still open: a screen for managing GS1 links, product-passport data, bulk import, and a first real customer domain.

Credits · A CULT production · 2026

Role
Everything: engine, studio, redirects, GS1 resolver, billing and the name.
Stack
Next.jsCloudflare WorkersOpenNextSupabaseStripeCloudflare for SaaS
Status
on air · 2026