Custom domains and firm subdomains
Every firm gets a subdomain immediately and can point its own domain at the platform whenever it is ready. Branding resolves from the hostname.
Instant firm subdomains, or the firm's own domain — branding follows
A subdomain on day one
No DNS work required to start. The firm's portal has a real address the moment it is provisioned.
Your own domain when ready
Point a CNAME and the portal answers on the firm's domain, certificate included.
Branding follows the hostname
The tenant resolves from the domain, so the right firm's brand renders before anyone signs in.
The address is part of the brand
A client asked to sign in at a vendor's domain reads it as a vendor's product. A client signing in at their accountant's domain reads it as their accountant's system.
But requiring DNS configuration before a firm can use anything is a good way to stall an onboarding for three weeks.
How domains work
Each firm is provisioned with a subdomain from its slug, which works immediately and needs no configuration. When the firm wants its own domain, it points a CNAME and the platform issues the certificate.
In both cases the tenant is resolved from the hostname, so the correct firm's name, logo and colours render on the sign-in page — before there is a session to read them from.
- An immediate per-firm subdomain from the tenant slug
- Optional custom domain by CNAME, with automatic certificates
- Tenant resolution from the hostname, so branding renders pre-login
- Both addresses live at once during a migration
What changes for the firm day-to-day
Firms can start today and brand the address later, without a migration when they do.
Clients bookmark an address that belongs to their accountant.
What ships in the module
- An automatic per-firm subdomain, live at provisioning.
- Optional custom domain via CNAME with managed certificates.
- Hostname-based tenant resolution so branding renders before sign-in.
- Both the subdomain and the custom domain serving simultaneously.
Updated July 2026