Edge Routing
Put your app behind a managed global gateway.
Adios routes public traffic through managed gateways so generated routes, custom domains, versions, and replicas stay tied together.
The hook
Why developers care
Public routing usually means learning DNS, TLS, proxies, route health, regional failover, and release cutovers before your app is even useful.
How Adios handles it
- 1Deploy an app and get a generated route.
- 2Promote the current runtime version.
- 3Let the gateway route traffic to healthy replicas and current releases.
What you get
Platform pieces that make this work.
Generated adios.run routes
Gateway-before-runtime traffic model
Versioned releases and current promotion
Replica and route health state
Build path
Route traffic without running your own proxy stack.
Deploy a webhook API or realtime app, then let Adios keep the public route pointed at the current healthy runtime.
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.
Adios Deployments
Use adios.yaml and the Adios control plane to build, start, health-check, and promote app runtimes.
Managed App Hosting
Run long-lived app processes for common runtimes while Adios handles routing, logs, health, regions, and deploy state.