Skip to main content
A render comes back as a URL. By default that URL is ours. Add a domain you own and the same image is served from your name instead, so the link a shopper sees belongs to your brand rather than to your supplier. Custom domains are a paid-plan surface. An account on trial credits does not see this page.

Add a domain

Enter the domain, then publish the DNS records the page hands you at your own provider. The page checks for them on its own every thirty seconds, and you can ask for a check immediately rather than waiting. A domain that never verifies is not left in limbo. The page counts down to the point where the attempt is dropped, so an unfinished setup is visible rather than silent.

Choose a default

An account can hold several domains. One of them is the default, and that is the one a render uses when nothing else is specified. Changing the default changes new renders only, so URLs already handed to customers keep working.

Bind a domain to a key

A domain can be bound to a specific API key from the API keys page. This is how one account serves two brands: each key renders to its own domain without either integration having to pass a domain per request.
Binding controls read the plan before they offer themselves. When the plan cannot be confirmed, the page says binding is paused instead of silently writing a binding that would not hold.

Who can change what

Adding a domain, asking for a fresh check and changing the default are owner and editor actions. A viewer sees the list and the status of each domain.

API keys

Where a key is bound to one of these domains.