Platform
Traza brings together three things that usually live apart: the identity of each unit, the record of its lifecycle, and a public, simple way to check both.
Workspace
Illustrative daily lookups; these are not usage measurements.
Example qualitative status. Each signal needs a separate review.
Explore alerts in the example registry.
Compare the record with the medicine label.
Illustrative view. Links open sections of this website; the figures do not describe a live operation.
One platform, six capabilities
Six capabilities that combine according to the deployment. None of them requires replacing the systems an organization already uses.
A unique, signed identifier for each unit, with the minimal data that describes it: manufacturer or importer, product and presentation, origin and lot.
Issuance, printing and activation when production is complete. Then lookups, signals and closure: every event retains its source and timestamp.
Anyone verifies a unit from the browser, with nothing to install and no account to create. The result is explained by signals and in plain language.
Regulators and companies consult the registry, follow anomalies, coordinate field inspections and export information for audit.
Each deployment defines its brand, its identity fields, its event types, its roles and the context the public sees when verifying.
Anyone verifying can prepare a discrepancy report to share with the responsible organisation. This website downloads it locally.
Product view
One unit, three ways to understand the evidence: its record, the recorded events and the checks that explain the result.
Digital passport Example
120 ml bottle
Identifier activated
Example data. Always compare the result with the label and physical unit.
Explore a unitUnit history Example
Identity issued
Issuer · production order
QR printed per unit
Plant · print check
Activation when production is complete
Issuer · completed record
Public lookup
Visitor · comparison with label
Available evidence is distinguished from what needs review. A readable QR or a valid signature alone does not certify the package contents.
A verification does not give a single verdict. It evaluates four signals separately and explains them, so that whoever verifies knows what was checked, how much confidence it provides and what the next step is.
Signature
Whether the identity was issued by the expected issuer and has not been altered.
Registry status
Whether the identity is active, suspended or revoked, and which events are recorded for it.
Data match
Whether what the label shows matches what the registry says: product, presentation, lot and expiry date.
Anomalies
Whether there are signals worth reviewing: repeated lookups of the same code, inconsistent locations or events out of sequence.
A valid signature indicates that the identity was issued; it does not describe the physical content or prevent a label from being copied. That is why the result is never reduced to a single word: it is explained, it comes with a next step, and physical inspection remains necessary.
From production
Traza links a unique identifier to each unit for printing during production. It is activated only when production is complete, with full lot and expiry data.
Look up the example unitTRZ-7F2K-4K7Q-92FA 
The issuer requests identifiers for the order, one per unit.
Each package receives its QR and readable serial during production.
Only when production is complete, printing is confirmed, and lot and expiry data are complete.
Role-based experiences
Access and actions depend on the permissions agreed for each deployment.
People
Scan and compare without creating an account.
Manufacturers and importers
Issue identities and activate units when production is complete.
Authorised teams
Review signals, inspect events and prepare inspections.
Workspace
Illustrative daily lookups; these are not usage measurements.
Example qualitative status. Each signal needs a separate review.
Explore alerts in the example registry.
Compare the record with the medicine label.
Illustrative view. Links open sections of this website; the figures do not describe a live operation.
Example view · explore the lookup and record through the links.
Brand and permissions
The master brand lives at traza.technology. Each medicines programme may present the responsible organization’s visual identity and its own lookup context, subject to approval.
Example co-brand for a pilot proposal. It does not imply an official relationship, approval or implementation.
The tenant lockup shown is a co-brand example included in a pilot proposal. Its use is subject to approval by the corresponding institution and does not imply an official relationship, endorsement or approval.
PUBLIC AND/OR PRIVATE COMPANY | TRAZA: example co-brand, subject to approval. It does not establish an institutional relationship.
Integrations
Connect issuance, activation and lookup with existing systems. Each implementation defines its interfaces, permissions and validation criteria.
Conceptual diagram: management, production, quality and analytics connect to Traza.
Integration capabilities are described generically and without naming products: each deployment agrees its own connectors.
Connection scope
Data, responsibilities and permissions for each system.
Issuance and printing; activation when production is complete.
Readability, data and change-traceability checks.
The three views show public verification, the journey of a unit and the institutional dashboard.
