Add the database, cache, or queue your app needs without leaving the app workflow.

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

Build a data-backed app Explore database examples

adios.yaml excerpt

name: realtime-dashboard
runtime:
  name: node@24
  port: 8080

requires:
  - db
  - cache
  - queue

Example outcome

Build a realtime dashboard with live and historical data.

Run the Node.js service as a persistent process, connect Redis for active counters and MongoDB for event history, and keep both dependencies visible beside the app.

Choose storage that fits the job

Use relational data, vector search, document storage, caching, pub/sub, or queues without forcing everything into one service.

Keep dependencies explicit

The app manifest shows which managed resources the workload expects.

Connect without copying credentials around

Required connection details are injected into the application environment.

Why this matters

The application is only one part of a working backend.

Storage, caches, queues, connection credentials, and persistence are often provisioned elsewhere, leaving the relationship between the app and its data services implicit.

What changes with Adios

Connect the app to databases, caches, and queues by dependency

Create a supported managed resource, link it in the application manifest, and let Adios inject its connection details into the workload.

How it works

Create the resource, declare the dependency, run the app.

Step 01
Create a managed data resource from a supported template.
Step 02
Reference it from your app manifest or workspace.
Step 03
Deploy the app with connection secrets and dependency wiring.

A real use case

Build a realtime dashboard with live and historical data.

Run the Node.js service as a persistent process, connect Redis for active counters and MongoDB for event history, and keep both dependencies visible beside the app.

Postgres and pgvector for relational and AI search apps

Redis for caching, sessions, pub/sub, and live buffers

MongoDB and MySQL templates

RabbitMQ for queue-backed systems

Connected pathReady

01
Postgres
Relational data and vectors
02
Redis
Cache, sessions, and pub/sub
03
MongoDB
Document workloads
04
RabbitMQ
Queued background work

Start here

Give the application the stateful services it actually needs.

Create a database, cache, or queue, link it in the manifest, and keep the dependency attached to the workload.

Build a data-backed app

Keep building

The next pieces usually connected to this one.

View all features

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 →

Workflows & Automation

Define webhook, event, schedule, or manual triggers and ordered steps in YAML. Each run keeps its status, logs, inputs, outputs, and errors after the original request ends.

Explore →

Secrets & Environment Variables

Commit secret:// references so required credential names remain visible while their values are stored separately, then resolved for the runtime or workflow that needs them.

Explore →