ZeroDev Sentinel

A server-side FiveM anti-cheat for ESX, QBCore, Qbox and standalone servers: rules that explain themselves in plain sentences, cases with the evidence, and your staff deciding what happens.

$25 once · no subscription

  • Cases with the evidence; your staff decide what happens.
  • Starts on Watch: it logs and punishes nobody until you choose a level.
  • An F7 console in game, a browser panel and Discord.

Needs OneSync and a Node 22 server artifact. oxmysql is optional. Checkout signs you in with Cfx.re, and the purchase goes to that account's Keymaster.

Sentinel

Overview

A server-side anti-cheat that shows your staff what happened, with the evidence, and lets them decide.

Sentinel records what the server sees, judges it with rules that explain themselves in plain sentences, and gives your staff the evidence before anyone is punished: positions, events, screen clips sealed with SHA-256 and a 3D replay.

It starts on Watch, where it logs what it would have done and punishes nobody. When you trust what it finds, switch to Recommended (staff get alerts and cases) or Strict (proof-level findings quarantine the player until staff look). The owner chooses what each staff member may do.

  • 3protection levels: Watch, Recommended and Strict
  • 16attacks in our lab against a live server: each caught, blocked or explained
  • 4staff roles out of the box, plus the roles you make
  • 25languages for players and staff

Sentinel

Before you buy

Everything that decides whether it fits your server, in one place.

What you get
The zerodev_sentinel resource: the detection rules, cases with evidence, the staff console, the browser panel, Discord alerts, the guard file and the install guides.
Version
0.1.2, released 13 November 2026. Release notes.
Price
$25 once, with lifetime updates.
Trial and cancelling
No trial and no monthly plan: one payment.
Frameworks
ESX Legacy, QBCore, Qbox, Standalone. Check your setup.
Needs
OneSync on and a Node 22 server artifact. Optional: oxmysql (records in your database, tables made on first start, no SQL to import); pma-voice, only for listening to voice chat.
Third-party services
None needed. Optional and yours to set: a Discord bot or webhook for alerts and appeals, and FiveManage or a Discord webhook for screen clips. Without them, cases and clips stay on your server.
Editable files
Readable after escrow: the config files and translations (config/), the framework adapters (bridge/) and the guard file (guard/guard.lua). The rest stays encrypted.
Install and updates
One folder, started after oxmysql and your framework. No config edit for the first start: the console prints a one-time owner code, you claim the seat in game and the First run sheet lists what is left.
Limits
Runs on FiveM for GTA V Legacy. Item changes are followed with ox_inventory and ESX's own inventory; with other inventories Sentinel follows money, detection and cases only.
Support
The documentation, then a private ticket in our Discord. Tickets usually get a first reply within a day. Delivery is through Tebex to your Cfx.re Keymaster.

Sentinel

See it before you buy

Things you can open and check yourself, before a trial or a purchase.

Sentinel

Compatibility

Found on start, nothing to set. The framework matters only for the money and item trail, which has its own adapter for ESX, QBCore and Qbox.

Check your setup

Pick what your server runs. Each answer comes from our test records: Verified in game means we played it; Verified means it started and passed the start-up check; Supported means a built-in adapter is included.

ZeroDev Sentinel

Framework

  • Choose your framework.

Inventory

  • Choose your inventory.

Voice

  • Choose your voice.
Test records and setup
  • ESX Legacy
  • QBCore
  • Qbox
  • Standalone

server.cfg

Copy the zerodev_sentinel folder into resources and keep its name. Start it after oxmysql and your framework. The first start prints a one-time owner code; the exact order for each framework is in the install guide.

set onesync on
ensure oxmysql
# your framework (es_extended, qb-core or qbx_core) and inventory
ensure zerodev_sentinel
Starts on Watch

Every rule watches and writes what it would have done. Nobody is alerted and nothing happens to anyone until you switch the level on the owner desk.

Your staff decide

On Recommended, Sentinel opens a case with the evidence and never punishes on its own. Bans go through a ban wave, with an appeal code.

Permissions you choose

Four roles ship; make your own, and give one person a switch or take one away. Every change goes to the staff record.

Its own folder only

Sentinel writes only inside its own folder, its database tables and its key-value store. It does not edit other resources or server.cfg.

Every supported script

Frameworks

  • ESX Legacy
  • QBCore
  • Qbox
  • Standalone

Detection, cases, the console, the panel and Discord work the same on every framework.

Money and item trail

  • ESX Legacy
  • QBCore: from its source
  • Qbox: from its source
  • ox_inventory hooks

With qb-inventory, item changes are not followed; a rollback can still move items. Standalone has no money trail.

Voice

  • pma-voice

Only for listening to a player's voice chat. Nothing else needs a voice resource.

Storage

  • oxmysql
  • The resource's own key-value store

No SQL file to import. Bans are always mirrored to the key-value store.

Discord and clips

  • Discord bot
  • Discord webhook
  • FiveManage

All optional. Without them, cases and clips stay on your server.

Sentinel

What you get

Interface render with sample players: the Right now sheet of the staff console, four players ranked from Proven to Unusual, each with what they did and what Sentinel did.
Interface render

Right now, in plain English

The first sheet says what is happening on your server: who looks like a threat and why, how sure Sentinel is, what it already did, and what was ruled out (a revive, a script's own teleport). One next step per player.

Interface render with sample data: a case file under review, with the finding, a screen clip, the case log and the seal.
Interface render

Cases with the evidence

Each case holds the finding, the recording around it, screen clips and a seal that shows whether its hash chain still verifies. Replay the incident in a private world, then reveal, quarantine, clear or ban.

Interface render: the Protection sheet of the owner desk, with Watch, Recommended and Strict, and every rule with its state.
Interface render

One switch: Watch, Recommended, Strict

Start on Watch and read what the rules would have done. Recommended alerts staff with the evidence; Strict also quarantines on proof-level findings. Pin any single rule to Live or Shadow on the same sheet.

Interface render with sample staff: the Staff sheet with one admin's switches, each set to follow the role, allow or deny.
Interface render

Permissions the owner chooses

Support, Moderator, Admin and Senior admin ship as lists of switches. Make your own roles, and allow or deny one switch for one person. The dangerous ones (ban at once, listen, settings) ask for a second press.

Browser panel with sample players: the Live view sheet watching one player's screen, with the player list and the player deck.
Browser panel

A browser panel for your staff

The same desk in a web browser, signed in with a one-time code. Live view of any player's screen and listening to their voice chat. Every view and listen is in the staff record.

Interface render with sample players: the duty map, a relief model of the island with brass place-name plates and player pins.
Interface render

The duty map

Every online player on a 3D model of the island, pinned by state: open case, high score, quarantined, staff. The terrain is measured from your own game the first time a staff member opens it.

Interface render with sample players: the Player reports sheet with two open reports and their close buttons.
Interface render

Player reports

Any player types /report with a server id and what happened. The last two minutes around both players are saved into a case. Reports about staff go to the owner only.

Interface render with sample staff: the Internal affairs sheet with the staff record of the last 35 days.
Interface render

Internal affairs

For the owner: what each staff member did, what needs a look (grants to themselves, bans with no case, teleports to players), and a weekly fairness report.

Guard a risky resource

sentinel:audit lists the events clients can trigger in every started resource. One line added to a resource stops bad calls before its script runs, with your own rules for amount, rate and distance.

Discord, clips and appeals

Cases posted to your Discord with buttons for your staff, clips to FiveManage or a webhook, and an appeal code on every ban that staff accept or reject.

Everything inside

Rules

  • Movement: teleport, speed, noclip and flight
  • World: entities, explosions, projectiles, particles, fires
  • Combat: damage, range, fire rate, aim
  • Events: bait events, state bags, floods, guarded events
  • Economy: money and items from nowhere, reward loops
  • The player's game: godmode, tampered checks
  • Identity: banned players on a new account

For staff

  • Right now sheet
  • Case files with clips, seal and 3D replay
  • Duty map
  • Player reports
  • Reveal, quarantine, clear, kick and ban
  • Browser panel with live view
  • Listen to voice chat

For the owner

  • Owner seat with a one-time code
  • First run sheet
  • Protection level
  • Staff roles and switches
  • Internal affairs and the weekly report
  • Discord and clip storage keys
  • Ban wave and appeals

Watchers

  • Event audit of every resource
  • The guard and virtual patches
  • Script scanner
  • File integrity
  • Join shield
  • Hardening advisor
  • Money and item trail with rollback

Sentinel

FAQ

Does Sentinel ban or kick anyone on its own?

Not on Watch or Recommended. It starts on Watch, where it only logs what it would have done. On Recommended your staff get the evidence and decide. Only on Strict does a high score quarantine a player until staff look, and a proof-level finding queue a ban for the ban wave.

Does it work on QBCore and Qbox?

Yes. Detection, cases, clips, the console, the browser panel, Discord and the owner desk are the same on every framework. The money and item trail has its own adapter for ESX, QBCore and Qbox.

Do I need a database?

No. With oxmysql Sentinel keeps its records in your database and creates its own tables on first start; there is no SQL file to import. Without it, everything lives in the resource's own key-value store.

Does it catch every cheat?

No anti-cheat can promise that. Sentinel judges what the server can see and what a player's game reports; it does not read other programs on a player's PC. The rule list says what each rule catches and how it was tested, and every finding comes with its evidence.

Can a banned player appeal?

Yes. The refusal message shows an appeal code. The player sends it to your staff, or your website posts it to Sentinel's appeal route, and staff accept or reject it.

What is editable?

The config files and translations in config/, the framework adapters in bridge/ and the guard file in guard/ stay open. The rest is protected by Cfx.re asset escrow.

Buying, delivery and licence questions are on the support page.

Sentinel

Pairs well with

Sentinel runs next to any script. These are the other ZeroDev scripts for the same servers.

In game: the ZD5 2.0.0 from the front three-quarter. ZD5 Back in stock In game

Custom car

ZD5

A four-door performance estate with a hand-built cabin, its own V8, a flagship sound system and air suspension.

  • ESX
  • QBCore
  • Qbox
  • Standalone

$10 onceno subscription, no trial

Docs and support

Documentation and support

Start with the quick start. Problems are in the troubleshooting guide. Tickets usually get a first reply within a day.

In game