AWS vs. Render vs. Fly.io: 2026 app hosting costs start with compute but rarely end there. A database, worker and bandwidth allowance can change which platform looks affordable.
The useful comparison puts complete deployments beside their operational responsibilities. These examples show where the money goes and why matching memory doesn't guarantee matching performance.
AWS vs. Render vs. Fly.io: Define a Fair Comparison
Comparable estimates need explicit workloads, regions and billing assumptions. Both examples use always-on services in US regions, with Fly.io Machines priced in Ashburn.
Figures reflect published rates checked November 9, 2026, excluding taxes, credits, domains and optional support. Fly.io estimates follow its documented 30-day convention; other figures use published monthly plan prices.
The applications are stateless: they retain no uploaded files locally. Consequently, they need no additional application disks, snapshots or object storage.
Build usage stays within included allowances, with no external logging services selected. Neither deployment includes a load balancer or redundant web replicas.
Memory requirements establish a starting point rather than a performance benchmark. Shared processors divide capacity across workloads; dedicated CPU allocations offer a different performance profile. Lightsail also leaves server administration with the developer.
How AWS, Render and Fly.io Charge for App Hosting
The platforms package infrastructure differently, which makes headline comparisons misleading.
AWS Hosting Costs: Lightsail and Managed Containers
Lightsail bundles a Linux server, public IPv4, storage and transfer. Its $5 plan includes 512 MB memory, 20 GB disk and 1 TB transfer.
AWS's managed container route requires a separate estimate. App Runner has closed to new customers and AWS recommends ECS Express Mode. Express Mode adds no service fee, though Fargate, load-balancer and networking resources generate charges.
Render Pricing: Workspace, Compute and Usage
Render separates workspace fees from each service's compute charges. Its published deployment example prices 512 MB web services and workers at $7 each on Hobby.
Current compute names describe resources: legacy Starter becomes 0.5c-512mb and Standard becomes 1c-2g.
Hobby includes 5 GB outbound bandwidth; public-internet overages cost $0.15 per GB. A free workspace therefore doesn't make paid services free.
Fly.io Pricing: Runtime, Storage and Regional Transfer
Fly.io bills running Machines per second, with no monthly platform fee. Its shared-cpu-1x configuration with 512 MB costs $3.69 for 30 continuous days in Ashburn.
Outbound traffic from North America costs $0.02 per GB. Volumes and stopped-machine root filesystems carry separate storage charges.
Managed PostgreSQL also has its own bill; running PostgreSQL independently transfers database operations to the developer.
App Hosting Cost Examples: Small App and Growing Deployment
These calculations estimate resource charges for explicitly selected configurations.
Small App: One Always-On Service Without a Database
Assume one 512 MB web service sends 50 GB monthly:
- Lightsail: $5 server plus $0 transfer overage equals $5.
- Render Hobby: $7 compute plus 45 × $0.15 equals $13.75.
- Fly.io: $3.69 compute plus 50 × $0.02 equals $4.69.
These calculations use the linked provider rates and assume no other bandwidth-consuming services. Lightsail includes disk capacity; the other configurations don't require persistent application storage.
Fly.io currently waives invoices under $5. Its $4.69 resource subtotal could therefore produce no charge if the entire invoice remains below that threshold.
Growing App: Add PostgreSQL, a Worker and Backups
Keep the web service and add one 512 MB worker. Assume 10 GB billed database storage, 200 GB total internet egress and same-region private database connections.
- Lightsail: $10 servers plus a $30 encrypted, single-node database equals $40; transfer stays within allowances.
- Render Hobby: $14 services + $19 database + $2.70 additional storage + $29.25 egress equals $64.95.
- Fly.io: $7.38 Machines + $38 database + $2.80 storage + $4 egress equals $52.18.
AWS's database includes 2 GB RAM and 80 GB storage. Render and Fly.io use 1 GB database plans.
AWS includes seven-day automatic backups; Render Hobby provides three-day recovery. Fly.io includes backups and automatic failover, whereas the selected AWS and Render databases lack standby instances.
Costs That Change the Hosting Decision
Traffic patterns and operating responsibilities can outweigh small compute differences. Egress means outbound data transfer; moving databases across regions can introduce additional network charges.
Fly.io's idle shutdown can reduce compute spending while retained storage continues billing. Staging environments, extra replicas and paid support also deserve separate budget lines.
Free access needs careful interpretation: Render discourages production use of free instances. A trial credit likewise doesn't establish an ongoing operating budget.
Keep maintenance costs separate from invoices, then calculate hours multiplied by an appropriate internal hourly rate. Include patching, deployment maintenance and recovery testing when evaluating server administration.
FAQ
Which Platform Is Cheapest for a Small Application?
Fly.io has the lowest resource subtotal in the small-app example. Lightsail costs less in the database example, although its selected database lacks automatic failover.
Does a Free Workspace Include Free App Hosting?
Render Hobby charges no workspace subscription, though paid compute remains billable. Free compute has separate restrictions, including idle shutdown for web services.
Does Stopping an App Stop All Hosting Charges?
Stopping compute doesn't necessarily stop storage or database charges. Check retained resources and other running services before assuming billing has ended.
Is AWS App Runner Available to New Customers?
AWS has closed App Runner to new customers while existing customers can continue operating services. AWS recommends evaluating ECS Express Mode for container deployments.
