Domains & TLS

Every web service on Helicarrier Cloud is reachable over HTTPS from the moment it deploys. You get a generated hostname for free and can attach your own custom domains whenever you are ready.

Generated hostnames

When a web service deploys, it is assigned a hostname automatically — something like your-service.on.helicarrier.xyz. It works immediately over HTTPS, which is perfect for previewing and internal use before you wire up a real domain.

Custom domains

To serve your service on your own domain:

1. On the service’s Networking (Domains) tab, add your hostname (for example, app.example.com).
2. Create the DNS record your DNS provider requires, pointing your domain at Helicarrier.
3. Watch the status move from pending to securing to active.

You can add several domains to one service and remove them at any time.

Automatic TLS

Helicarrier provisions TLS certificates automatically — there is nothing to upload or renew. Certificates are issued on demand at the first request to a hostname, and renewed for you. Your services are always served over HTTPS.

Note

If your domain is proxied through Cloudflare (the orange cloud), verification is Cloudflare-aware: because Cloudflare terminates the connection, the platform cannot always confirm ownership by DNS alone. Follow the guidance shown when you add the domain if it stays in securing — usually a matter of DNS mode or a moment for propagation.

Private services

Not everything should be public. A private service (see Service types) has no public domain — it is reachable only by your other services over the internal network. Use it for internal APIs and backends.

Next

• Link services and inject URLs with Service references.
• Confirm traffic is healthy in Runtime logs.