NUTRISYNCBuilders Hub
🏠 🛠
NUTRISYNC · Roadmaps · 19 Jul 2026

enterprise.setup — Corporatisation Roadmap-Backlog

Todo bajo cuentas propiedad de NutriSync, con el modelo 3+1 y 2FA en el 100%. Fuente completa: doc 19 (fases P0–P8).

Principles

Company-owned accounts everywhere · 3 founders + interim technical super-admin (Juanjo → future CTO, handover checklist ready) · 2FA mandatory on every account · every credential + recovery code in a team password vault · personal accounts out of the critical path.

Phases

Phase Scope Key risk / gotcha
P0 Legal data (CIF), 4 admin identities, choose password vault Vault first — highest value of the whole plan
P1 Google Workspace on the domain + shared Drive (backup target) ⚠ Email hosting decision: move MX from IONOS or keep IONOS mail
P2 GitHub org + transfer nutrisync-app/nutrisync-web ⚠ Cloudflare Pages GitHub App must be re-connected after transfer; re-point clone remotes; verify rulesets
P3 Cloudflare → company identity + 3 members as Admins Verify Zero Trust / Pages / DNS untouched
P4 Supabase org ownership + roles; service_role vault-only Add founders to public.admins for KPIs/feedback
P5 Expo org + project transfer + robot token Verify eas update channel with a test OTA
P6 Apple Organization enrollment (D-U-N-S) + Play company account Org (not individual) so the store says NutriSync
P7 IONOS to company identity + auto-renew; future vendors company-first Registrar lapse = domain death
P8 Verification: all deploys E2E, Access login, mail, backups, 4× logins, vault complete Nothing is done until P8 passes

Pending decisions (founders)

Email hosting (IONOS vs Google) · vault choice · org name on GitHub/Expo.