Ship the app you already have with one repeatable release path.

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.

Deploy an existing app Follow the quickstart

adios.yaml

name: dashboard
region: de
replicas: 2

build_cmd: pnpm build
start_cmd: pnpm start

runtime:
  name: node@24
  port: 3000
  health_path: /api/health
  memory_mb: 1024

Example outcome

Move an existing dashboard from a local folder to a live route.

Add the runtime commands and health path, run adios up, inspect build and runtime logs, then confirm the promoted version behind the generated route.

Keep deployment decisions beside the code

Teammates can review how the app builds and runs without opening a cloud console.

Follow the same path for every release

Source, build, replicas, health, and promotion stay connected.

Keep the evidence when something fails

Each version retains its build output, runtime logs, artifacts, and release state.

Why this matters

A small app should not require a pile of release infrastructure.

Build scripts, runtime settings, health checks, deploy logs, and release promotion often end up scattered across CI files and cloud consoles that are hard to reproduce or review.

What changes with Adios

One manifest carries your app from source to a healthy release

Describe the runtime once, deploy the current source, and follow the same build, health-check, and promotion path from the CLI or workspace.

How it works

One path for the first deploy and every release after it.

Step 01
Add an adios.yaml manifest to your project.
Step 02
Run adios up or deploy from the console.
Step 03
Follow build logs, runtime logs, health checks, and release promotion from one place.

A real use case

Move an existing dashboard from a local folder to a live route.

Add the runtime commands and health path, run adios up, inspect build and runtime logs, then confirm the promoted version behind the generated route.

Manifest-based build and start commands

Runtime versions tied to source artifacts

Health checks and release promotion

Build and runtime logs from the CLI or dashboard

Connected pathReady

01
Source
Upload current files
02
Build
Create a versioned artifact
03
Health
Verify running replicas
04
Promote
Move the current route

Start here

Take the app in front of you live.

Add one manifest, run adios up, and keep the full release path visible when you ship again.

Deploy an existing app

Keep building

The next pieces usually connected to this one.

View all features

CLI & Local Development

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.

Explore →

Managed App Hosting

Use the build and start commands your framework already expects. Adios runs the app as a long-lived managed process with replica health, logs, release state, and public routing.

Explore →

Observability & Logs

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

Explore →