Skip to main content
Workspaces Custom domains

Your brand, your domain. Omazy underneath.

Point a DNS record at Omazy and your customers never see our hostname. Each workspace can claim multiple custom domains — one per app, one for the operator console, one for support — and we handle the certificate.

DNS verification — three steps

From hostname to live in minutes.

One TXT record per host. We resolve it, lock the binding to your workspace, and provision TLS automatically.

01

Pick the host

Decide which subdomain belongs to which app. Cards on chat.acme.com, Support on support.acme.com, the operator console on omazy.acme.com — your call, one workspace.

Hostname

chat.acme.com

02

Add the verification TXT record

Omazy gives you a one-shot token. Add it as a TXT record on the host you want to claim. Most DNS providers propagate in 60 seconds.

TXT record

_omazy-verify.chat.acme.com → omazy-verify=ws_acme_8f3c2a91

03

Click verify

Omazy resolves the TXT, locks the host to your workspace, and provisions the certificate via the platform CDN. From then on, your customers see your domain — Omazy is invisible.

Status

Verified — chat.acme.com → app.cards (TLS active)

DNS · acme.com zone
_omazy-verify.chat TXT "omazy-verify=ws_acme_8f3c2a91"
chat CNAME edge.omazy.cx.
_omazy-verify.support TXT "omazy-verify=ws_acme_b71e0c4a"
support CNAME edge.omazy.cx.

Two records per host — one TXT for verification, one CNAME for traffic. Omazy handles certificate issuance after verification succeeds.

Examples

One workspace. Many hosts. Same control plane.

Bind any host you control to any app, console, or surface. Acme has three brands — they each get their own domain.

https://chat.acme.com

Customer-facing widget

Bound to app.cards

Embedded chat for the Cards app. Customers never leave acme.com.

https://omazy.acme.com

Operator console

Bound to workspace console

Where your team works. Same Omazy UI, your domain in the address bar.

https://support.acme.com

Help-centre + email-to-ticket

Bound to app.support

A separate brand under the same workspace, on its own host.

White-label posture

Omazy powers the ride. Your brand drives.

Custom domains are step one. Paid workspaces unlock the full presentation layer — hide the Omazy footer, ship your own favicons, and put your support email on the customer-facing surface.

Free workspaces can claim a custom domain but keep a small "Powered by Omazy" footer. Pro and above remove it.

See plans

Hide "Powered by Omazy" footer

Owners on paid plans flip a single toggle and the badge disappears across all custom-domain surfaces — widget, console, customer emails.

Custom favicons + logos per app

Each app already carries its own brand asset bundle. Custom domains just put it on your URL too.

TLS auto-renewal

Certificates renew automatically before expiry. No 3am alerts, no manual cert rotation.

Workspace stays the source of truth

Custom domains are presentation. Routing, analytics, billing, and audit log remain on the workspace — one truth, many faces.

Where we are today. Custom domains in Launch 3 ship with DNS verification, TLS provisioning, and white-label posture controls. Edge-side multi-tenant SNI routing lands as part of the platform's Phase H — for now we run a fast certificate pipeline behind the workspace's bound CNAME. Existing customers who want to migrate from a previous reverse-proxy setup get a one-click flow.

Claim your domain in five minutes.

Spin up a workspace, point a TXT record, watch it go green. White-label is two clicks away.

✓ DNS-verified✓ TLS auto-renewed✓ White-label on paid plans