Deployments
Deploy from source to production without wiring cloud tools together.
Use adios.yaml and the Adios control plane to build, start, health-check, and promote app runtimes.
The hook
Why developers care
Small apps still end up with CI scripts, Docker decisions, cloud consoles, deploy logs, health checks, and release steps scattered across different tools.
How Adios handles it
- 1Add an adios.yaml manifest to your project.
- 2Run adios up or deploy from the console.
- 3Follow build logs, runtime logs, health checks, and release promotion from one place.
What you get
Platform pieces that make this work.
Manifest-based build, lint, and start commands
Runtime versions tied to source artifacts
Health checks and release promotion
Build and runtime logs from the CLI or dashboard
Build path
Ship an existing app with one manifest.
Point Adios at a local project, set runtime commands, add secrets, and promote the healthy version behind the generated route.
Deploy your first app on Adios.
Start with this feature, then add the rest of the platform as your app needs it.
Keep exploring
AI Coding Workspaces
Use the Adios agent inside a source-backed workspace, then inspect, edit, preview, commit, and deploy the code it creates.
Managed App Hosting
Run long-lived app processes for common runtimes while Adios handles routing, logs, health, regions, and deploy state.
Global Edge Routing
Adios routes public traffic through managed gateways so generated routes, custom domains, versions, and replicas stay tied together.