Skip to content
Mengi Cloud Mengi Cloud Docs

Custom Domains (DNS)

Every deployment gets a free public address like https://<id>.apps.mengi.cloud. To serve your app on your own domain (e.g. app.example.com), you do two things once:

  1. Connect your DNS provider on the DNS page.
  2. Point a deployment at your domain from the deployment’s settings.

Mengi then creates the DNS record for you and keeps it in sync — including automatic HTTPS.

1. Connect your DNS provider

On the DNS page, click Add credential and:

  1. Choose your provider — Bunny.net, Cloudflare, AWS Route 53, or DigitalOcean.
  2. Give it a name (optional).
  3. Paste the provider’s API credentials (an API key/token for most providers; an access key + secret for AWS Route 53).
  4. Save. Mengi validates the credential and shows whether it’s valid.

That’s it — you don’t enter your domain names by hand. Mengi discovers the domains your account manages directly from the provider, so they’re ready to pick when you configure a deployment.

Keep the credential valid. If the API key is later rotated or revoked, Mengi can’t update your records until you reconnect it.

2. Point a deployment at your domain

Open a deployment’s Custom Domain settings (available both in the New deployment wizard and on an existing deployment) and:

  1. Pick a base domain from the dropdown — these are the domains discovered from your DNS credential.
  2. Optionally type a subdomain. For example app + example.com → app.example.com. Leave the subdomain empty to use the domain root.

Save, and Mengi creates the DNS record pointing at your deployment and keeps it in sync. To remove a custom domain later, set it back to None — the record is removed automatically.

  • HTTPS is automatic — a TLS certificate is issued and renewed for your custom domain, with nothing to configure.
  • Custom domains require a dedicated cluster. On shared regions the option isn’t offered; deploy to (or create) a dedicated cluster to use one.

No DNS provider connected yet? The custom-domain field is disabled with a link to the DNS page so you can add one first.

3. Health check (optional)

When configuring the custom domain you can add a health check:

  • None — just publish the record.
  • HTTP — Mengi checks your app over HTTP.
  • Ping — Mengi checks reachability.

When a health check is set, Mengi monitors the target and steers DNS away from an unhealthy deployment, where your DNS provider supports it.

4. Run the same domain in multiple regions

To make a domain resilient across regions, deploy your app to two or more dedicated clusters and give each deployment the same custom domain. Mengi publishes a record for each region and balances traffic and fails over between them automatically — so if one region goes down, the domain keeps serving from the others.

Good to know

  • You don’t need a custom domain to go live — every app already has an *.apps.mengi.cloud URL with automatic HTTPS.
  • Custom domains run on dedicated clusters only.
  • One DNS provider credential can serve any of the domains it manages — you don’t add a separate credential per domain.