Custom access domains

A custom access domain serves a workspace's Stackyapper portal and MCP endpoint from a hostname your organization controls, such as stackyapper.example.com.

Custom access domains are included with Business. For an MSP-managed customer workspace, the customer identity package supplies that customer's separate identity configuration and custom access domain. Without that package, the customer workspace uses the MSP's canonical access instead of a separate hostname.

Before you start

You need:

A Business subscription or an active customer identity package
Workspace owner access
Permission to create a CNAME record in the hostname's DNS zone

Choose a dedicated hostname that is not already serving another application. Stackyapper manages the TLS certificate after the DNS record is detected.

Set up the domain

Open the Stackyapper portal and select the intended workspace.
Open Settings and go to Identity & access.
Under Custom access domain, select Set up domain.
Enter the complete hostname you want to use.
Add the CNAME record shown in the portal:
- Type: CNAME
- Name: the custom hostname
- Target: copy the exact target displayed by Stackyapper
Return to the portal and select Check now, or leave the page open for automatic checks.

No TXT verification record is required. Do not substitute a different CNAME target or point the hostname directly to an IP address.

Verification states

Stackyapper reports routing and certificate progress separately:

Waiting for DNS: the expected CNAME has not been detected.
Hostname routing ready: Stackyapper can route the hostname to the workspace.
Certificate issuing: DNS is ready and the TLS certificate is being created automatically.
Verified: portal and MCP traffic are served from the custom hostname.
Needs attention: review the displayed error, correct DNS if needed, and select Check now again.

DNS propagation and certificate issuance can take several minutes. Keep the CNAME record in place after verification.

Use the verified hostname

After verification:

Open the workspace portal from https://<your-hostname>.
Use the MCP URL shown under AI clients → Connection URLs when configuring a client.
Prefer the portal-displayed URL over constructing an endpoint manually.

The hostname is bound to one workspace. Stackyapper resolves the workspace again for each request; a custom hostname does not broaden membership, app access, or tool grants.

Change or remove a domain

To replace a hostname, remove the existing custom access domain in Identity & access, then set up the replacement. Update AI clients after the new hostname is verified.

Removing the domain returns the workspace to its canonical Stackyapper access. Remove the obsolete DNS record after the portal confirms the domain has been removed.

Troubleshooting

If verification does not complete:

Confirm the DNS record is a CNAME with the exact name and target shown.
Remove conflicting A, AAAA, or CNAME records for the same hostname.
If your DNS provider flattens CNAME records, confirm it still publishes the expected target.
Select Check now after DNS changes have propagated.

If the portal reports a persistent routing or certificate error, contact support with the workspace name, hostname, approximate time, and displayed error. Do not send DNS-provider credentials or Stackyapper session data.