Skip to main content
Cutovers run in this order: lowest risk first. Marketing page groups flip through the gateway instead (see the gateway Worker page). Each section is the whole runbook for one app; the linked packet has the full binding, secret and variable names.

Web apex pin

Full rollback for the apex tuturuuu.com (Vercel project platform, apps/web): dpl_FZuaw8J2RRS3ust79agjwyKo2AAf (source d209d72b). The current production deployment is dpl_9NxJS4nsCaYZwEjSWe2bJwj2Hjdk (prebuilt from a7826c1f). Pins read 9 Nov 23:40.

Common steps

  1. Record the source SHA, the sealed artifact (CI run id) and the Vercel rollback pin below.
  2. Download the artifact: gh run download <run-id> -R tutur3u/platform -n <artifact-name> -D /tmp/<app>-cutover. Take the run id from a run on the production ref (main) at the accepted source SHA, and verify the run’s head SHA. Never take an artifact by name alone: a name can match a pull-request run.
  3. Secrets: set TUTURUUU_APP_COORDINATION_SECRET on every Worker to EXACTLY the value of Web’s signer (the SUPABASE_SECRET_KEY value) and also set the same SUPABASE_SECRET_KEY. Drive, Mind and Rewise refuse requests when TUTURUUU_APP_COORDINATION_SECRET is unset, so leaving it unset is not an option. The dedicated signing value comes later through the accept-only slot (see the app-coordination secret rollout page).
  4. Provision the secret names from the packet on the Worker, then deploy the artifact config route-free: bunx wrangler deploy --config /tmp/<app>-cutover/dist/server/wrangler.json --name <worker> (no route yet).
  5. Smoke the Worker on its own hostname before any route change: node scripts/cutover-smoke.mjs <app> https://<worker-hostname>.
  6. Attach the route or custom domain for the host (proxied, in front of the still-valid Vercel origin where possible).
  7. Re-run the smoke on the public host and watch for 5 minutes: no 5xx, login renders, entry route as expected.
  8. Rollback on any 5xx above 1% for 5 minutes, a wrong redirect or a broken login: remove the route or repoint the DNS record to the Vercel pin. Never rebuild on the rollback path. No data or migration is involved.

1. shortener

2. tools

3. storefront

4. external

5. rewise

6. drive

7. teach

8. tasks

9. track

10. finance

11. calendar

12. mail

13. apps

14. learn

15. chat

14. infrastructure

15. mind

Not cut over tonight

  • playground: no Vercel deployment found; staff-only app, routes attach at its own hostname when wanted.
  • colab: already on Cloudflare; Start/Void port is a separate change.
  • parley: already on Cloudflare (OpenNext).
  • contacts: stays on Vercel (a client uses it daily); its conversion needs its own rehearsed rollback.
  • mastermind: held by the wave-2 security hold.
  • learn, chat, infrastructure, mind, hive: sources merged; packets exist but production artifact jobs and Vercel pins are still to capture.

Hive

cms

ai

Forms

  • infrastructure, mind, hive: sources merged; packets exist but production artifact jobs and Vercel pins are still to capture.
  • learn, chat, hive: sources merged; packets exist but production artifact jobs and Vercel pins are still to capture.

16. git

Inventory

nova

pay

workspace