Teams, Environments, And Secrets

Once an app moves past local development, the operational workflow usually becomes:

kizaki login
kizaki env list
kizaki secrets set STRIPE_SECRET_KEY sk_live_... --env production
kizaki logs --env production --tail

This is where Kizaki starts feeling like a full platform instead of only a local development tool. The deployment surface, environment model, secret storage, and access controls should all line up with the same app you built locally.

Recommended Split

• use environments for staging, preview, and production
• use secrets for runtime credentials
• use keys for CI and automation access
• use api-keys for application-level HTTP access to your routes

Why The Vocabulary Matters

These commands solve different operational problems:

• secrets is for runtime configuration
• keys is for people or automation accessing the platform
• api-keys is for external systems accessing your app

Keeping those concepts separate helps prevent broad credentials from being reused for the wrong job.

Public Product Vocabulary

The docs use these command groups consistently:

• kizaki secrets for environment secrets
• kizaki keys for platform or CI tokens
• kizaki api-keys for app-level route access

Related Reference

• Deploy And Operations
• Auth And Access