public active Last verified 2026-03-30

Topolo Quro

Public overview of the QR creation, redirect, analytics, and authenticated UI surface in the Topolo portfolio.

Owners
growth-platform
Source Repos
Applications/TopoloQuro, Websites/docs
Systems
Topolo Auth, Topolo Quro
Tags
qr, redirects, analytics

What It Is

Topolo Quro is the QR creation, redirect, and scan-tracking application in the Topolo portfolio.

Architecture

The current repo shape includes an API worker, a redirect worker, a canonical modern UI, and a retained legacy UI used only for reference and parity checks.

Runtime Surfaces

Use /systems/topolo-quro for the current deployment inventory and service metadata.

API Reference

The active contract centers on QR creation, templates, analytics, redirect resolution, and org-scoped authenticated browser flows.

Auth and Permissions

The canonical current UI uses the first-party Topolo auth pattern with authenticated routes and callback flows. The legacy UI should not be treated as the active auth model.

Data Ownership

Quro owns QR assets, redirect mappings, analytics, and related org-scoped settings and dashboards.

Deployments

Deploy Quro as a cluster of API, redirect, and authenticated UI surfaces. Treat the legacy UI as reference-only.

Failure Modes

  • legacy UI behavior is mistaken for the live product contract
  • redirect and analytics behavior drifts from the authenticated create/manage surface
  • auth flows are documented from the wrong UI generation

Debugging

Start with /systems/topolo-quro, then confirm whether the failing behavior belongs to the canonical UI, redirect worker, or API worker.

Change Log / Verification

  • Added canonical Topolo Quro coverage and retired repo-local Quro docs on 2026-03-30