Custom domain & HTTPS

Serve the ERP on a domain you own. You add the domain, verify it by DNS, and the platform issues and renews the HTTPS certificate for you.

Add and verify a domain

Each company has one white-label domain at a time. Saving a new one replaces the old and (re)starts verification.

  • Enter your domain (for example app.yourcompany.com) and save. Its status becomes Pending.
  • At your DNS provider, point the domain at the platform: a CNAME to the target we show is preferred (it survives server-IP changes), or an A record to the server IP.
  • Press Check. On a match the domain flips to Active; otherwise it shows Failed so you can fix the record and try again.
Re-checks are throttled. The Check button has a short cool-down between attempts, so give DNS a moment to propagate before retrying.

HTTPS is automatic

Once a domain is Active, the platform sets up its web-server entry and issues a free Let’s Encrypt TLS certificate, then renews it automatically before it expires. You do not manage certificates yourself.

Your Google Maps key

Google Maps keys are locked to a specific host, so the platform’s key will not work on your domain. Add your own Maps JavaScript API key on the White-label tab; it is used only when the ERP is served on your domain. Leave it blank and maps simply fall back to manual coordinates.

Tip. To stop serving on a domain, clear the field and save — the domain is disabled and the ERP is reached on the main host again.
On this page
Docs

Frequently asked questions

One white-label domain is active per company. Saving a different domain replaces the current one and starts a fresh verification.

No. Once the domain verifies, the platform issues and auto-renews a Let's Encrypt HTTPS certificate for it.

Google keys are host-locked. Add your own Google Maps key on the White-label tab; the platform key only works on the main ERP host.