# WordPress on Fly.io

Canonical: https://inetgeek.com/stacks/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 requires from the platform underneath it, and what Fly.io publishes about each. Fly.io documents 2 of the 4.

| Requirement | Fly.io | Why it matters |
| --- | --- | --- |
| 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. |
| Managed databases | Supported | Every post, option and user lives in MySQL. Without a managed database you are running, patching and backing one up yourself. |
| 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. |

- Persistent storage source: https://fly.io/docs/volumes/overview/
- Managed databases source: https://docs.fly.io/about/pricing/

## What Fly.io documents

> Setting up a WordPress application on Fly.io is quite simple. In this guide, we'll learn just how simple it is!

Source: https://fly.io/docs/languages-and-frameworks/wordpress/

### WordPress features on Fly.io

- **managed_mysql**: Not supported — If you just want to run a quick, self-managed MySQL instance on Fly.io ([source](https://fly.io/docs/app-guides/mysql-on-fly/))

## What it costs to run there

|  | Fly.io |
| --- | --- |
| Pricing model | Usage-based, no compute plan tiers; billing is pro-rated for the time resources are provisioned. |
| 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 | 17 regions |

- Pricing model source: https://fly.io/docs/about/pricing/
- When you exceed a cap source: https://fly.io/docs/about/pricing/
- Regions source: https://docs.fly.io/reference/regions/

## 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.

Written by Palash Bagchi on 2026-09-05. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

## Related

- Best hosting for WordPress: https://inetgeek.com/stacks/wordpress/
- Fly.io: https://inetgeek.com/hosting/fly-io/