FMCache
Deploy and manage FiveM asset caching instances on Cloudflare's global network.
FMCache is currently in beta.
FMCache is a FiveM asset caching service built on Cloudflare's global network. It accelerates FiveM resource delivery by routing asset requests through Cloudflare's edge, reducing load on your origin server and improving download times for players.
How it works
Each FMCache instance is identified by a unique routing token stored in Cloudflare D1. When traffic arrives at the edge for your FQDN, the token is used to route the request to your origin server. Usage metrics are recorded in Cloudflare Workers Analytics Engine and surfaced in the dashboard.
Requirements
- You must be signed in with an AuroraHosts account.
- You must have at least one active FMCache product on your WHMCS billing account.
- If you manage multiple WHMCS client accounts, select the correct one using the Billing Account selector in the sidebar.
Deploying an instance
- Click FMCache in the sidebar.
- Select the billing client that holds your FMCache subscription using the sidebar selector.
- Click New Instance.
- Enter the fully-qualified domain name (FQDN) the FiveM server will use, e.g.
assets.example.com. - Click Deploy.
PhotonDash registers the instance in Cloudflare D1 and generates a 64-character hex routing token. The token is displayed in the dashboard.
The FQDN must be a valid domain name — IP addresses and bare URLs are not accepted. The number of instances you can create is determined by your FMCache subscription quota (see below).
Viewing analytics
Each instance shows a 7-day rolling analytics chart with three metrics:
| Metric | Description |
|---|---|
| Edge hits | Requests served from the Cloudflare edge |
| R2 hits | Requests served from Cloudflare R2 storage |
| Misses | Requests that could not be served from cache and hit your origin |
Analytics data is fetched from the Cloudflare Analytics Engine SQL API and cached in-process for 60 seconds (configurable via ANALYTICS_CACHE_TTL_SECONDS) to avoid hitting Cloudflare API rate limits.
Deleting an instance
- On the FMCache page, find the instance you want to remove.
- Click the Delete button next to it.
- The token is revoked in Cloudflare D1 and the instance is removed from your dashboard.
Deletion is permanent. Once the token is revoked, traffic for that FQDN will no longer be routed. Update your DNS or FiveM configuration before deleting to avoid disruption.
Quota and limits
Your maximum number of instances equals the sum of the quantity (qty) field across all Active FMCache products on your WHMCS account. For example:
- One FMCache × qty 2 = 2 instance slots
- Two FMCache × qty 1 each = 2 instance slots
The quota is re-checked from WHMCS each time you load the FMCache page. If you need more capacity, purchase additional FMCache products from the billing dashboard.