---
title: "Suites and custom domains"
description: "Organize apps into suites with separate login directories, attach custom hostnames, and verify DNS ownership with TXT challenges."
canonical: "https://grid82.com/docs/build/suites-and-domains"
updated: "2026-11-20"
---

# Suites and custom domains

A **suite** is a workspace boundary that groups related apps under one sign-in page, one user directory, and one web address (`{suite}.grid82.app` or your custom domain).

![Studio suite overview showing Sales CRM (1) and Apps navigation item (2)](/docs/images/app/studio-overview.webp)

_A suite in the Studio showing its apps (1) and suite navigation (2)_

## When to create a separate suite

- **Separate audiences or clients.** Agencies building portals for different clients keep each client in its own suite so user directories never mix (even if the same human email is invited to two clients, those are isolated accounts).
- **Shared team login across apps.** Keep apps that belong to the same team (such as `Sales CRM`, `Client Portal`, and `Onboarding`) in one suite so members sign in once and switch apps or connect a single suite MCP server (`https://{suite}.grid82.app/mcp`).

## Custom domains

On **Pro** and **Custom** plans, you can attach custom hostnames (such as `portal.yourcompany.com`) to any suite from the suite's **Domains** tab or via [`domains.attach`](/docs/builder-api/domains/attach).

1. **Attach the hostname**

   Add your domain in the Studio. Grid82 validates that the hostname does not belong to `grid82.app`, `workers.dev`, or another active Grid82 organisation, then issues a one-time DNS TXT verification challenge.
2. **Publish the TXT verification record**

   Add the generated TXT record to your DNS zone:

   - **Name.** `_grid82-challenge.portal.yourcompany.com` (or `_grid82-challenge.<your-host>`)
   - **Value.** `grid82-verify=<token>`

   Point your hostname's CNAME or DNS routing record according to the domain setup panel in the Studio.
3. **Verify ownership**

   Click **Verify** (or call [`domains.verify`](/docs/builder-api/domains/verify)). Grid82 queries multiple public DNS resolvers (Cloudflare, Google, and Quad9) concurrently so a stale negative DNS cache never blocks activation. Once verified, the domain starts serving your suite's login page, Runtime apps, `/v1` API, and `/mcp` server under your own hostname with zero `grid82.app` URLs visible to end users.

> **Note**
>
> Published custom Interface pages still execute inside Grid82's sandboxed cross-origin frame (`pages.grid82.app`) so untrusted page scripts can never read session cookies on your custom domain.
