tieback supports flexible domain configuration for Digital Product Passports. Brands can serve passports from platform subdomains or their own custom hostnames.
Every brand on tieback receives a platform subdomain:
This subdomain is immediately available after onboarding and supports all resolver paths and public passport pages.
Example:
Brands can configure a custom hostname to serve passports from their own domain:
Custom hostnames are provisioned via Cloudflare for SaaS and require a DNS CNAME configuration. See the DNS Setup Guide for details.
When a consumer scans a QR code or follows a Digital Product Passport link:
/01/, /mu/, /mb/, /ml/) are forwarded to a Resolution Engine/p/<id>)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.
Custom hostnames support public consumer paths only:
Dashboard and application access should continue to use the platform subdomain (<brand>.tieback.io) or the main application URL (app.tieback.io).
tieback supports both domain models simultaneously: