Domains & routing

The platform lives entirely under patternyard.dev, a Vercel-registered domain on Vercel Edge (DNS is auto-managed — there is no external nameserver step). Each surface gets its own subdomain, mapped to a Vercel project.

Subdomain map

Subdomain	Project	Serves
patternyard.dev + www.	patternyard-home	The home / community site
studio.	patternyard-studio	The editor
api.	patternyard-backend	The backend API (projects, accounts, assets)
packager.	patternyard-packager	Project → HTML/exe packager
extensions.	patternyard-extensions	Extension gallery + manifests
docs.	patternyard-docs	Product documentation
library.	patternyard-library	Costumes, sounds, backpack, project assets

How the subdomains were attached

Each subdomain was added to its project with:

vercel domains add <subdomain>.patternyard.dev <project> \
  --scope team_1A5hxCsAnX5KFLm69oklRZWB

Because the domain is Vercel-registered and on Vercel Edge, DNS records are created automatically — there is no separate registrar step.

Why the split matters

The editor (studio.) and home (apex) being different origins is the single most consequential routing fact. It means:

• Credentialed editor → backend calls must be on the backend’s CORS allowlist (the allowlist includes both studio. and the www/apex home origin).
• The editor cannot read the home session directly; it uses the cross-origin /embed/editor login bridge.
• Auth callback URLs and email links must point at the right origin — the backend builds these from its ApiURL / HomeURL / StudioURL env vars, not hardcoded hosts.

See the environment reference for exactly which variable points where.