CUSTOM DOMAINS
Custom domains for a site you uploaded
Point a domain you already own at a site you dropped in here, and the certificate is issued and renewed for you. No server, no DNS panel of ours to learn, no renewal to remember.
Free plan, free SSL, no credit card.
Plan availability
Which plans include custom domains
Connecting a domain starts on Pro ($15 a month). Every plan below it still gets a permanent HTTPS address on our own domain.
- Free Not included
- Starter Not included
- Pro Included
- Business Included
- Enterprise Included
Read from the plan records this account is billed against, not from a page someone wrote, so it cannot disagree with what happens when you click the button. See every plan and its limits.
What it does
What connecting a domain actually changes
The site does not move and it does not get rebuilt. One more name starts answering for it, and that name is yours.
When you publish here, the site is already live on a subdomain of ours over HTTPS. Connecting a custom domain adds your own name in front of exactly the same files: www.yourstudio.com and the address we gave you serve the same bytes from the same deployment. You add two DNS records at your registrar, we watch for them, and once they resolve the certificate is requested, installed and renewed on its own for as long as the domain stays pointed here.
The part people expect to be difficult is the certificate, and it is the part you do not touch. There is no ACME client to install, no renewal cron to forget, and no separate certificate purchase. Behind the scenes the edge asks us whether a domain is allowed to have one before it issues, which is also what stops somebody pointing a domain they do not own at your account. Apex domains and subdomains both work, and the same site can answer on several names at once, so a rename does not break the link you already sent. If you have not published anything yet, static website hosting covers the upload side first.
How to use it
Three steps
-
Publish the site first
Drop the files in and confirm the page looks right on the address we issue. A domain pointed at a site that is not working yet just moves the problem.
-
Add the DNS records
The dashboard shows the exact records for your domain, and we have a per-registrar walkthrough if your panel calls them something else.
-
Wait for the check to pass
We poll for the records and issue the certificate as soon as they resolve. Most registrars are done inside an hour, some take longer.
Where it earns its keep
When people reach for this
A client site that has to look like the client owns it
Agencies rarely get to hand over a link on somebody else's brand. Publish the build, connect the client's domain, and the only name in the address bar is theirs. See static hosting for freelancers for the whole workflow.
A campaign page that outlives the campaign
A landing page on a memorable name is easier to put on a poster or read out loud than a generated subdomain, and it stays yours if you ever move it somewhere else.
A documentation or status page on a subdomain
Point docs.yourcompany.com here and keep the main site wherever it already lives. A subdomain is the easiest way to add a static page to an existing setup without touching it.
The alternative
Doing this without us
The alternative is not "no custom domain". It is a small pile of separate jobs that each have to keep working.
| Droply | A VPS you set up yourself | |
|---|---|---|
| Getting the certificate | Requested and installed when the DNS check passes. | Install an ACME client, open port 80, keep it running. |
| Renewing it | Automatic, with no action and no expiry date to track. | A timer you have to notice when it stops firing. |
| Server maintenance | None. There is no server of yours in the path. | Patching, restarts, and a web server config to maintain. |
| Several names on one site | Add each one; they all serve the same deployment. | A virtual host block and a certificate entry per name. |
| What it costs | Included from Pro upward, at $15 a month. | The machine, plus your time when it breaks. |
Compared against running a small Linux server yourself, which is the usual alternative for a static site on a custom domain. Checked September 2026.
When this is not the right tool
A custom domain here points at static files. If your domain needs to do more than that, some of it belongs elsewhere.
- We do not sell or register domains. You buy the name wherever you like and point it here.
- Email on that domain is untouched and stays with your provider. We serve web traffic only, so your MX records are your business.
- You need access to the domain's DNS. If somebody else manages it, they have to add two records for you.
- A domain can only be connected to one account at a time, which is what stops a stranger claiming it.