Run APIs, workers, and realtime apps without managing servers.

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.

Host your app Explore runtime examples

adios.yaml · FastAPI

name: search-api
region: de

build_cmd: python -m pip install -r requirements.txt
start_cmd: python -m uvicorn app.main:app --host 0.0.0.0 --port $PORT

runtime:
  name: python@3.13
  port: 8080
  health_path: /healthz

secrets:
  DATABASE_URL: secret://DATABASE_URL

Example outcome

Run a live analytics dashboard that stays connected.

Host an Express and Socket.io process, use Redis for active counters and pub/sub, and store history in MongoDB while the platform handles routing, TLS, logs, and deploy state.

Keep real server behavior

Run WebSockets, connection pools, and long-running processes without forcing them into short-lived functions.

Bring the runtime you already use

Node.js, Python, Go, PHP, Ruby, and .NET projects keep their normal production commands.

Operate the app, not the VM

Inspect health and logs without configuring a proxy, certificate tooling, or process manager.

Why this matters

Real backends do not always fit into short-lived functions.

WebSockets, connection pools, API servers, and background workers need long-running processes, but operating those processes should not turn into a VM, proxy, and certificate project.

What changes with Adios

Run the process your framework expects

Host API servers, full-stack frameworks, WebSocket services, and background workers as managed processes with configured runtime resources and health checks.

How it works

Keep your framework. Hand off the server work.

Step 01
Choose the runtime your app already uses.
Step 02
Set build and start commands in adios.yaml.
Step 03
Run your app as a managed runtime with logs, health checks, and route state.

A real use case

Run a live analytics dashboard that stays connected.

Host an Express and Socket.io process, use Redis for active counters and pub/sub, and store history in MongoDB while the platform handles routing, TLS, logs, and deploy state.

Included in the workflow

01Node.js, Python, Go, PHP, Ruby, .NET, and Next.js examples
02Long-running runtime replicas
03Runtime health and logs
04Generated route after deploy

Start here

Run the process your application actually needs.

Bring its production commands and let Adios handle the runtime, health checks, logs, and route around it.

Host your app

Keep building

The next pieces usually connected to this one.

View all features

Managed Databases

Create Postgres, pgvector, Redis, MongoDB, MySQL, or RabbitMQ, declare the dependency in requires, and let Adios inject its connection details into the workload.

Explore →

Global Edge Routing

Traffic enters through Adios edge locations while generated routes and custom domains resolve to the promoted current release and a healthy regional replica.

Explore →

Observability & Logs

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

Explore →