Skip to content

Custom domains and the widget

What a custom domain does and does not change — the portal is branded, the widget script is always served from app.evoriqa.com.

Reseller and agency accounts only
Warning:

Read this before planning work around it. A custom domain brands the portal — the dashboard, the pre-login pages, and emails. The widget script is always served from `app.evoriqa.com`, and there is no setting that serves it from your own hostname.

What is and is not white-labelled

So a visitor who views the page source of your client's site sees an app.evoriqa.com script URL. Everything they see rendered — colours, avatar, badge — is yours to control on Appearance.

Who can set one

Custom domains are part of white-label and require an active reseller plan. Only the organisation owner can manage one. Without a reseller plan the write is refused with a 403. See Reseller overview.

Setting one up

  1. 1
    Claim the hostname in Settings → Custom domain — a bare host such as

    support.acme.com. The domain becomes pending and a verification token is issued.

  2. 2
    Prove ownership. Add the DNS TXT record shown:

``text host: _sw-domain-verify.support.acme.com type: TXT value: <the token from step 1> ``

Then choose Verify. evoriqa looks up the record and marks the domain verified. Only a verified domain resolves to your brand, so a pending entry can never take over someone else's.

  1. 1
    Point traffic and issue a certificate. CNAME the hostname to your

    deployment and add it to your reverse proxy or hosting platform.

Note:

evoriqa does not terminate TLS or issue certificates for custom domains. HTTPS is handled by whatever sits in front of the app — Caddy with on-demand TLS, Cloudflare for SaaS, or your host's own custom-domain feature.

While the plan lasts

Branding and the custom domain apply only while the organisation holds a reseller plan. If it lapses terminally, the portal and emails revert to evoriqa defaults and the verified domain stops resolving to your brand. A past_due subscription keeps the brand through the dunning window, and the settings and verification are retained — resubscribing restores everything without re-entry.

Removing a domain stays available to the organisation owner even without a plan, so a stale mapping can always be cleared.

Where to go next

Last updated