Skip to content

Custom Domains

Add your own domain to any service on ZevCloud. SSL certificates are automatically provisioned via Let’s Encrypt.

  1. Go to your service → Domains tab
  2. Click “Add Domain”
  3. Enter your domain (e.g., myapp.com)
  4. Configure your DNS records (see below)
  5. Click Verify

You have two options:

Add a CNAME record pointing to ZevCloud’s proxy:

TypeNameValue
CNAME@ or wwwproxy.zevcloud.app

If CNAME isn’t possible, point an A record to our server IP:

TypeNameValue
A@162.55.133.205

You’ll also need to add a TXT record for domain ownership verification:

TypeNameValue
TXT_zevcloud-verifyzevcloud-verify-<unique-token>

The exact values are shown in the dashboard after you add the domain.

After DNS verification, an SSL certificate is automatically issued via Let’s Encrypt. This typically takes 1-2 minutes.

If you have multiple custom domains on a service:

  • The first custom domain added is automatically set as primary
  • The primary domain is used for display and (for WordPress) as the siteurl
  • You can change the primary domain from the Domains tab
  • The auto-generated domain (slug.zevcloud.app) always remains active as a fallback

When you attach a root domain (like myapp.com), visitors who type www.myapp.com should land on your site too. ZevCloud handles this with a www redirect: www.myapp.com responds with a permanent redirect to myapp.com, with the path and query string preserved.

You’ll find the toggle on the domain’s card in the Domains tab. It only appears for root domains — subdomains like app.myapp.com don’t have a www variant.

If your domain was registered through ZevCloud (or its DNS is managed by us), everything is automatic:

  • The www DNS record is created for you
  • The redirect and its SSL certificate are configured at our edge network
  • Turning the toggle on or off takes effect within a minute — no redeploy needed

If you manage DNS yourself, ZevCloud can’t create the www record for you. When you enable the toggle, the dashboard shows the record to add at your DNS provider:

TypeNameValue
CNAMEwwwproxy.zevcloud.app

If your provider doesn’t allow a CNAME there, use an A record for www pointing to the server IP shown in the dashboard. Once the record resolves, the redirect and the SSL certificate for www are set up on the next deploy (the toggle triggers one for you).

Click the delete icon next to the domain in the Domains tab. The service will revert to using the auto-generated domain.

For WordPress services, the siteurl and home settings will be reverted to the auto-generated domain.

If you use Cloudflare for your own DNS, set the DNS record for your domain to “DNS Only” (gray cloud), not “Proxied” (orange cloud). ZevCloud issues and manages the SSL certificate at the origin — if Cloudflare also proxies the same hostname, the two SSL layers conflict.