Bring your own domain: client-owned domains in the Builder, Docs and Portal
The Builder and Docs now support external, client-owned domains through Cloudflare for SaaS custom hostnames. In the Portal, those domains carry a Client chip, and the estate table can be filtered by owner. The practical result: a partner can run an InsurEco-powered site on its own web address, and everyone looking at the estate can see whose domain is whose.
This shipped in the Builder, Docs and Portal deploys on 2026-10-06. The change log is in the daily what's new.
What changed
Three things, in three places:
- Builder. Sites built in the Builder can be served on an external domain that the client owns, not only on an InsurEco-provided address.
- Docs. Documentation sites get the same support, so a partner's help or reference pages can sit on the partner's own domain.
- Portal. In the estate table, client-owned domains are marked with a Client chip. You can filter the table by owner to see only the domains that belong to clients, or only the ones that don't.
The mechanism underneath is Cloudflare for SaaS custom hostnames. That is the part of Cloudflare built for this exact case: a platform serving traffic for a hostname that belongs to someone else, while the domain itself stays registered to, and controlled by, its owner.
Why the domain should belong to the client
For an agency or an MGA, the web address is not a detail. It is what policyholders type, what appears on printed materials, what sits in email signatures and on carrier appointment paperwork. It is part of how a business is recognised, and it often outlives any one software vendor.
When a platform makes you publish on its own address, a few things follow. Your customers see someone else's name in the address bar. Your search history accrues to someone else's domain. And if you ever move, you start again with a new address and a new set of links to update.
Keeping the domain with the client avoids all of that. The partner keeps the registration and the address. InsurEco provides the site behind it. Ownership stays where it started.
Ownership you can see, not just assume
The Portal side of this release is small, and it matters. An estate of sites tends to grow: some domains are InsurEco's, some are a partner's, some were set up for a pilot and never revisited. Over time, nobody is quite sure which is which.
The Client chip answers that question at a glance. Each client-owned domain is labelled as such in the estate table, and the owner filter lets you narrow the table to the domains that belong to a given owner. For an operations person, that turns "whose domain is this?" from a search through old tickets into a column in a table.
This is the same principle we apply to insurance data: every record has an owner, and that ownership should be visible rather than implied. A domain is not a policy record, but the habit is the same. If something belongs to a client, the system should say so, and anyone with access to the estate should be able to see it.
Who this is for
Agency owners. If you already have a domain your clients know, you can keep using it for a site built in the Builder. Your address stays your address.
MGAs. If you run programs that need their own presence, or you support agencies that each have their own brand, client-owned domains let each site sit on the address that fits it, while the Portal keeps the estate legible with the Client chip and owner filter.
Carrier and reinsurance operations. If you publish documentation for partners, Docs on a client-owned domain means reference material can live on the address your partners already trust.
Anyone responsible for an estate of sites. The owner filter gives you a direct way to separate client-owned domains from the rest when you review, audit or tidy up.
How it fits the way we work
InsurEco exists to make trusted, transparent insurance data the industry standard. The core of that is simple to state: every record has an owner, every access is visible and logged, and data is shared only with consent. It is the opposite of opaque data resale, where information moves without its owner knowing where it went.
Client-owned domains are a smaller version of the same idea, applied to the web presence rather than the data. The client owns the address. The platform serves the site. The Portal shows the ownership plainly. Nothing about the arrangement depends on anyone remembering who set what up.
The data that flows through InsurEco-powered sites follows the same rules as data anywhere else in InsurEco. Secured on InsureBio, the insurance data chain.
What to do next
If you are a partner with a domain you want to use for a Builder or Docs site, talk to your InsurEco contact about setting it up as a client-owned domain. If you manage an estate in the Portal, open the estate table and use the owner filter: the Client chip will show you which domains belong to clients.
The full deploy notes for 2026-10-06 are in the daily what's new.