Every site starts on a free *.devani.studio address. When you're ready to put it on your own (or a client's) domain, you attach it in the dashboard (or via the API) and point DNS at us. Cloudflare then issues and serves the HTTPS certificate automatically — there's nothing to renew.
Two ways to handle the DNS
Attaching a domain always produces the DNS records that need to exist. The only question is who creates them:
- You add them manually — works on any DNS provider (GoDaddy, Namecheap, Route 53, Cloudflare). We show you the records; you paste them. No credentials shared. This is the universal default.
- We add them for you (Whitelabel) — if your domains are on Cloudflare and you've connected a scoped token, we create the records in your zone automatically when you attach a domain. Zero-touch.
Both end the same way: the domain validates, the cert issues, and it goes live on HTTPS in a few minutes.
Good to know
- Subdomains are easiest (
www.client.com,app.client.com) — a clean CNAME that works everywhere. A bare apex (client.com) needs your provider's CNAME-flattening/ALIAS support (Cloudflare does it automatically). - No downtime risk during setup — nothing changes for visitors until the records resolve.
- Already pointed elsewhere? Changing the records is the cutover. With the automatic (token) path, if a conflicting record already exists we ask you to confirm before replacing it, so a live domain is never repointed by surprise.
- The certificate is fully managed by Cloudflare at the edge — no Let's Encrypt renewals on your side.