Skip to main content

Domains and network

One subdomain per project​

URLWhat
q3-variance.apps.contoso.comA project's production
q3-variance--d7f3a2.apps.contoso.comAn immutable preview of deployment d7f3a2
console.apps.contoso.comThe console and its /api
mcp.apps.contoso.comThe MCP endpoint for AI assistants
auth.apps.contoso.comThe sign-in callback

Using -- instead of nested subdomains means one wildcard certificate (*.apps.contoso.com) covers everything. Only the Edge holds the certificate and terminates TLS; it routes by host name.

Setting up DNS (self-hosted)​

The preferred setup is one request to your DNS team, once: delegate apps.contoso.com (NS records) to the Azure DNS zone vastframe installs. After that the Hub creates records and renews the wildcard certificate itself. No ticket per project.

Fallbacks, in order:

  1. The DNS team won't delegate: create one wildcard CNAME *.apps.contoso.com pointing to the Edge, and upload a wildcard certificate into Key Vault. vastframe reminds you before it expires.
  2. No wildcards allowed at all: path mode, apps.contoso.com/q3-variance/. The Edge strips the prefix and sets TC_BASE_PATH. Some single-page apps with hard-coded absolute asset paths break in this mode, which is why it's a fallback.
  3. Nothing from the DNS team yet: start on a temporary vastframe-provided domain and switch later.
Availability

Automatic DNS records and certificate renewal on Azure, path mode and custom per-project domains are coming soon. On the local stack, *.apps.localhost resolves to your machine and needs no DNS.

Network exposure (self-hosted)​

Chosen at install time:

OptionBehaviour
Identity-protected public (default)The Edge is reachable from the internet, but every request needs sign-in through your identity provider, so Conditional Access applies. Works from phones and the Teams mobile app
Private onlyThe Edge has an internal IP and is reachable over VPN or ExpressRoute only

Reaching on-premises systems​

On-premises systems such as SQL Server and file shares are reached through VNet peering into your network. Only the Integration Gateway connects to them, with credentials held by the platform.

Reserved paths​

Every app origin reserves /_tc/* for the platform: sign-in (/_tc/auth/*), the Data API (/_tc/db/*), storage (/_tc/storage/*) and integrations (/_tc/int/*). Don't serve your own routes there.

Was this page helpful?