FiveM-aware enforcement
Validate the Control resource at startup, monitor runtime heartbeats, and keep checks light enough for busy RP servers.
Control gives FiveM owners a production API, license system, resource heartbeat monitor, and detection console for executor abuse, trigger spam, economy exploits, and server tampering.
3 active servers, 1 elevated detection stream
Platform
Validate the Control resource at startup, monitor runtime heartbeats, and keep checks light enough for busy RP servers.
Issue, suspend, expire, and monitor license keys for individual FiveM servers without exposing raw secrets in chat.
Track server name, resource version, last seen time, and stale heartbeat status from the web panel.
Capture executor attempts, injection signals, impossible movement, economy abuse, and resource tampering with timestamps.
Deployment flow
The website is the control panel. Chat A can point the FiveM resource at the production API while this site handles accounts, licenses, heartbeats, and detection records.
Create the Control organization for your FiveM community, then invite trusted staff who manage licenses and review detections.
Generate a production license for the FiveM resource, bind it to server limits, and keep the raw key visible only once.
Set the API base URL and license key in server.cfg, start the Control resource, and let heartbeat plus event logging take over.
Low-latency validation for resource startup and recurring heartbeats.
Control API secrets and signing secrets stay in Vercel, not source files.
Neon stores plans, communities, license keys, server records, detection events, and audits.
Auth-protected dashboards keep user panels and admin tools separated.
Use the dashboard to create the community and production license, then set the FiveM resource to call the live API endpoint.