TAGBASE connects a physical tag to a cloud backend, with the customer’s browser as the only client. There’s nothing to install on either side.
┌──────────┐ ┌────────────┐ ┌──────────────┐ ┌──────────────┐
│ NFC tag │ → │ Smartphone │ → │ Backend │ → │ Verifications│
│ (dynamic)│ │ (browser) │ │ verification │ │ + history │
└──────────┘ └────────────┘ └──────────────┘ └──────────────┘
Components
Dynamic NFC tags. Each tag emits a fresh verification URL on every tap. The material that proves authenticity lives on the tag and is checked server-side.
The browser. Any NFC-capable phone, any modern browser. Tapping opens the verification URL. The customer needs no app and no login.
The verification backend. It validates each tap, runs the two-scan liveness check (see the security model), and records the result. Clients are never trusted with verification logic.
Storage. Tag status, verification history, and product content live in a database.
The brand dashboard. Brands manage products and tags, watch verifications live on a map, and review history and statistics. See using the dashboard.
Writing tags
A dedicated NFC writer (USB or Raspberry Pi) programs tags before they ship on products.
Scaling
Each part scales independently. The backend handles many concurrent taps across a large tag population.