Custom Domains

Coming soon

Custom domains are not yet available. The details below describe the planned feature. We will update this page — including the setup steps — when the feature ships.

Keelson will let you serve a deployed app from your own subdomain, such as app.example.com, in addition to the standard public URL Keelson issues for every app.

Planned scope

• Plan: Team plan only
• Limit: Up to 10 per tenant in total (one domain per app)
• Supported domains: Subdomains only (app.example.com). Root domains (apex, example.com) and email domains are out of scope.

When to use it

• Publish an internal tool under your own company domain
• Give users a clear URL instead of the standard Keelson URL
• Match URLs with an existing internal portal or site

Difference from the public URL

A standard public URL is always issued on a successful deploy. A custom domain lets the same app also be reached through your own subdomain. Access-control rules are unchanged: any authentication or IP restriction you have enabled applies to custom-domain traffic as well.

Setup steps (provided when the feature ships)

The concrete setup steps — the DNS records to add, how to verify them, and how TLS certificates are handled — will be documented here when the feature becomes available.