CLI authentication
Login with a CLI token, store auth locally, and keep secure access to platform APIs without opening the dashboard.
Run the full A8S workflow from your terminal with one clean CLI for authentication, setup, secrets, logs, rollout tracking, and instant recovery.
Start from the terminal with token authentication, project control, and environment setup before the first deployment.
Authenticate first, choose or create a project, then apply environment configuration before deployment.
Login with a CLI token, store auth locally, and keep secure access to platform APIs without opening the dashboard.
Create new projects, switch between existing ones, and manage platform resources directly from the terminal instead of the UI.
Manage environment variables and runtime configuration from the CLI so the next deployment picks up the updated values.
Authenticate, bootstrap, inspect, and release from one operator-friendly command surface.
Build or select a version and ship it to the chosen environment with rollout feedback directly in the terminal.
Deploy, redeploy, rollback, and inspect logs from one CLI workflow instead of bouncing back to the web UI.
Deploy an application from the terminal with the same release flow as the UI deploy button and support environment selection directly in shell.
Re-trigger the last deployment without code changes when you need a restart, a config refresh, or a quick recovery cycle.
Rollback to a previous version from the CLI and instantly redeploy the stored image without waiting for another build.
Open application logs directly in the terminal with live streaming and filtering so debugging stays close to the release workflow.
A simple CLI path for authentication, project setup, deployment, logs, and rollback.
A8S turns the daily release flow into a short CLI path your team can repeat with confidence.
Connect the workspace and load the correct project context before changing the release state.
Bootstrap the app configuration, runtime defaults, and generated project files from the CLI.
Push environment values and make sure deployments have the runtime configuration they need.
Release the app, watch rollout progress, and keep the log stream nearby until the service is healthy.