For accounting firms · controlled pilot

Custom domains during the pilot

Do not assume custom domains, white-label portals, per-client domains, or branded invitation links are included in the current accounting-firm pilot. These capabilities may exist behind product controls, but availability and setup are confirmed individually during onboarding.

Before changing DNS

Contact Kelvaro pilot support before creating or changing any DNS record for a Kelvaro custom domain. Support will first confirm that the custom-domain workflow is enabled for your firm and provide the current target hostname and verification instructions.

Do not reuse old DNS instructions. Provider, proxy, certificate, and routing details can change. Follow only the values supplied for your current pilot workspace.

If custom-domain access is enabled

Choose a subdomain you control, such as portal.example.com.
Use only the DNS record supplied by Kelvaro for that pilot workspace.
Wait for the product to report the domain as verified/active before using it in contractor communications.
Test the domain in a private browser session before sending contractor invitations.
If branding or routing is incorrect, revert to the canonical Kelvaro URL and contact support rather than improvising DNS changes.

Commercial scope

Kelvaro is not publishing a canonical custom-domain add-on price, per-client domain price, white-label entitlement, or service-level guarantee during the controlled pilot. Any enabled capability and commercial treatment are confirmed directly during onboarding.

Security and support

DNS ownership does not change Kelvaro's authentication, tenant-isolation, payout, tax-document, or support controls. Do not send DNS-provider credentials, API keys, passwords, tax IDs, or bank details by email.

For pilot support, email support@getkelvaro.com.