Fly.io Cost and Capacity Review

Overview

Optimize from measured usage and the current pricing page, not copied monthly constants. Separate running and stopped Machine charges, persistent volume and snapshot charges, network and IP costs, and Managed Postgres resources that live outside application deletion.

Prerequisites

• Billing window, currency, organization, apps, and cost owner
• Machine state and resource history plus traffic, latency, and availability objectives
• Inventory of volumes, snapshots, IPs, transfer, builders, and Managed Postgres clusters

Instructions

Step 1: Reconcile the bill to resources

Map each charge class to current Machines, volumes, snapshots, addresses, transfer, builders, and databases. Include unattached and stopped-resource dependencies.

Step 2: Measure utilization and state