Custom Domains

Point your own domain to your Clouderized app in three steps

How it works

Every app on Clouderized gets a default URL at username-appname.clouderized.com. Custom domains let you serve the same app from your own domain — HTTPS is handled automatically, no certificate management needed.

1

Add your domain in the portal

Enter the domain or subdomain you want to use in the Domains tab of your app.

2

Add a CNAME record

In your DNS provider, create a CNAME pointing your domain to the address shown in the portal.

3

Verify and you're live

Click Verify in the portal. Once DNS is confirmed, your domain is live with HTTPS.

Step 1 — Add your domain in the portal

Takes about 30 seconds

  1. 1

    Open the Domains tab

    Go to dash.clouderized.com → select your app → click Domains.

    2

    Enter your domain

    Type the domain you want to use (e.g. app.example.com or example.com) and click Add Domain.

    3

    Copy the CNAME target

    The portal shows a CNAME address. Copy it — you'll need it in the next step.

Step 2 — Add a CNAME record in your DNS

Works with any DNS provider — Cloudflare, Namecheap, GoDaddy, Route53, etc.

Log in to your DNS provider and add a CNAME record for your domain pointing to the address you copied from the portal.

DNS record to add
Type Name / Host Value / Target TTL
CNAME app (or @ for root) <CNAME from portal> Auto
Subdomain (recommended): Use app.example.com — set the Name to app and the Value to the CNAME from the portal.
Root domain (example.com): Some DNS providers support CNAME on root domains (called ALIAS or ANAME records). Check your provider's documentation. If not supported, use a www subdomain instead.
Using Cloudflare DNS? You can leave the proxy toggle (orange cloud) on or off — both work. Using the proxy adds Cloudflare's DDoS protection on top of Clouderized's routing.

Step 3 — Verify and go live

DNS changes can take a few minutes to propagate — usually under 5 minutes, up to 24 hours in rare cases

Back in the portal Domains tab, click Verify next to your domain. The portal checks that your DNS CNAME points to the right place.

Verified — you're live

Your domain is routing to your app with HTTPS. Open it in a browser to confirm.

No CNAME — DNS hasn't propagated yet

Wait a few minutes and try again. If it keeps failing after 30 minutes, double-check the record in your DNS provider.

HTTPS is automatic. There's nothing extra to configure — your domain gets a valid TLS certificate the moment it starts routing through Clouderized.

Multiple domains

You can add more than one custom domain to the same app. All domains will serve the same container — useful for www and non-www variants, or multiple brand domains pointing at one backend.

Repeat Steps 1–3 for each domain you want to add. Each gets its own CNAME record and its own HTTPS certificate.

Removing a custom domain

In the portal Domains tab, click Remove next to the domain. This stops Clouderized from routing that domain to your app. Don't forget to also delete the CNAME record in your DNS provider — otherwise visitors will see a generic error until the TTL expires.

Troubleshooting

Verify keeps failing after 30+ minutes

Check the CNAME value exactly matches what the portal shows — any extra characters or a typo will cause it to fail. You can confirm the record is live by running dig CNAME app.example.com +short in a terminal.

Domain verifies but shows a certificate error in the browser

TLS certificates are issued automatically but can take a minute or two to provision after DNS verifies. Wait 2–3 minutes and reload.

My DNS provider doesn't support CNAME on the root domain

Use www.example.com as your custom domain (CNAME on www is always supported), then set up a redirect from the root domain to www in your DNS provider's redirect/forwarding feature.

Need help?

Email us at [email protected] — include your domain name, username, and app name.

Related docs