How Cerberus delivers protection updates to your game — without requiring downtime or client patches.
Cerberus uses a layered update pipeline so your game stays protected without requiring downtime or client patches. Most updates are transparent — your players never notice them. Here's how each type flows from our team to your live environment.
| Scenario | Update Type | Partner Action | Player Impact | Downtime |
|---|---|---|---|---|
| New cheat detected in the wild | Signature | None | None — signatures sync silently | Zero |
| Improved aim analysis model | AI Model | None | ~5ms latency spike during swap | Zero |
| New hardware fingerprinting capability | Driver + SDK | Pull new SDK, ship in next patch | Included in your regular game update | Zero |
| False positive spike on a game overlay | Hotfix (Sig) | None — whitelist pushed automatically | Affected sessions released from hold | Zero |
| Critical kernel vulnerability patched | Hotfix (Driver) | Emergency SDK pull recommended | Players update on next game launch | Minimal |
| Scheduled maintenance window | Infrastructure | None — detection falls back to cached sigs | Dashboard may lag briefly | 2-4 min |
Partners receive webhook notifications for all update types. Configure your endpoint in the API dashboard to receive real-time deployment events. Each payload includes the update type, affected components, changelog summary, and whether any partner action is required. Webhooks fire at each rollout stage (canary, 10%, 100%) so you can track deployment progress.