The website, store and status page your FiveM server deserves.
Heartbeat-driven live status, opt-in player lists, VIP and priority queue delivered in-game after a confirmed payment, and Discord roles that follow the purchase.
A status page players trust
The resource sends a heartbeat every 30 seconds: status, player count, max players, queue length and uptime. Your public server page and Discord embed stay current so "is it up?" stops being a question.
VIP and priority queue, delivered in-game
A purchase becomes an entitlement only when Stripe's webhook confirms it. The resource polls pending grants, applies ACE or framework permissions and acknowledges each by id — applied exactly once, revoked on refund.
Privacy by default
Exact positions are never public. Players opt in to the player list; the public map shows zone counts with a minimum threshold; admins see detail only if the server enables it.
ESX, QBCore or custom
A small adapter reports character and job when you want it to. Everything else is framework-agnostic Lua that never blocks the game thread.
Up and running in an afternoon
- Create a workspace and add your community and game server.
- Download the resource, set the API key and server id as convars in server.cfg.
- Create VIP and Priority Queue products with FiveM and Discord deliverables.
- Share your server page and let the store, roles and automations run.
“Priority queue used to be a spreadsheet and a staff member. Now it is a webhook.”
Illustrative — the platform is new and we would rather show you than quote you. Ask for a walkthrough.
Read the playbooks
New guides every other day on the blog: growth, monetization, automation and sponsorships.