Skip to content
Mikrom Docs

Domains and TLS

Every app gets a hostname and HTTPS

Section titled “Every app gets a hostname and HTTPS”

When you create an app, Mikrom assigns it:

<app-name-slug>.<apps-domain>

<apps-domain> is configured per platform by your operator. The name is slugified: lowercased, with non-alphanumeric runs collapsed to - (My App 1 → my-app-1). The hostname is globally unique.

On the first successful deployment:

  • mikrom-api triggers ACME certification for the hostname.
  • mikrom-router serves the app over HTTPS on that hostname.
  • Certificates renew automatically; there is nothing to manage.

You can see the assigned hostname in mikrom app deployments --name <app> output and in GET /v1/apps/{name}.

Custom domains

Section titled “Custom domains”

Bringing your own domain (e.g. app.yourcompany.com) is not self-service. There is no CLI command or API endpoint to attach an external domain to an app; the app hostname is fixed to <app-name-slug>.<apps-domain>.

The router and the API-side ACME worker already certify managed platform domains and per-app hostnames, so the certificate machinery exists — but the user-facing domain-verification flow is not implemented. Until it is, put your own domain in front of the app with an external reverse proxy or CDN that forwards to https://<app-name-slug>.<apps-domain>.

Section titled “Related”
  • Networking — ingress, the platform network, and per-app firewall rules.