Magic Ship

Infrastructure and deploy

Fly.io

Run containers close to users without cloud paperwork.

made by
Fly.io
source
Official Fly.io site

Magic Ship is one shop in Vancouver, BC, working remotely with clients worldwide. We are not a partner, reseller, or certified vendor of Fly.io - we just build with this.

What Fly.io is

Fly.io runs Docker images as lightweight VMs in regions you choose. It provides a private network between apps, persistent volumes, Postgres, and machines that can scale to zero and start again on request.

How we use it

We use Fly for staging and for small production services where the entire deploy story should be one config file and a push. Scale-to-zero machines are how a demo environment stays reachable for months without a bill worth discussing. Region placement is picked to sit near the database rather than near the user, since the database round trips dominate.

Where it is the wrong choice

It is a smaller vendor than the big clouds, which stops it at some procurement reviews, and volumes are attached to a single machine so durability is something you plan for deliberately. Data that must not be lost goes on managed Postgres somewhere else.

Service lines it turns up in

More in Infrastructure and deploy

  • AWSThe cloud many clients have already standardized on.
  • Cloudflare TunnelPublish a private service without opening a port.
  • Cloudflare WorkersEdge runtime for APIs, webhooks, and small services.
  • DockerThe same stack on a laptop, in CI, and in production.
  • GitHub ActionsCI that runs the same checks a developer runs locally.
  • VercelDeploy target that matches how Next.js is built.

Other tools in the same service lines

Building something on Fly.io?

Send the problem rather than a job spec. You get an answer on scope, on fit, and on whetherFly.io is even the right call for it.

Start a project

Fly.io and Fly.io are trademarks of their respective owners, used here to say what we work with.