Domains & Custom Hostnames

Domain Architecture

Domain Architecture

tieback supports flexible domain configuration for Digital Product Passports. Brands can serve passports from platform subdomains or their own custom hostnames.

Domain Models

Platform Subdomains

Every brand on tieback receives a platform subdomain:

https://<brand>.tieback.io

This subdomain is immediately available after onboarding and supports all resolver paths and public passport pages.

Example:

https://mybrand.tieback.io/01/5060999100032

Custom Hostnames

Brands can configure a custom hostname to serve passports from their own domain:

https://passport.mybrand.com/01/5060999100032

Custom hostnames are provisioned via Cloudflare for SaaS and require a DNS CNAME configuration. See the DNS Setup Guide for details.

Architecture Overview

Request Flow

When a consumer scans a QR code or follows a Digital Product Passport link:

  1. The request arrives at the Cloudflare edge
  2. A Tenant Proxy identifies the request type based on the URL path
  3. Resolver paths (/01/, /mu/, /mb/, /ml/) are forwarded to a Resolution Engine
  4. The Resolution Engine calls the tieback backend to resolve the identifier
  5. The consumer receives an HTTP 302 redirect to the public passport page (e.g., /p/<id>)
  6. The passport page renders the full Digital Product Passport experience

Hostname Preservation

The original hostname is preserved throughout the resolution process. Whether the request arrives via a platform subdomain or a custom hostname, the resolver uses the hostname to identify the correct brand and product. The final passport page is also served on the same hostname — so the consumer stays on the brand’s domain throughout the journey.

Supported Path Prefixes

PrefixTypeDescription
/01/<GTIN>GS1 Digital LinkStandard GTIN-based product identifier
/01/<GTIN>/10/<lot>GS1 Digital LinkProduct identifier with lot/batch number
/01/<GTIN>/21/<serial>GS1 Digital LinkProduct identifier with serial number
/mu/<id>Mint UnitDirect mint unit identifier
/mb/<id>Mint BatchBatch-level identifier
/ml/<id>Mint LotLot-level identifier
/p/<id>Passport PagePublic passport rendering destination

Custom Hostname Path Policy

Custom hostnames support public consumer paths only:

PathSupportedPurpose
/01/*, /mu/*, /mb/*, /ml/*✅ YesResolver paths — scan entry points
/p/*✅ YesPublic passport page rendering
/dashboard, /settings, etc.❌ NoApplication routes — use platform subdomain

Dashboard and application access should continue to use the platform subdomain (<brand>.tieback.io) or the main application URL (app.tieback.io).

Platform Support

tieback supports both domain models simultaneously:

  • Start with a platform subdomain — available immediately after onboarding
  • Add a custom hostname later — configure when ready, with no disruption to existing QR codes
  • Both active at the same time — platform subdomain always remains available as a fallback

Getting Started

  1. Your platform subdomain is available immediately after brand onboarding
  2. To set up a custom hostname, follow the DNS Setup Guide
  3. Custom hostnames must be verified before they become active