- Shipped
- September 28, 2026 at 6:10 PM UTC
- Author
- Kamo
- Commit
- e663547
Four places kept their own "kamocrm.com" literal as the platform host they fall back to, so they could never follow the brand to kamouniverse.com. Each now reads the shared **************** - Hosted Computers: an org with no live domain opens its computer on computers.<primary apex> (KAMO_HC_GUAC_BASE_URL still overrides; unset in prod). computers.kamouniverse.com holds a certificate and is routed by the gateway's computers.* IngressRoute; computers.kamocrm.com keeps working. - Password reset: with no caller origin the link names login.<primary apex>. A reset requested on a kamocrm.com page still links back to it. - Team member activation: kamo.platform.domain (unset in prod) defaults to the primary apex. - Public org branding: a domainless org's themeDomain is {alias}.<primary apex>, the rule PublicLoanApplicationController already reports. Its reader (the meet lobby) takes only the apex to pick theme.<apex>, and every theme.<platform apex> serves the same bucket. Outbound fetchers identify as **************** The KnownAliases javadoc no longer says orgs point at kamocrm.com. Tests pin the new fallbacks next to the legacy-apex cases, which stay.