A unique, branded web address (e.g. portal.yourcompany.com) that replaces a platform's default URL, giving your app or client portal a fully
For any client-facing app, portal, or internal tool, the URL is part of the first impression. A custom domain:
- Reinforces brand identity instead of exposing the underlying software vendor
- Builds trust with clients and users, since a branded URL looks more official and secure
- Improves professionalism for extranets, client portals, and self-service tools
- Can support consistent, memorable links across marketing, email, and support materials
Without one, users are reminded at every login that they're using a third-party tool rather than "your" system — which can undercut confidence in client-facing software.
Setting up a custom domain typically involves:
1. Owning a domain name, purchased through a registrar like GoDaddy, Namecheap, or Cloudflare
2. Choosing a domain or subdomain to connect (e.g. portal.yourcompany.com)
3. Adding the DNS records the platform provides — usually a CNAME (for subdomains) or ALIAS record (for root domains)
4. Verifying the connection once DNS changes propagate, which can take anywhere from a few minutes up to 48 hours
Subdomains are generally easier to configure than root/apex domains, since most DNS providers support CNAME records for them out of the box.
Noloco makes connecting a custom domain a point-and-click process. From Settings → Domains, you can add a domain or subdomain, and Noloco generates the DNS records you need to add at your registrar. Once verified, your app — or Client Portal, in the case of an Agency OS — is served entirely from your own URL, with Noloco's "Powered by Noloco" branding removed for a fully white-labeled experience.
Custom domains are available on Noloco's Pro, Business, and Enterprise plans, and SSL is handled automatically once the domain is connected — no separate certificate setup required.