FlyingHost plans and resource limits
FlyingHost plans are billed per site, with monthly or yearly billing. Each plan sets the CPU, memory, storage, PHP, database, and cache resources available to that site.
Monthly billing is selected by default when creating a site. With yearly billing, you pay for 10 months and get 2 months free. Resource limits are the same for both billing cycles.

Lite
$19 per site/month or $190 per site/year.
- 1 dedicated high-frequency CPU core
- 2 GB RAM
- 5 GB storage
- 4 PHP workers
- 256 MiB MariaDB buffer pool
- 64 MiB Redis memory
- 256 MiB OPcache memory
Core
$29 per site/month or $290 per site/year.
- 2 dedicated high-frequency CPU cores
- 4 GB RAM
- 10 GB storage
- 8 PHP workers
- 512 MiB MariaDB buffer pool
- 128 MiB Redis memory
- 256 MiB OPcache memory
Growth
$49 per site/month or $490 per site/year.
- 4 dedicated high-frequency CPU cores
- 6 GB RAM
- 30 GB storage
- 18 PHP workers
- 1 GB MariaDB buffer pool
- 256 MiB Redis memory
- 256 MiB OPcache memory
Pro
$99 per site/month or $990 per site/year.
- 8 dedicated high-frequency CPU cores
- 12 GB RAM
- 75 GB storage
- 24 PHP workers
- 2 GB MariaDB buffer pool
- 512 MiB Redis memory
- 384 MiB OPcache memory
Scale
$199 per site/month or $1,990 per site/year.
- 12 dedicated high-frequency CPU cores
- 20 GB RAM
- 150 GB storage
- 36 PHP workers
- 4 GB MariaDB buffer pool
- 1 GB Redis memory
- 512 MiB OPcache memory
Bandwidth
Every plan includes 100 GB of bandwidth per month. This monthly allowance applies to both monthly and yearly hosting plans.
Additional bandwidth costs $5 per 100 GB.
What the plan limits mean
- Dedicated high-frequency CPU cores: CPU cores reserved exclusively for the site, with 5 GHz+ boost speeds for consistent performance.
- RAM: Memory shared by WordPress, PHP, MariaDB, Redis, and other site services.
- Storage: Disk space available to the site.
- PHP workers: Maximum concurrent dynamic PHP requests.
- MariaDB buffer pool: Memory used to cache frequently accessed database data and indexes.
- Redis memory: Memory available for WordPress object caching.
- OPcache memory: Memory used to store compiled PHP code.
When choosing a plan, consider PHP concurrency, CPU and memory usage, and storage together. More workers help with concurrent dynamic traffic, but they do not make a single slow request faster.
For help diagnosing capacity limits, see PHP workers explained.
Updated on: 12/11/2026
Thank you!