Adios
← PLATFORM / Global Edge Routing

One public route. A connected network.

When your AI agent deploys a new release, the Adios gateway routes traffic dynamically without DNS downtime. Your agent can test and preview changes in isolation before you promote the new release behind your main domain.

IN PRACTICE

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.

Live request path

User to nearest edge to app worker

Updates automatically
Adios request pathA request from Toronto enters through the New Jersey edge and travels to the New Jersey worker.Dallas, United States · PlannedOslo, Norway · PlannedSydney, Australia · PlannedHong Kong, Hong Kong · PlannedPhoenix, United States · PlannedMexico City, Mexico · PlannedTel Aviv, Israel · PlannedDubai, United Arab Emirates · PlannedDublin, Ireland · PlannedHonolulu, United States · PlannedAuckland, New Zealand · PlannedKathmandu, Nepal · PlannedIstanbul, Turkey · PlannedJohannesburg, South Africa · PlannedLondon, United Kingdom · Current edgeParis, France · Current edgeAmsterdam, Netherlands · Current edgeMadrid, Spain · Current edgeFrankfurt, Germany · Current edgeLos Angeles, United States · Current edgeMiami, United States · Current edgeNew Jersey, United States · Current edgeSão Paulo, Brazil · Current edgeTokyo, Japan · Current edgeSingapore, Singapore · Current edgeSilicon Valley, United States · Current edgeMumbai, India · Current edgeChicago, United States · Current edgeUser · Toronto, CanadaWorker · New Jersey, United States
User Edge WorkerPlanned
Map data: Natural Earth
Toronto, CanadaNew Jersey, United States edgeNew Jersey, United States workerThis example moves around the world automatically. Your app settings control the real worker.

HOW IT WORKS

Publish once, then move traffic by promoting a release.

Read the guide ↗
  1. 01

    Deploy an app and get a generated route.

  2. 02

    Promote the current runtime version.

  3. 03

    Let the gateway route traffic to healthy replicas and current releases.

WHY IT BELONGS HERE

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.

Keep the public route stable while the app changes

Promotion moves traffic without a DNS change for every deploy.

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.

What’s included
  • ✓ Generated platform routes
  • ✓ Gateway-before-runtime traffic model
  • ✓ Versioned releases and current promotion
  • ✓ Replica and route health state

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.

Publish an app ↗

CONNECTED CAPABILITIES

Keep building.

All features ↗