Skip to main content
Your project starts at {project}.hiveku.com, but most real sites run on a custom domain like yoursite.com. Here’s how to connect one.

​
Run the Domain Setup Wizard

1

Open Custom Domains

In your project, go to Settings > Custom Domains.
2

Start the wizard

Click Start Domain Setup Wizard.
3

Pick a tier

Pick which environment this domain is for:
  • Production — your live public site
  • Staging — pre-release testing
  • Development — internal / early dev
Most users set up Production first.
4

Enter your domain

Type the domain you want:
  • www.example.com — subdomain (easiest)
  • example.com — apex domain (needs extra setup, see below)
Click Next.
5

Copy the CNAME record

Hiveku shows you a DNS record to add. It looks like:
Type:  CNAME
Name:  www
Value: proxy.hiveku.com
Copy the Value.
6

Add the CNAME at your DNS provider

Log into wherever you bought your domain (GoDaddy, Namecheap, Cloudflare, Route 53, etc.) and add the CNAME record in your DNS settings.
7

Verify DNS

Back in the wizard, click Verify DNS Configuration. Hiveku checks that the CNAME resolves correctly.
8

Wait for SSL

After DNS verifies, SSL auto-provisions — usually within a few minutes. When it finishes, your domain is live over HTTPS.

​
Apex Domains (example.com)

Apex domains (no www. prefix) don’t support CNAME records at the root in most DNS systems. You have two good options:
Some DNS providers (Cloudflare, DNSimple, Namecheap’s premium DNS) support CNAME flattening at the apex. Add the Hiveku CNAME at @ — the provider handles the rest.

​
Cloudflare Users — Read This

Cloudflare adds a wrinkle because of its proxy. Follow one of these paths:
If you use Cloudflare’s proxy (the orange cloud), you MUST either:
  1. Set the record to DNS only (gray cloud) — simplest, Hiveku handles SSL
  2. Keep the proxy on but set Cloudflare’s SSL mode to Full (strict) — otherwise you’ll get redirect loops or cert errors
To change SSL mode: Cloudflare dashboard → SSL/TLS → Overview → set mode to Full (strict). Never use Flexible with Hiveku.

​
DNS Propagation Times

Expect 15 minutes to 48 hours for DNS to propagate globally. Most propagation happens in the first 30 minutes. Check progress with dnschecker.org — enter your domain and record type (CNAME) to see it resolve worldwide.

​
Multiple Domains Per Tier

You can attach multiple domains to the same tier. One is marked Primary; the others redirect to it.
1

Add each domain

Run the wizard once per domain.
2

Pick the primary

In Settings > Custom Domains, click the star icon next to the domain you want as primary. All others redirect to it.
Common use case: example.com, www.example.com, and getexample.com all redirect to www.example.com.

​
Removing a Domain

To detach a domain:
1

Open Custom Domains

Go to Settings > Custom Domains.
2

Click the trash icon

Next to the domain row, click Remove.
3

Confirm

The domain stops serving your site. Your Hiveku subdomain ({project}.hiveku.com) still works, so this is safe.
After removing, you can delete the CNAME from your DNS provider too — though it doesn’t hurt to leave it.

​
Verifying Your Domain

After SSL provisioning finishes:
  1. Visit https://yourdomain.com in a browser
  2. Confirm the padlock shows (SSL is live)
  3. Confirm you see your site, not a 404 or error
  4. Hard-refresh (Cmd+Shift+R / Ctrl+Shift+R) to bypass cache

​
Troubleshooting

Most common cause: the CNAME hasn’t propagated yet. Wait 15-30 minutes and retry. Confirm the record at dnschecker.org — the value should match what Hiveku showed you.
Usually a Cloudflare proxy issue. Set Cloudflare’s SSL mode to Full (strict) or turn the proxy off (gray cloud). Flexible SSL causes mixed-content and redirect-loop errors.
Classic Cloudflare Flexible SSL symptom. Switch Cloudflare SSL mode to Full (strict) in the SSL/TLS section.
Apex doesn’t support CNAME in standard DNS. Either use a DNS provider with CNAME flattening (Cloudflare, DNSimple), or set up a redirect from apex to www. and only connect www..
Each hostname is separate. Add both example.com and www.example.com in the wizard, then pick one as primary so the other redirects.
Verify the record is really there and valid. Some registrars add a period (proxy.hiveku.com.) or drop the protocol — check what dnschecker.org shows vs. what Hiveku expects. If they don’t match, fix the record.

​
What’s Next?

Deploy your site

Push changes live

Custom Domains reference

Full technical reference