> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.flyinghost.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# FlyingHost Plans and Resource Limits

FlyingHost plans are billed monthly per site. Each plan sets the CPU, memory, storage, PHP, database, and cache resources available to that site.

## Core — $29 per site/month

- 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

- 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

- 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

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

Additional bandwidth costs **$5 per 100 GB**.

## What these 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](https://flyinghost.crisp.help/en/article/php-workers-explained-1s5qdf0/).