A custom domain for your app
Your customer points app.theirbusiness.com at you and it starts working. The most common shape there is, and the one this was built for.
Use cases
What your customers can finish without you.
RelayDNS connects a domain your customer owns, from inside your product. Here is what it covers today, where one click works, and what happens everywhere else.
One click, today.
Any product that gives each customer a subdomain of their own. Your customer approves once and the records appear.
A help centre or docs site
Support content under your customer's own name rather than a subdirectory of yours.
A status page
status.theirbusiness.com, so an outage notice arrives somewhere their users already trust.
A storefront or booking page
Checkout and scheduling flows that stay on the customer's domain, which is where conversion holds up.
A branded link shortener
Short links on the customer's domain instead of yours, for campaigns and email.
A per tenant portal
One subdomain per account, created and verified without anyone reading DNS documentation.
Coverage
Where one click works.
One click needs the customer's DNS provider to support it. Right now that means Cloudflare. Everywhere else still works, it just asks your customer to copy a couple of records.
Cloudflare
One click, live now
Your customer approves the change on a Cloudflare screen and the records are written for them. Nothing to copy, nothing to type.
More providers
Being onboarded
Domain Connect is a shared standard, and our templates are published in its public repository. Each provider decides separately when to pick them up. We are working through them.
Everywhere else
Records to copy, free
We show the exact records, watch public resolvers until they answer, and tell your product when the domain goes live. This works at every registrar on earth, including the ones that will never support one click.
You are charged twenty cents when a setup finishes automatically. The records path is free, however many domains go through it, so a provider we do not cover yet costs you nothing.
Coming
Not ready yet. Worth knowing about.
Email on a domain
DKIM, SPF, DMARC, a bounce path and click tracking, for a product that sends on its customers' behalf. The template is published and provider onboarding is under way. Not ready to rely on yet.
Custom templates
A published template is a fixed set of records, so one click only covers shapes we have published. If your product asks for something different, you will be able to define your own template and have us take it through review and provider onboarding for you. Until that ships, those setups use the records path.
If your customers connect domains, this is the part they abandon.
One API call from your server, a widget in your product, and a webhook when the domain goes live.