starter.wikiSearch⌘K

Region-placed application Machines

Fly.io

A platform for running application Machines with explicit lifecycle, regional placement, networking, and attached volumes.

Visit official site

Editorial verdict

Choose Fly.io when Machine lifecycle and region placement are product requirements and the team can own capacity, storage, networking, scaling, and recovery.12

Best for

  • Explicit Machine resources and lifecycle
  • Deliberate region placement
  • Teams prepared to operate volumes, health, and scaling
12

Not ideal for

  • Teams wanting a framework-managed path
  • Applications assuming automatic multi-region state or failover
  • Unverified capacity, storage, transfer, or recovery requirements
12
Main trade-off

Runtime and placement control increase together with responsibility for capacity, networking, volumes, scaling, recovery, and cost.12

Product boundary

Whether explicit Machines and regional placement justify greater infrastructure ownership.

Fly.io supplies Machines, application networking, and volumes; it does not guarantee application-level multi-region durability or operate a Kubernetes control plane.12

For: Teams needing conventional runtimes and explicit Machine/region control

  • Regional capacity is unavailable.
  • The team cannot own volume and failover design.
  • A higher-level service or request container satisfies the workload.

Why teams consider Fly.io

  • Machine controlMachine lifecycle and resources are explicit.12
  • Regional placementMachines can be placed in selected available regions.12
  • Conventional runtimesApplications run in VM-like Machines rather than a framework-specific function contract.12

Pricing

Usage-based Machine resources plus volumes, snapshots, transfer, IP, and support dimensions.2

Region-placed workload

Pay-as-you-go Machines

Model Machine size and state, region, hours, volumes, snapshots, transfer, and IPs.2

Machine state
Running and stopped resources have different charges2
Regional boundary
Capacity and transfer can vary by region2
Pricing checked View official pricing

Fly.io vs alternatives

Railway

Choose when
Choose a higher-level persistent-service workflow.
Compared with Fly.io
Railway exposes less direct Machine control.45

Google Cloud Run

Choose when
Choose request-driven managed containers.
Compared with Fly.io
Direct Machine lifecycle and conventional persistence are reduced.67

Amazon ECS

Choose when
Choose AWS-native service orchestration.
Compared with Fly.io
Capacity providers, IAM, networking, and AWS cost add a broader surface.89

Resources and sources

Official product, policy, and pricing

  • Fly Machines overview
    Open
  • Fly.io pricing
    Open
  • Fly.io regions
    Open

Related tasks

  1. 1
    Fly Machines overview

    Fly.io · Accessed Official

  2. 2
    Fly.io pricing

    Fly.io · Accessed Official

  3. 3
    Fly.io regions

    Fly.io · Accessed Official

  4. 4
    Railway services

    Railway · Accessed Official

  5. 5
    Railway pricing

    Railway · Accessed Official

  6. 6
    What is Cloud Run

    Google Cloud · Accessed Official

  7. 7
    Cloud Run pricing

    Google Cloud · Accessed Official

  8. 8
    Amazon ECS overview

    Amazon Web Services · Accessed Official

  9. 9
    Amazon ECS pricing

    Amazon Web Services · Accessed Official