Static implementation guide
Two-Project Deployment Checklist
Deploy the origin before the gateway and verify environment, protection, domain, content synchronization, and asset-routing assumptions.
Last updated 2026-08-29
Prepare the shared repository
Create two separate Vercel projects from the independent Project A and Project B directories. Each project installs from its own package manifest and lockfile, so neither build needs source files from the other directory. Both builds must use the pinned Next.js release and the required Node.js major version.
Place both projects in one team before measuring transfer behavior. Confirm that the operator can manage domains and environment variables and can view usage and observability. Check the current plan and regional terms rather than relying on values copied into old notes.
Deploy origin, then gateway
Build the origin with the final public site URL and obtain its stable production hostname. Verify its robots file, a generated guide, and the gateway canonical. Then configure that stable hostname as the gateway origin, build the gateway, and attach the dedicated custom domain only to the gateway.
Deployment protection must allow the gateway to fetch the origin without returning a login document. After both releases, test the public pages, raw SEO HTML, prefixed chunks, unknown-slug 404, and repeated cache headers. Begin usage experiments only after this baseline is clean.