Custom Domains

Every service deployed on the platform gets a default subdomain. You can also attach your own custom domains with automatic SSL certificates.

Default Subdomain

Every service automatically receives a subdomain on the platform domain. No DNS configuration is required — it works immediately after deployment.

Default subdomain format

{your-subdomain}.rouic.com

For example, a service with the subdomain my-app would be accessible at my-app.rouic.com.

Adding Custom Domains

Add custom domains through the dashboard:

Navigate to your project

Open the Dashboard and select your project.

Open domain settings

Go to Settings → Domains.

Add your domain

Enter your custom domain and click Add. The platform will provide the DNS records you need to configure.

Domain Types

The platform supports two types of custom domains:

Apex Domain

The root domain without any prefix, e.g. example.com. Requires an A record pointing to the platform server IP.

Subdomain

Any prefix on your domain, e.g. www.example.com or app.example.com. Can use either an A record or a CNAME record.

DNS Setup

Configure your DNS provider with one of the following record types, depending on your domain type:

Option A: A Record (apex or subdomain)

Point your domain directly to the platform server IP address.

A record

dns

Type:  A
Name:  example.com (or subdomain)
Value: YOUR_SERVER_IP
TTL:   Auto

Option B: CNAME Record (subdomains only)

Point your subdomain to your service's default platform domain.

CNAME record

dns

Type:  CNAME
Name:  www (or your subdomain prefix)
Value: {your-slug}.rouic.com
TTL:   Auto

SSL Certificates

SSL certificates are provisioned automatically via Traefik and Let's Encrypt. No manual configuration is required.

Custom Domains

Certificates are issued using the HTTP-01 challenge. The platform automatically handles the challenge and renewal. Your DNS must be correctly pointing to the server before a certificate can be issued.

Wildcard Platform Domain

The wildcard certificate for *.rouic.com is issued using the DNS-01 challenge via Cloudflare DNS.

Domain Verification

When you add a custom domain, the platform checks that DNS resolution is correctly configured before activating the domain. This ensures that SSL certificate provisioning will succeed.

The platform performs the following checks:

Resolves the domain via DNS to verify it points to the platform server
Validates that the resolved IP matches the expected server address
Once verified, Traefik automatically provisions the SSL certificate

DNS propagation can take up to 48 hours depending on your provider, though it typically completes within minutes.

Primary Domain

When a service has multiple domains, you can set one as the primary domain. The primary domain is displayed in the dashboard and used as the canonical URL for your service. You can change the primary domain at any time from Settings → Domains.

Multiple Domains

Each service supports multiple custom domains. All domains receive their own SSL certificate and route traffic to the same running container. This is useful for serving the same application under different brand domains or regional domains.

Cloudflare Users

If you use Cloudflare as your DNS provider with the proxy enabled (orange cloud), you must configure the SSL/TLS mode correctly to avoid redirect loops.

Important: Set SSL mode to "Full"

In your Cloudflare dashboard, navigate to SSL/TLS and set the encryption mode to Full(not "Flexible"). Using "Flexible" mode will cause infinite redirect loops because the platform enforces HTTPS on all connections.

Cloudflare SSL/TLS setting

Cloudflare Dashboard -> SSL/TLS -> Overview
Encryption mode: Full (recommended)

Do NOT use:
- "Flexible" -> causes redirect loops
- "Full (Strict)" -> requires a valid origin cert (also works if you have one)

WWW Redirect

The platform does not automatically redirect between www and apex domains. You can configure this redirect using one of the following approaches:

Option 1: Cloudflare Page Rules

Create a page rule in Cloudflare to redirect www.example.com/* to https://example.com/$1 with a 301 permanent redirect (or vice versa).

Option 2: Application-Level Redirect

Handle the redirect in your application code or framework middleware. For example, in a Next.js middleware.ts, check the host header and redirect accordingly.