WordPress on Fly.io
Fly.io publishes its own guide for deploying WordPress.
PHP content management system that requires a database and persistent filesystem for uploads and plugins.
What WordPress needs.
Every host claims to run WordPress, so the claim on its own decides nothing. These are the things WordPress actually requires from the platform underneath it, and what Fly.io publishes about each. Fly.io documents 2 of the 4.
Persistent storage
Supported
Uploads, themes and plugins are written to disk while the site is running. A host that resets the filesystem on every deploy loses them.
Sources (1) →Sources ↓
- Fly Volumes overview · Fly Docs ↗
“Fly Volumes are local persistent storage for Fly Machines.”
Read 2026-09-05 · official docs
Managed databases
Supported
Every post, option and user lives in MySQL. Without a managed database you are running, patching and backing one up yourself.
Sources (1) →Sources ↓
- Fly.io pricing ↗
“The price of running Fly.io Managed Postgres depends on your selected Managed Postgres Plan and the amount of storage your Postgres cluster has.”
Read 2026-09-05 · official docs
Storage (entry plan)
Not documented
A media library grows steadily and is almost never pruned. Disk is the cap a WordPress site reaches first.
Monthly visits cap
Not documented
Managed WordPress plans meter traffic rather than CPU, so the visit ceiling is the real size of the plan you are buying.
What Fly.io documents.
Fly.io publishes its own guide for deploying WordPress.
Setting up a WordPress application on Fly.io is quite simple. In this guide, we'll learn just how simple it is!
Sources (1) →Sources ↓
- Run a WordPress App · Fly Docs ↗
“Setting up a WordPress application on Fly.io is quite simple. In this guide, we'll learn just how simple it is!”
Read 2026-09-05 · official docs
What it costs to run there.
- Pricing model
- Usage-based, no compute plan tiers
- When you exceed a cap
- No plan cap to exceed — Fly bills per second for provisioned resources. The only documented enforcement is unspecified automated scaling limits, which surface as an error message (platform-wide, all plans)
- Regions
- 18 regions
Sources (2) →Sources ↓
- Fly.io pricing ↗
“Plans get complicated, so we just charge based on usage. Billing is based on the resources provisioned for your apps, pro-rated for the time they are provisioned.”
Read 2026-09-05 · official docs
- Fly.io regions ↗
“You can host your apps in any of the following regions — including ams (Amsterdam, Netherlands), nrt (Tokyo, Japan) and syd (Sydney, Australia).”
Read 2026-09-05 · official docs
Whether it suits you.
Workloads that ship as Docker images and need placement in particular regions. Billing is purely usage-based with no plan tiers, which suits spiky or region-pinned traffic better than a flat monthly fee.
Consider something else if…
You want a predictable flat bill rather than charges that track the resources provisioned for each app.
Visit Fly.io documentation