Tenkit is a toolkit for creating one mobile product built with Expo around explicit setup data: App Variants, Runtime Tenants, native identity, and Build Preparation.

Is the public create command available yet?

Yes. The current Tenkit repo includes the create-tenkit package surface, with create commands for pnpm, npm, npx, Bun, and bunx.

Does Tenkit handle backend multi-tenancy?

No. Tenkit handles project generation for apps built with Expo, native identity, setup data, and local build workflows. Your backend, billing, and admin product stay in your stack.

How do I pick a setup type?

Choose the model that matches distribution: separate App Variants per brand, one App Variant with multiple Runtime Tenants, or a hybrid where a generic App Variant coexists with selected standalone App Variants.

Why does each App Variant need its own EAS Project?

Each native app identity should own its release lane, environment values, and project ID. Tenkit maps each App Variant to exactly one EAS Project so Build Preparation can target the right native app on purpose.

CLI

create-tenkit is available now

One Codebase Many Branded Apps

Create a project built with Expo around the Setup Type you actually ship: white-label App Variants, Runtime Tenants, or a hybrid with selected standalone breakouts.

Open GitHub Setup types

$ pnpm create tenkit@latest

Proof points

The create flow is backed by real setup primitives for apps built with Expo.

Tenkit keeps the difference between native identity and runtime business context explicit, so teams can review the generated app shape before shipping it.

Open sourceMIT repo
Expo SDK 56native-ready
TypeScripttyped setup data
pnpm, npm, Bunlauncher-aware
App Variantsbuild identity
Runtime Tenantsruntime context

Setup types

Three distribution models, shown as native app shapes.

Pick the relationship between App Variants and Runtime Tenants first. Tenkit turns that choice into generated files instead of a copied app.

white-label01

White Label Apps

Separate store listing per brand.

One shared mobile product built with Expo, with each customer or brand owning its app name, icon set, bundle ID, package name, scheme, theme, and EAS project.

Brand

Variant

EAS

One app per customer
One EAS Project per App Variant
Shared product code

runtime-tenants02

Runtime Tenant App

One app, many runtime contexts.

Ship one native app identity, then let the installed app open different businesses, organizations, or locations at runtime.

App

Runtime

Switch

One native app identity
Selectable Runtime Tenants
Runtime Tenant Access bootstrap data

generic-standalone03

Generic + Standalone

A network app with selected breakouts.

Most Runtime Tenants live inside a generic App Variant. Selected brands can also ship as standalone App Variants.

Generic

Breakout

Store

Generic App Variant
Standalone App Variants
Excluded generic picker access

What gets generated

A starter project, plus a map for the real production values.

Tenkit gets the app shape into code. The useful next step is deciding which Expo and EAS service values, native identity, and product-context values replace the starter data.

Project

Starter project

A typed app scaffold built with Expo, setup data, README commands, and starter values kept easy to replace.

Commands

Launchers

The package manager you start with carries into install commands and generated next steps.

Services

EAS connection

Expo account owner, EAS project IDs, and build environments are named directly.

Reviewable

Editable setup files

App Variants, Runtime Tenants, access rules, identifiers, and themes live in TypeScript.

Native app

Native identity

Names, slugs, schemes, bundle IDs, package names, icons, splash assets, and colors are grouped together.