We built the FiveM anticheat we wanted to run, then sold it to the people who needed the same one.

Every FiveM anticheat we tried in 2024 forced a choice: tank resmon, eat false positives, or wait weeks for a public bypass to get patched. Raven started as a workaround on one server. It now protects five hundred.

Founded 2024 · Independent

1000+
Servers running Raven today
Under 0.5ms
FiveM resmon at 200+ concurrent players
24h
Median response to a new public bypass
4.9 / 5
Operator rating across reviews

Detection runs in two layers. They check each other.

The client layer watches process integrity, memory regions, input patterns, and the attack surface that paid menus inject through. The server layer cross-checks every event the client emits against state the server already knows is true: health, position, inventory, money, weapons.

A signed heartbeat channel ties the two halves together. Tampering with the client is visible from the server. Spoofing the server is visible from the client. Most public bypasses pretend the other half does not exist; ours stays loud about both.

New detections go through an internal false-positive review on a thirty-server sample before they ship. Aggressive heuristics catch more cheaters and also ban more legitimate players. We treat that second outcome as unacceptable. Raven Mind handles the per-server tuning so operators do not have to babysit thresholds for the protection to work.

Six principles we hold to.

  1. Dual-layer or nothing

    Client and server detection run together on every plan, never sold apart. Client-only anticheats miss server-side event abuse. Server-only anticheats miss memory injection. Shipping just one half is what produces the bypass videos you see on TikTok.

  2. Heartbeat anti-tamper

    A signed liveness channel between client and server detects tampering in seconds. Any drop, replay, or signature mismatch triggers a kick and an audit log entry admins can review later. Killing the anticheat process is itself a detection.

  3. Evidence-first bans

    Every automated ban carries the signature that fired, a screenshot of the frame, a session replay link, and the trust score history. Admins audit and reverse in two clicks. False-positive triage is a first-class workflow, not a ticket queue.

  4. Operator-driven AI

    Raven Mind, our in-house ML system, suggests fixes but never auto-unbans. Every reversal is an operator decision. The model learns from those decisions across the network. The longer you run Raven, the less tuning you have to do yourself.

  5. Global ban network

    A bad actor banned on one Raven server is flagged on every other Raven server. Operators choose whether to enforce automatically or just receive the warning. The network cuts the cost of catching repeat offenders to roughly zero.

  6. Performance is a hard ceiling

    The resource runs under 0.5ms on the FiveM resmon, measured at 200+ concurrent players. Detections that push tick over budget get refactored or cut. Players never feel the anticheat in the frame timer.

How we run the product.

Disclosure and response
Researchers who report a bypass get an acknowledgement within 24 hours. Critical issues ship as a hotfix to every live server, with no operator update required.
Privacy posture
Raven processes only what is needed to detect cheats: in-game events, memory signatures, and screenshots of suspect frames. No keystrokes, no microphone, no camera, no off-game telemetry.
Operational transparency
Detection updates land in the dashboard changelog. Status incidents (panel outages, ban-network sync delays) are posted to Discord and resolved publicly, not buried in a support email.
Refunds and cancellation
Subscriptions cancel from inside the dashboard at the end of the current period. No email tickets, no retention scripts. The published refund policy applies to every plan without exceptions.

Drop the resource in, restart, and the protection is live. Two-minute install on every framework, including ESX, QBCore, vRP, and QBox.