Keep the public route stable while the app changes
Promotion moves traffic without a DNS change for every deploy.
Edge Routing
Give every release a stable global front door.
Traffic enters through Adios edge locations while generated routes and custom domains resolve to the promoted current release and a healthy regional replica.
Live request path
User to nearest edge to app worker
User Edge WorkerPlanned
Map data: Natural EarthToronto, CanadaNew Jersey, United States edgeNew Jersey, United States workerThis example moves around the world automatically. Your app settings control the real worker.
Example outcome
Receive a European request without moving the workload.
A request can enter through the Paris edge, resolve the hostname to the current release, and cross the platform network to a healthy Frankfurt replica.
Serve eligible content closer to users
The edge can return a fresh cached response without contacting a worker.
Separate the public edge from the workload
Edge ingress and compute placement remain distinct while the platform keeps them connected.
Why this matters
The public route should not be rebuilt for every release.
DNS, TLS, proxy configuration, route health, regional placement, and release cutovers can become a separate system that drifts away from the application it serves.
What changes with Adios
Keep public traffic pointed at the current healthy release
Generated routes, custom domains, release promotion, and runtime health meet at the Adios gateway, so changing an app version does not mean rebuilding your routing stack.
How it works
Publish once, then move traffic by promoting a release.
- Step 01
Deploy an app and get a generated route.
- Step 02
Promote the current runtime version.
- Step 03
Let the gateway route traffic to healthy replicas and current releases.
A real use case
Receive a European request without moving the workload.
A request can enter through the Paris edge, resolve the hostname to the current release, and cross the platform network to a healthy Frankfurt replica.
01
Generated platform routes
02
Gateway-before-runtime traffic model
03
Versioned releases and current promotion
04
Replica and route health state
Connected pathReady
- 01
Anycast
Available anycast edge
- 02
Gateway
Host and release lookup
- 03
Current
Promoted healthy version
- 04
Replica
Running application process
Start here
Put a stable route in front of your next release.
Deploy an app, promote the healthy version, and let the gateway keep public traffic connected as the code changes.
Keep building
The next pieces usually connected to this one.
Custom Domains & TLS
Declare custom hosts and whole-host redirects with the app. After DNS verification, Adios serves the TLS route and keeps the hostname attached to the promoted current release.
Explore →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 →Observability & Logs
Build logs, runtime logs, source artifacts, versions, replica health, routes, and workflow runs stay connected in the same deployment path.
Explore →