Multiple Brand Support
A single HaaS space can support sharing data from multiple brands to the CDR ecosystem, each with their own unique branding and separate CDR Data sharing realms. A HaaS brand is one-to-one with the Data Holder Brand of the CDR.
There are two core constraints to this:
- All brands must share the same Data Adapter (the
x-haas-realm-nameheader value is passed to the Data Adapter) - One brand must be designated as the primary brand
Multi-Brand Endpointsβ
In HaaS, every brand is addressed by its own fully-qualified hostname. Each brand's endpoints use the standard HaaS subdomains (auth, api, public, dashboard, management-api, etc.) under a domain that belongs exclusively to that brand.
There is no per-brand routing choice to make. Every space is host-addressed (spec.brands.mode == DOMAIN_BASED), never path-based. The only decision, per brand, is where that domain comes from:
- A domain of its own: Biza Managed Zone (delegate the domain to HaaS; Biza manages all DNS records automatically, including certificate validation records) or Customer Managed Zone (you keep control of your own DNS zone and create CNAME records pointing each branded endpoint to the space's canonical FQDN).
- A subordinate domain: no domain of its own; the brand takes a slug under a base domain the space already delegated, so there's no DNS onboarding step at all for that brand.
See DNS for a full overview of the available DNS options.
haas-manager is the one exception to "every brand has its own domain" as it is a single, space-level administration console, not a per-brand endpoint. It's served on the primary brand's domain by default, but moves to the shared base domain once subordinate domains are configured for the space β see that page's HaaS Manager section for the full breakdown.
Example: Two brands, each with their own domainβ
| Brand | Auth endpoint | API endpoint |
|---|---|---|
| Primary (First Bank) | auth.firstbank.com.au | api.firstbank.com.au |
| Secondary (First Bank Business) | auth.firstbankbusiness.com.au | api.firstbankbusiness.com.au |
Subordinate Domainsβ
The following feature is available on the Nebula series and later.
If you do not have a separate registered domain for every brand, subordinate domains let you onboard additional brands under a single shared base domain instead. You supply a short slug per brand (e.g. firstbank) and a shared base domain, and the platform synthesises all endpoint FQDNs automatically, for example auth.firstbank.cdr.example.com.au.
Subordinate domains require a Biza Managed Zone for the base domain and are described in detail on the Subordinate Domains page, including how they interact with haas-manager and CDR/ACCC certificates.
Mixing custom domains and subordinate domains in one spaceβ
Custom domains and subordinate domains are a per-brand choice, not a space-wide setting. A single space can run:
- a primary brand on its own custom domain,
- some secondary brands each with their own custom domain, and
- other secondary brands as subordinate brands under one shared base domain,
all at the same time. This is the common shape for onboarding a growing set of whitelabel brands: keep the primary (and any brand that already has a registered domain) on its own domain, and add every new whitelabel brand as a subordinate brand with no further DNS delegation required.
Retirement of Path-Based Routing (Nebula series)β
Path-based multi-brand routing is retired in the Nebula series. This is a breaking change for any space currently using the PATH_BASED mode, where secondary brands share the primary brand's domain and are distinguished by a realm prefix in the URL path (e.g. api.holder.com.au/brand-a).
If you are on Magellan and using path-based multi-brand routing, you must migrate each brand to its own fully-qualified host (a custom domain or a subordinate domain) before taking up the Nebula series. See FDO 27Q102 for the required-by date and full details.
In the Nebula series every brand β primary and secondary β is host-addressed. The path-based PATH_BASED configuration option is not available; spec.brands.mode must be DOMAIN_BASED.
What changesβ
Magellan β Path-Based (PATH_BASED) | Nebula | |
|---|---|---|
| Primary brand | api.holder.com.au | api.holder.com.au |
| Secondary brand | api.holder.com.au/brand-b | api.brand-b.com.au (or a subordinate domain) |
| DNS zones required | 1 (primary only) | 1 per brand (or a shared base zone for subordinate brands) |
| Cert scope | 1 per space | 1 per brand per service bucket |
What does not changeβ
- Spaces already using domain-based (
DOMAIN_BASED) multi-brand routing on Magellan are largely unaffected as each brand already has its own FQDN. The ingress layer moves from nginx to ALB (transparent to you), and certificates consolidate to the core ALB. - All three DNS management modes (No Custom Domain, Biza Managed Zone, Customer Managed Zone) are available in both series. If you have already delegated your domain to Biza, that delegation carries forward unchanged.