Adios
CLI

Keep your editor and terminal. Add a direct path to production.

Use the Adios CLI to deploy the current directory, read build and runtime logs, manage platform resources, and sync source both ways with a workspace.

Install the CLIRead the CLI reference
Terminal
adios login --browser
adios up

adios logs --build
adios logs --runtime

adios sync
adios sync --pull

Example outcome

Take an existing repository live, then keep working locally.

Log in, run adios up, inspect build and runtime logs, open the attached source in a workspace, and use adios sync in either direction.

01

Deploy what is in front of you

adios up uploads the current source, reads its manifest, builds it, starts replicas, and promotes a healthy release.

02

Operate without console hopping

Read logs and manage apps, databases, secrets, domains, routes, and workflows with focused commands.

03

Move between local and web workflows

Push local changes into a linked workspace or pull workspace files back to your editor.

Why this matters

A terminal-first workflow should not end at the cloud console.

Deploying, reading logs, managing resources, and moving changes between local and web environments often means abandoning the tools developers use for the rest of the day.

What changes with Adios

Keep the local tools you like and add a direct path to production

Use one CLI for login, source deploys, logs, workspace sync, databases, secrets, domains, and workflow operations.

How it works

Work locally, inspect the result, move source in either direction.

  1. Step 01

    Install and log in with the adios CLI.

  2. Step 02

    Run adios up from a local app or sync with a workspace.

  3. Step 03

    Manage logs, databases, workflows, domains, and secrets from commands.

A real use case

Take an existing repository live, then keep working locally.

Log in, run adios up, inspect build and runtime logs, open the attached source in a workspace, and use adios sync in either direction.

01

adios up for local deploys

02

adios logs for build and runtime output

03

workspace sync and pull commands

04

database, workflow, domain, and secret commands

Connected pathReady
  1. 01

    Local source

    Your editor and Git workflow

  2. 02

    adios sync

    Shared workspace files

  3. 03

    Preview

    Stable workspace runtime

  4. 04

    adios up

    Healthy production release

Start here

Take the current directory all the way to a healthy release.

Install the CLI, deploy from the project root, and keep logs, resources, and workspace sync in the terminal.

Install the CLI

Keep building

The next pieces usually connected to this one.

Adios Deployments

Keep the build, start, health, region, and resource contract in adios.yaml. Running adios up turns the current source into a version and promotes it when the deployment is healthy.

Explore →

AI Coding Workspaces

Adios gives developers and AI agents a shared, source-backed workspace. Team members can edit and review code, run builds, open preview environments, inspect logs, and decide what moves to production. Git state, secrets, runtime configuration, and deployment controls stay connected to the project.

Explore →

Observability & Logs

Build logs, runtime logs, source artifacts, versions, replica health, routes, and workflow runs stay connected in the same deployment path.

Explore →