Cerberus exists because most anti-cheat still fights today's cheats with yesterday's tools. We're a small, closed-beta team trying to close that gap honestly — no claims of solved-forever, no hype we can't back up.
Cerberus wasn't pitched as a moonshot. It started as a handful of security engineers comparing notes on where every anti-cheat product they'd worked with or been beaten by kept falling short.
Cerberus was founded in October 2024 by a small group of engineers with backgrounds in kernel-mode security products — EDR sensors, HIPS drivers, and independent hardware-cheat research. Between them they'd spent years watching the same pattern play out: a signature database catches a public cheat, a paid provider ships an undetected build within hours, and the anti-cheat vendor is back to reacting. Meanwhile the fixes on offer were either a heavier always-on kernel driver watching everything on the machine, or no hardware-layer defense at all against DMA boards and spoofed peripherals. Neither felt like an actual answer.
The founding idea was narrow on purpose: build detection across four independent layers — kernel integrity, behavioral AI, hardware fingerprinting, and network-side correlation — so that beating one layer doesn't mean beating Cerberus, and load the kernel component only while the protected game is running instead of leaving it resident all the time. The first year was almost entirely R&D: no customers, a handful of engineers, and a lot of internal red-teaming against our own driver before we trusted it near a live game process.
Closed beta opened in October 2025 with a small number of partner studios willing to run an early build in exchange for direct access to the team. We're still in that closed beta today, still adding studios one at a time rather than opening the gates all at once, and still fixing the things beta is supposed to surface. The team has grown from that original handful to 32 engineers across five departments, but the goal hasn't changed — close the three gaps above without pretending we've closed every gap that exists.
None of these are finished commitments — they're the standard we're building against, and the Trust Center shows exactly where we stand on each one today.
The Cerberus SDK isn't a background service. It loads with the protected game process and unloads when the game closes — nothing keeps collecting data once you've stopped playing.
We publish our real uptime (97–98%, not 99.9%), our real detection rates (58–92% depending on category), and our real false-positive rate (0.14%) on the same pages a customer would see — not just the good months.
The four-layer design came out of reverse-engineering actual DMA boards, firmware, and behavioral bypass tools — not a checklist. Threat research drives what we build next, not the other way around.
We add partner studios one at a time, our driver is EV code-signed with WHQL certification still pending, and our SOC 2 Type II audit is in progress, not complete. We'd rather say "not yet" than overstate where we are.