White-label tracking domains

What it is

White-label serves TrackJet tracking on your own domain, with your brand. A customer who lands on track.acme.com/t/{code} sees Acme's name and colour — not TrackJet's — on the same live tracking page.

How the app side works

When a request arrives on a host a tenant has declared, TrackJet resolves that tenant's brand from the host and renders it. You declare your domains and set a logo/colour on your widget (the same branding the status page and emails use).

The canonical TrackJet hosts are never white-labelled, and a domain is only ever matched to the tenant that explicitly claimed it — one tenant's brand can never bleed onto another's host.

What you set up (DNS + TLS)

The app resolves the brand correctly once a request reaches it; getting your host to reach it is infrastructure you control. For each custom domain, e.g. track.acme.com:

1. DNS (you): add a CNAME track.acme.com → trackjet.world.
2. nginx (TrackJet owner): add the host to the app server block's server_name.
3. TLS (TrackJet owner): issue/extend the certificate to cover the host.
4. Widget (you): add track.acme.com (or acme.com) to your widget's allowed domains and set a logo/colour.

Until steps 1-3 are done, a custom host doesn't reach the app and falls back to the default site. The full runbook is in deploy/OWNER-ACTIONS.md.

Verify

curl -s https://track.acme.com/t/<code> shows your colour; https://trackjet.world/t/<code> is unchanged. Contact TrackJet to provision a new white-label domain.