Custom domains: serve your client portal from your own address
Give clients a branded, secure address for your portal in a few DNS records — certificate and renewals handled for you.
A branded web address is a small thing that changes how a service is perceived. “portal.yourfirm.com.au” reads as our system; a shared subdomain on a vendor's domain reads as a tool they bought. For client-facing work, that difference in perception is worth more than it looks, and it costs surprisingly little to fix.
A custom domain lets your workspace live at a hostname you own. Clients sign in, upload documents, approve engagements and pay invoices at your address, with a valid HTTPS padlock showing your own name in the bar.
How it works
You add a couple of DNS records at your registrar: a CNAME that routes the domain to the app, plus verification records so the TLS certificate can be issued. Finye shows you the exact records to add, then verifies them for you — there is a “check status” button, and a background job that keeps re-checking so the domain flips to active on its own once your DNS is correct. You do not have to babysit it.
Under the hood this runs on Cloudflare for SaaS, so your clients get a fast, globally-distributed edge and automatic certificate renewal. Once it is set up, it simply keeps working; there is no annual scramble to renew a certificate and no risk of a lapsed one throwing browser warnings at your clients.
Pairing it with white-label
A custom domain is most powerful alongside white-label. The domain puts your name in the address bar; white-label makes sure the pages that load there carry your brand and nothing else. Together they turn a shared platform into something indistinguishable from software you built — which, for a reselling practice, is exactly the impression you want.
Takeaway: Pick the address you want clients to use, add the DNS records Finye shows you, and let the certificate and renewals run themselves — a branded, secure portal is a short setup away.