Custom Domains

By default your service is live at something like my-app.rivendeploy.com. That's perfect for testing. But for a real product you'll want your own domain — myapp.com or app.myapp.com — so it looks professional and stays yours.

You bring the domain (from any registrar), and Riven serves your app on it with a valid HTTPS certificate, issued and renewed automatically.

To connect a domain to your service:

• Go to your service's Settings and choose Add Custom Domain.
• Enter the domain you want to use — like app.myapp.com.
• Riven shows you the DNS record to add at your registrar.

Once you add that record and it propagates, Riven verifies the domain and issues an SSL certificate automatically.

After adding the domain in Riven, you add a DNS record at wherever you bought your domain (GoDaddy, Namecheap, Cloudflare, etc.). Rivenshows you the exact record — it looks like this:

Copy the exact values from your Riven dashboard — they're specific to your service. DNS changes can take a few minutes to a few hours to propagate.

Once your DNS record is in place, Riven checks that the domain points to your service. When it verifies, Riven automatically requests an HTTPS certificate fromLet's Encrypt and installs it — no manual certificate setup.

Your domain then serves over https:// with a valid certificate that renews on its own before it expires. You don't have to touch it again.

There are two kinds of domain you might add:

• A subdomain — like app.myapp.com or www.myapp.com. These use a CNAME record and are the simplest to set up.
• A root domain — like myapp.com with nothing in front. These sometimes need a different record type depending on your registrar, since not all registrars allow a CNAME on the root.

Riven shows you the right record for whichever you add. If you're not sure, a subdomain like app.myapp.com is the easiest place to start.

The domain isn't verifying.

This is almost always DNS. Double-check the record matches exactly what your dashboard shows — the type, name, and value. Then wait; propagation can take up to a few hours depending on your registrar.

My site shows a certificate warning.

The certificate is still being issued. Once the domain verifies, the HTTPS certificate follows within a few minutes. If it persists after that, remove and re-add the domain.

I want to move the domain to a different service.

Remove it from the current service first, then add it to the new one and update your DNS record to point to the new service.