technical

Use a custom domain (auto vs manual provisioning)

604 views

Bring your own domain so endpoints publish at app.yourcompany.com instead of a shared system domain. Manage domains in the dashboard under Domains (/account/domains). Custom domains are plan-gated — your plan must include the custom-domains entitlement.

Wildcard model

Each custom domain is served via a wildcard — *.yourcompany.com — so every endpoint subdomain you create on it resolves without per-record DNS edits.

Two provisioning modes

The mode is fixed when you add the domain.

Auto

You provide DNS provider credentials for the zone; Ngris provisions and manages the DNS records and issues the wildcard TLS certificate automatically via ACME DNS-01, renewing it before expiry. Supported providers include Cloudflare, AWS Route 53, DigitalOcean, Namecheap, cPanel, and Webmin. Credentials are validated against the provider before anything is saved and are stored encrypted at rest. The domain then enters pending_issuance while the wildcard certificate is minted.

Manual

You add a CNAME record yourself at your own DNS provider and upload your own TLS certificate. The domain is created in pending_cname; the dashboard shows the exact * CNAME record to add. After adding it, click Validate CNAME — once it resolves the domain advances to awaiting_cert, where you upload your certificate (PEM, with private key). No credentials are stored, so Ngris never edits records on your behalf.

Status lifecycle

A domain progresses through status pills: pending_cname, awaiting_cert, pending_issuance, issuing, and finally active. An endpoint can only be created on a custom domain once that domain is active (its certificate is live).

Ask an AI to summarise this page