Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gateways.app/llms.txt

Use this file to discover all available pages before exploring further.

Gateways vs Fly.io

Fly.io runs your containers and machines close to users on Fly’s network, with a strong story for global apps and low-latency placement. Gateways does not replace a container scheduler; it orchestrates the cloud primitives you already use (instances, scaling groups, databases, DNS, functions) across AWS, Azure, and GCP with a canvas and API.
TopicGatewaysFly.io
Unit of workCloud resources & connections in your accountsFly Machines, volumes, regions on Fly
Cloud breadthAWS + Azure + GCP in one product mapFly platform + optional integrations
Ideal userPlatform teams standardizing on hyperscalersTeams optimizing global process/container placement
Use Fly.io when Fly’s runtime and network match your app model. Use Gateways when the source of truth is your enterprise cloud footprint and you need one map for people and automation. Compare hub · Resource types