Start with a deployable app, not an empty repository.

Choose a ready-to-deploy app, API, or data-service starter with adios.yaml already included. Deploy it from the console or clone the source and make it yours.

Browse templates Read the template guide

adios.yaml · Next.js starter

name: nextjs-app
runtime:
  name: node@24
  port: 3000
build_cmd: npm install && npm run build
start_cmd: npm start

Example outcome

Start a webhook receiver without a full-stack framework.

Clone the Fastify starter, confirm its health route and production command, deploy it, then add signature verification and durable event storage.

Skip repetitive framework setup

Start with a production command, runtime port, and health path already connected.

Choose the workload you actually need

Browse web, API, database, cache, and queue starters across supported runtimes.

Own the result after launch

Inspect locally, use Git, open it in a workspace, and keep deploying the same project.

Why this matters

The first useful feature should not wait for repetitive setup.

An empty repository still needs framework wiring, production commands, a runtime port, health checks, and deployment configuration before anyone can test the idea.

What changes with Adios

Start with the framework and deployment contract already connected

Choose a ready-to-deploy app, API, database, cache, or queue template and begin with runnable source plus the manifest Adios needs to deploy it.

How it works

Choose a starter, make it yours, keep deploying it.

Step 01
Pick a starter template.
Step 02
Deploy it from the console or clone it locally.
Step 03
Open it in a workspace and customize it with code or the AI agent.

A real use case

Start a webhook receiver without a full-stack framework.

Clone the Fastify starter, confirm its health route and production command, deploy it, then add signature verification and durable event storage.

Web, API, database, cache, and queue starters

Multiple runtime and framework variants

adios.yaml included

Console deploy and local clone paths

Connected pathReady

01
Web apps
Next.js and full-stack starters
02
APIs
Python, Go, Ruby, PHP, and .NET
03
Databases
Postgres, MySQL, and MongoDB
04
Services
Redis and RabbitMQ

Start here

Begin with something that already runs.

Pick the closest starter, deploy it, and spend the next hour changing the product instead of rebuilding boilerplate.

Browse templates

Keep building

The next pieces usually connected to this one.

View all features

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 →

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 →

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 →