Grid82
grid82.comJoin the waitlist
BuildSuites and domains

Suites and custom domains

Organize apps into suites with separate login directories, attach custom hostnames, and verify DNS ownership with TXT challenges.

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)

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.

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.

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.

Verify ownership

Click Verify (or call 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.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.