Software · head to head
Fly.io vs Packer
The short version
- Each has a real cost: Fly.io egress is priced by destination region, from $0.02 per GB in North America and Europe to $0.12 per GB for Africa and India, so the same traffic costs six times more depending on where users are; Packer packer 1.10.0 and later is licensed under the Business Source License 1.1 with IBM Corporation as licensor, not an OSI open source licence
- They diverge on capability: Fly.io covers Global deployment, Packer covers Image building.
Where they differ
Only the attributes on which Fly.io and Packer actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Unknown).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Fly.io
- Global deployment
- Docker support
- Postgres databases
- Redis support
- Auto-scaling
- Health checks
- Backups
- Monitoring
Only in Packer
- Image building
- Multi-platform support
- Provisioners
- Builders
- Post-processors
- Variables
- Data sources
- Validation
Both cover
- Docker
- Cloud deployment
What people use each for
The jobs each tool is most often brought in to do.
Fly.io
- Deploying containerised applications close to users across regionsnot Packer
- Running full stack apps and databases on managed machinesnot Packer
Packer
- Building identical machine images for multiple clouds from one templatenot Fly.io
- Baking golden AMIs and VM images into a CI pipelinenot Fly.io
- Creating immutable infrastructure artifacts consumed by Terraformnot Fly.io
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Fly.io
- Egress is priced by destination region, from $0.02 per GB in North America and Europe to $0.12 per GB for Africa and India, so the same traffic costs six times more depending on where users are
- Stopped machines still bill at $0.15 per GB of root filesystem a month, so a paused service is not a free one
- Volumes are billed on provisioned capacity rather than usage, at $0.15 per GB a month
- Reservation discounts of 40% require paying a year up front, from $36 to $1,440
- Fly Kubernetes is a separate $75 a month per cluster
- Dedicated IPv4 addresses are $2 a month each
Packer
- Packer 1.10.0 and later is licensed under the Business Source License 1.1 with IBM Corporation as licensor, not an OSI open source licence
- The Additional Use Grant forbids offering Packer to third parties on a hosted or embedded basis in a paid product that competes with IBM's paid versions of Packer
- Each version converts to the MPL 2.0 Change License only four years after that version is first published, and the Change Date is set separately per version
- Alternative licensing for uses outside the grant must be arranged with the licensor rather than taken under the public licence
Pricing, plan by plan
Fly.io
Free- FreeFree
- 3 shared-cpu-1x VMs
- 3GB persistence storage
- 160GB outbound data/month
- Pay-as-you-goFree
- Unlimited applications
- Dedicated machines
- Global deployment
Packer
Free- Open SourceFree
- Multi-platform image building
- Template-driven
- Provisioner support
Which should you pick?
Choose Fly.io if
- You need global deployment.
- You want to start without paying.
- You work on Web, Api, Docker.
- You also want docker support.
Choose Packer if
- You need image building.
- You want to start without paying.
- You work on Linux, Windows, Mac.
- You also want multi-platform support.
Questions people ask
- Is Fly.io or Packer better?
- Neither clearly leads. Fly.io starts at Free and Packer at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Fly.io or Packer?
- Fly.io starts at Free and Packer at Free.
- Does Fly.io or Packer run on more platforms?
- Fly.io runs on Web, Api, Docker. Packer runs on Linux, Windows, Mac.
- Can I use Fly.io for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Fly.io best used for?
- Fly.io is most often used for deploying containerised applications close to users across regions, running full stack apps and databases on managed machines. Of those, deploying containerised applications close to users across regions and running full stack apps and databases on managed machines are not what Packer is typically brought in for.
- What can Fly.io do that Packer cannot?
- Fly.io covers Global deployment, Docker support, Postgres databases, Redis support. Packer covers Image building, Multi-platform support, Provisioners, Builders. Both handle Docker, Cloud deployment.
Related pages
Keep looking
Other head to heads
- Fly.io vs Grafana Cloud
- Fly.io vs Neon
- Fly.io vs DigitalOcean
- Fly.io vs AWS (Amazon Web Services)
- Fly.io vs Lambda (AWS Serverless)
- Fly.io vs Deno Deploy
- Fly.io vs Heroku
- Fly.io vs Hetzner Cloud
- Fly.io vs Linode
- Fly.io vs Pulumi
- Fly.io vs Render
- Fly.io vs Upstash
- Fly.io vs Vagrant
- Fly.io vs Vultr
- Fly.io vs Akamai
- Fly.io vs Alibaba Cloud
- Fly.io vs Chef
- Fly.io vs Contabo
- Packer vs Grafana Cloud
- Packer vs Neon
- Packer vs DigitalOcean
- Packer vs AWS (Amazon Web Services)
- Packer vs Lambda (AWS Serverless)
- Packer vs Deno Deploy
- Packer vs Heroku
- Packer vs Hetzner Cloud
- Packer vs Linode
- Packer vs Pulumi
- Packer vs Render
- Packer vs Upstash
- Packer vs Vagrant
- Packer vs Vultr
- Packer vs Akamai
- Packer vs Alibaba Cloud
- Packer vs Chef
- Packer vs Contabo

