Adios

Build & Deploy
Production Software

Adios gives engineering teams one platform to review code, run previews, manage infrastructure, inspect logs, handle secrets, and deploy healthy releases. Whether a change comes from a developer or an AI agent, it stays connected to source and Git history.

Start buildingExplore the platform

Plans from $10/month.

From source to production

From source change to healthy release, in one system.

Code, configuration, previews, logs, health checks, and deployment stay connected. Your team can review what changed, run it before release, and see exactly what is serving production.

01

Review real source

Start with an existing Git repository, local project, or template. Every change lands in files your team can inspect, test, and commit.

02

Verify before release

Build and preview the app with its production commands. Use logs and health checks to catch issues before it goes live.

03

Define how it runs

adios.yaml keeps build commands, runtime settings, resources, secrets, regions, and routes beside the code.

04

Trace every deployment

Keep the source revision, build output, runtime logs, health status, and live route tied to the same release.

Application configuration

Define how your application runs.

adios.yaml keeps build commands, startup behavior, health checks, resources, regions, and secret references beside the source. The same reviewed configuration follows the application from preview to production.

  • ✓One deployment contractKeep build, start, port, health, and resource settings in one file that your team can review with the code.
  • ✓Secrets outside GitCommit the secret names your application expects while Adios provides their values securely during the build or at runtime.
  • ✓Healthy releases go liveAdios builds the source, starts the application, checks its health endpoint, and makes the release live only after it reports healthy.
adios.yaml
name: node-api
region: de
replicas: 2

build_cmd: npm ci && npm run build
start_cmd: node dist/server.js

runtime:
  name: node@24
  port: 8080
  memory_mb: 1024
  health_path: /healthz

secrets:
  DATABASE_URL: secret://DATABASE_URL
adios-demo.mp4

Use AI where the source and deployment context already live.

Connect an MCP-capable AI client to scoped Adios tools. The client can inspect workspace files, propose edits, run builds, open previews, read logs, and request approval-sensitive deploy actions through the same project boundary as the web app.

  • ✓Source-backed changes: inspect files and Git state before accepting an AI-generated edit.
  • ✓Preview evidence: run commands, follow build output, open the preview, and read runtime logs.
  • ✓Controlled release: keep deploys and destructive actions behind explicit approval.
Explore Adios MCP

Build and manage the full application surface

Node.jsPythonGo.NETRubyPHP
Next.jsDjangoFlaskExpressLaravelReactVueAngularSvelte
PostgresRedisRabbitMQMongoDBMySQLWorkflows

Deployable starters

Deploy a starter, then customize it.

Start from official Adios templates for web apps, API backends, databases, caches, and queues. Deploy in the console or clone locally and run adios up.

View all deployment paths
Web apps

Next.js

4 variants

JavaScript and TypeScript Next.js starters using npm or pnpm and Adios runtime config.

Next.jsNode.jsnpmpnpmTypeScript
$ cd template-nextjs
$ adios up
Deploy nowView deployment
Web apps

Supabase-connected Node.js

1 variant

A Node.js 24 starter connected to an existing Supabase project with secret-backed configuration.

SupabaseNode.js 24PostgreSQLnpm
$ cd templates/nodejs/supabase
$ adios up
Deploy nowView deployment
Web apps

WordPress

1 variant

WordPress 7.0.1 on PHP 8.3 with managed MySQL, generated salts, and persistent wp-content.

WordPress 7.0.1PHP 8.3MySQL 8Persistent
$ cd templates/php/wordpress
$ adios up
Deploy nowView deployment
Web apps

Strapi

1 variant

Strapi 5 on Node.js 24 with managed PostgreSQL, generated secrets, and persistent uploads.

Strapi 5Node.js 24PostgreSQL 17Persistent
$ cd templates/nodejs/strapi
$ adios up
Deploy nowView deployment
API starters

Python API

8 variants

FastAPI, Django, Flask, Litestar, and Sanic starters with production start commands.

PythonFastAPIDjangoFlaskLitestarSanic
$ cd template-python-fastapi
$ adios up
Deploy nowView deployment
API starters

Ruby apps & APIs

5 variants

Rails, Sinatra, Grape, Hanami, and Roda starters with Bundler and Adios config.

RubyRailsSinatraGrapeHanamiRoda
$ cd templates/ruby/rails
$ adios up
Deploy nowView deployment
API starters

PHP apps & APIs

6 variants

Laravel, Symfony, CakePHP, CodeIgniter, Yii, and PHP 8.2 starters.

PHPLaravelSymfonyCakePHPCodeIgniterYii
$ cd templates/php/laravel
$ adios up
Deploy nowView deployment
API starters

Go API

5 variants

Gin, Chi, Echo, Fiber, and Beego starters with compiled production binaries.

GoGinChiEchoFiberBeego
$ cd templates/go/gin
$ adios up
Deploy nowView deployment
API starters

.NET apps & APIs

6 variants

ASP.NET Core, Blazor, ABP, FastEndpoints, Orchard Core, and .NET 8 starters.

.NETC#ASP.NET CoreBlazorABPOrchard Core
$ cd templates/dotnet/aspnet-core
$ adios up
Deploy nowView deployment

Platform capabilities

One platform from source to production.

Keep development, infrastructure, and operations connected instead of rebuilding the release path across separate tools.

🌐

AI workspaces with source control

Let the AI agent work inside your actual project—not a disposable sandbox. Review every file change, preview the result, and keep the work in Git.

🚀

Deployments tied to source

Define how the app builds, starts, and reports health in adios.yaml. Each release stays connected to its source, logs, health status, and live route.

🖥️

Hosting for full-stack applications

Run APIs, WebSockets, background workers, and long-lived services without operating servers, proxies, or certificates.

⚡

Databases and application services

Add Postgres, pgvector, Redis, MongoDB, MySQL, or RabbitMQ and connect them to the application without placing credentials in source.

🔄

Workflows you can inspect

Run scheduled jobs, webhooks, approvals, and multi-step processes with visible status, logs, inputs, outputs, and errors.

🌍

Global routing and domains

Route traffic through the Adios edge network, attach custom domains, and keep TLS and the live release connected as versions change.

Workflow example

Automate backend work without losing visibility.

Define triggers, secret references, and ordered steps in YAML. Each run keeps its status, logs, inputs, outputs, and errors, so your team can see exactly what happened.

Daily market brief

This example runs every weekday or from a webhook, then turns market data into a brief for an internal dashboard.

  1. 01

    Trigger

    Run on a weekday schedule or start from a webhook.

  2. 02

    Process

    Fetch price data and select the fields the next step needs.

  3. 03

    Publish

    Send the brief to an internal dashboard and keep every step attached to the run.

Explore workflowsRead the workflow docs
workflows/daily-market-brief.yaml
workflow_id: daily-market-brief
enabled: true

triggers:
  - type: cron
    cron: "0 13 * * 1-5"
  - type: webhook
    event: market.brief.requested

secrets:
  MARKET_DATA_API_KEY: secret://MARKET_DATA_API_KEY

steps:
  - step_id: fetch-prices
    kind: http
    command:
      method: GET
      url: https://api.example.com/quotes
      headers:
        Authorization: "Bearer secret://MARKET_DATA_API_KEY"

  - step_id: select-close
    kind: data-json
    dependencies: [fetch-prices]
    command:
      from_step: fetch-prices
      path: ".quotes"

  - step_id: publish-brief
    kind: http
    dependencies: [select-close]
    command:
      method: POST
      url: https://dashboard.example.com/api/market-briefs
2 triggers3 visible stepsSecret-backed API access

Before you start

Know what stays connected after the first build.

Can I bring an existing repository to Adios?

Yes. Start from an existing Git repository or local project, add the runtime contract the app needs, then use previews, logs, and health checks before deployment.

Does AI-generated code stay reviewable?

AI-assisted changes land in project files where the team can inspect the diff, run checks, open a preview, and decide what to commit or deploy.

What kinds of workloads can Adios run?

Adios supports web applications, APIs, long-running workers, WebSockets, workflows, and data-service templates across Node.js, Python, Go, .NET, Ruby, and PHP ecosystems.

What happens when a candidate release is unhealthy?

The build and runtime evidence remains available for inspection. The candidate must report healthy before it becomes the promoted release serving the application route.

Choose the capacity your apps need

Plans start at $10 per month. Choose the compute, storage, bandwidth, and included AI usage that fit your apps. Final terms and availability are shown at checkout.

Starter

For a first app, small API, or personal workspace.

$10/mo

  • 1 vCPU and 1 GB RAM
  • Deploy apps within plan resource limits
  • Built-in AI assistant and web editor
  • Git and CLI deploys
  • Custom domains and TLS
  • 10 GB storage
  • 500K included AI tokens
  • 500 GB included bandwidth
Choose Starter
POPULAR

Dev

For active development across several apps.

$50/mo

  • 2 vCPU and 4 GB RAM
  • Deploy apps within plan resource limits
  • AI assistant, workspaces, and previews
  • Database deployments with backups
  • Custom domains and TLS
  • 50 GB storage
  • 2.5M included AI tokens
  • 2 TB included bandwidth
Choose Dev

Pro

For production projects that need more headroom.

$99/mo

  • 4 vCPU and 8 GB RAM
  • Deploy apps within plan resource limits
  • AI assistant, workspaces, and previews
  • Database deployments with backups
  • Custom domains and TLS
  • 100 GB storage
  • 5M included AI tokens
  • 5 TB included bandwidth
Choose Pro