Documentation

Overview

hoaxeye is an anti-cheat SaaS for FiveM. These pages describe what each live detection family does today, the operator-facing modes and verdicts, and how false positives are handled. Action stays with the operator — hoaxeye produces a verdict; the server decides what to do with it.

Start here

New install? Walk through the Quickstart for a working setup in under ten minutes, then read Server setup for deeper config (resource whitelist, performance, Discord verify hookup).

Detection families

Each family page below describes the modes you can run it in, the public verdicts it emits, the latencies and cadences we measure, and the false-positive history that shaped the current version.

Reference

  • API reference — public endpoints, auth, status-code semantics.
  • FAQ — false-positive appeals, whitelist requests, update cadence, emergency-bypass use cases.
  • Live availability is on the status page; incidents and scheduled maintenance show up there before they show up here.

What we don't publish

These docs describe what each family does — not the exact storage locations, signal keys, regex/pattern internals or score thresholds that drive the detection. That information would let bad actors target the very signals the product depends on. If you've signed an NDA as part of the pilot, the corresponding internals are documented in your pilot package.