CLI Overview

The public CLI surface is organized into a few clear jobs:

• init and dev for local development
• compile and migrate for schema workflows
• deploy, env, secrets, and logs for environments and operations
• login, keys, and api-keys for access control

Recommended Way To Think About The CLI

The CLI is the developer control surface for the platform:

• project creation
• local runtime orchestration
• schema validation and migration planning
• deployment and operational access

Use the command-group pages below for the exact workflows.

The Typical Lifecycle

For most apps, the CLI journey looks like this:

1. init to start the project
2. dev while building locally
3. compile and migrate as the schema evolves
4. deploy when the app is ready for staging or production
5. secrets, env, logs, keys, and api-keys once the app is running in shared environments

That progression is why the docs separate the CLI into job-oriented reference pages rather than a flat command list.