CLI
Deploy, sync, inspect logs, and manage resources from the Adios CLI.
Keep your terminal workflow while Adios handles deploys, logs, workspaces, databases, secrets, and source sync.
The hook
Why developers care
Developers who live in the terminal should not have to click through cloud consoles just to deploy, read logs, or push workspace changes.
How Adios handles it
- 1Install and log in with the adios CLI.
- 2Run adios up from a local app or sync with a workspace.
- 3Manage logs, databases, workflows, domains, and secrets from commands.
What you get
Platform pieces that make this work.
adios up for local deploys
adios logs for build and runtime output
workspace sync and pull commands
database, workflow, domain, and secret commands
Build path
Keep building locally, then deploy when ready.
Make changes in your editor, run adios up, inspect logs, and sync back with an Adios workspace when you need the web IDE.
Deploy your first app on Adios.
Start with this feature, then add the rest of the platform as your app needs it.
Keep exploring
AI Coding Workspaces
Use the Adios agent inside a source-backed workspace, then inspect, edit, preview, commit, and deploy the code it creates.
Adios Deployments
Use adios.yaml and the Adios control plane to build, start, health-check, and promote app runtimes.
Managed App Hosting
Run long-lived app processes for common runtimes while Adios handles routing, logs, health, regions, and deploy state.