Adios
← PLATFORM / Global Edge Routing

One public route. A connected network.

The Adios gateway sends traffic for your hostname to the promoted current release. A new deploy does not need a DNS change. Workspace previews are separate runtimes, so your agent can test changes before you promote them.

Free to start, no card. Always-on hosting from $10/month.

IN PRACTICE

Receive a European request without moving the workload.

A request can enter at the Paris edge, find the current release for the hostname, and cross the platform network to a healthy replica in Frankfurt.

Example request path

User to edge to app worker

01 / 05
Adios request pathA request from Cape Town enters through the Johannesburg edge and travels to the Frankfurt worker.London, United Kingdom · Live edgeParis, France · Live edgeAmsterdam, Netherlands · Live edgeMadrid, Spain · Live edgeFrankfurt, Germany · Live edgeLos Angeles, United States · Live edgeMiami, United States · Live edgeNew Jersey, United States · Live edgeSão Paulo, Brazil · Live edgeTokyo, Japan · Live edgeSingapore, Singapore · Live edgeSilicon Valley, United States · Live edgeMumbai, India · Live edgeChicago, United States · Live edgeSydney, Australia · Live edgeJohannesburg, South Africa · Live edgeUser · Cape Town, South AfricaWorker · Frankfurt, Germany
User Edge Worker
Map data: Natural Earth
Cape Town, South AfricaJohannesburg, South Africa edgeFrankfurt, Germany workerThis path is illustrative. Internet routing can select a different edge, and 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

    The gateway routes traffic to the current release.

WHY IT BELONGS HERE

The public route should not be rebuilt for every release.

DNS, TLS, proxy setup, route health, and release cutovers can turn into a separate system that drifts away from the app it serves.

Keep the public route stable while the app changes

Promotion moves traffic to the new release without a DNS change for each 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

The edge and the compute stay separate, and the platform network connects them.

What’s included

  • ✓ Generated platform routes
  • ✓ Traffic goes through the gateway before the runtime
  • ✓ Versioned releases and a promoted current release
  • ✓ Anycast entry points and a CDN cache

PLANS AND LIMITS

Generated routes and preview URLs are on every plan. Custom domains need Plus, Dev, or Pro.

  • Next.js static assets are cached at the edge automatically. Other apps turn on caching with cache in adios.yaml.
  • Free preview sleeps after 4 hours idle.
Compare plans →
DOCSRead the routing docs

CONNECTED CAPABILITIES

Keep building.

All features ↗

YOUR NEXT DEPLOY STARTS HERE

Works on localhost? Ship it tonight.

Connect your AI, say “deploy this,” and share the link. Upgrade for production from $10/month.