Deploy Your App

Deploying with Kizaki is promotion, not translation. You take the same Inspire schema, committed migrations, generated artifacts, and server functions you built locally and move them into a hosted environment.

Before You Deploy

Run a short checklist:

kizaki compile --check         # validate schema
kizaki migrate status          # ensure migrations are committed
kizaki secrets list --env staging  # verify secrets are set

The compile check catches schema errors before they reach the deploy pipeline. Migration status confirms every schema-affecting change has a committed migration. The secrets list shows whether the target environment has the credentials it needs.

Also confirm that:

• Server functions are exposed intentionally (review your @expose declarations).
• The browser app calls generated client functions rather than hard-coded endpoints.
• OAuth credentials and payment keys are set for the target environment.

Your First Deploy

kizaki login
kizaki deploy --env staging

On the first deploy to an environment, the platform creates the application with a confirmation prompt. After confirmation, the pipeline runs:

1. Compile the Inspire schema.
2. Bundle server functions and generated artifacts.
3. Upload the bundle to the target environment.
4. Apply any pending migrations.
5. Reload the application.

Pending migrations are applied automatically as part of the deploy. You do not need to run kizaki migrate apply separately in hosted environments.

After Deploying

Watch the logs to verify the deployment:

kizaki logs --env staging --tail

Visit the staging URL and walk through the core flow: authentication, a few reads and writes, any payment or email integration. Confirm everything behaves as expected outside of local development.

The Default Environment

kizaki deploy without --env defaults to production. Once your workflow is established this is convenient, but for early deploys, be explicit:

kizaki deploy --env staging     # explicit target
kizaki deploy                   # defaults to production

Use --env staging until you are confident in your deploy workflow and ready to go live.

Deploying To Production

Same command, different secrets:

kizaki secrets set STRIPE_SECRET_KEY "sk_live_..." --env production
kizaki secrets set GOOGLE_CLIENT_ID "..." --env production
kizaki secrets set GOOGLE_CLIENT_SECRET "..." --env production
kizaki deploy --env production

The application code does not change between staging and production. Only the secrets and database differ. What worked in staging works in production because it is the same application.

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.

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

Related Reference

For the full set of deploy flags, environment management, and operational commands, see Deploy And Operations.