Deploy Your App

Kizaki deploys the same application shape you build locally: Inspire schema, committed migrations, generated artifacts, and server functions.

The best way to think about deploys is promotion, not translation. You are taking the same application model you have already been working with locally and moving it into a hosted environment.

Recommended Deploy Flow

kizaki login
kizaki secrets set STRIPE_SECRET_KEY sk_live_...
kizaki deploy --env staging
kizaki deploy --env production

The deploy pipeline should be treated as:

1. compile
2. validate migration state
3. apply the intended schema change
4. publish the new app version

That is why the docs emphasize generated surfaces, migrations, and environment configuration before deployment. A clean deploy comes from using those pieces as part of normal development, not as last-minute release chores.

Environments

Use environments to separate work:

• staging for previewing changes
• production for live traffic

Store environment-specific values with kizaki secrets.

For most teams, staging should be the first cloud target. It is the right place to verify auth flows, routes, billing setup, and environment-specific credentials before a production launch.

Before You Deploy

Confirm that:

• migrations are committed
• server functions are exposed intentionally
• secrets are configured for the target environment
• the browser app calls generated client functions rather than hard-coded endpoints

Recommended First Deployment Path

1. deploy to staging
2. verify the core app flow end to end
3. configure production secrets
4. deploy to production

For the command-level reference, see CLI Overview and Deploy And Operations.