Tenkit

Use Tenkit only at project birth, when the user already knows they will ship the same Expo app under several brands — it decides the multi-tenancy model up front, and retrofitting one of these Setup Types onto an existing Expo app is far more work than starting over. Make the user choose between White Label (App Store listing per brand, EAS project per variant, slow release cadence) and Runtime Tenant (one binary, tenant chosen at runtime, instant onboarding) before you run anything; the CLI takes --setup and --styling flags so you can scaffold non-interactively with `pnpm create tenkit@latest --name x --setup white-label --styling unistyles --yes`. It is a scaffold, not a UI kit — it gives you variant plumbing, Expo Router and theming, so pair it with your own component library. Note it is young (30 stars) and pinned to Expo SDK 57; check the repo before assuming SDK compatibility. It publishes markdown mirrors and an llms.txt, so read those rather than the JS-rendered /configure page.

Why it is here. White-labelling an Expo app is a solved-in-private problem that almost nobody has open-sourced; Tenkit names the three architectures explicitly and generates the native identity plumbing that teams normally hand-roll and get wrong.