Session-bound telemetry
Heartbeats and detections travel on a short-lived, session-scoped token with a strictly increasing sequence. Your tenant credentials never ship inside a game, launcher or DLL.
Anti-cheat control plane for online games
Catch tampering.
Keep the verdict on your server.
Blackbeard ties client integrity signals to licensed, authenticated game sessions and gives your team the evidence to decide. Your game server stays the source of truth. Blackbeard makes cheating costly, visible and reviewable.
No client-side anti-cheat can make a game impossible to copy or modify. Blackbeard is one layer of a defense-in-depth design.
- Server-authoritativeVerdicts stay on your game server
- Tenant-isolatedEvery request scoped to one studio
- Evidence trailSignals tied to a session and build
- Fails closedNo silent “protected” state
How it works
Four parts, one clear boundary
The client gathers evidence. The control plane binds it to a real session. Your game server decides. No step trusts the one before it blindly.
-
01
Launcher
Verifies signed game files and requests a one-use launch ticket from your backend. It never holds a tenant key.
-
02
Blackbeard agent
Matches the exact signed game binary, starts the sensor and reports narrowly scoped integrity signals.
-
03
Control plane
Binds signals to the licensed session with short-lived tokens, stores evidence and alerts your team.
-
04
Your game server
Validates every state change and combines its own checks with Blackbeard evidence to decide.
Platform
Evidence your team can act on
Signals arrive with the context a reviewer needs, through credentials scoped to a single session.
Context, not just alerts
Each detection arrives with its player, game, sensor and evidence. Launcher sessions record their build and agent.
Response on your terms
Review, dismiss or ban from the console, with temporary bans and appeals. Every decision records who made it.
Audit trail
Bans, key rotations, configuration changes and exports are recorded per studio.
Webhooks and exports
HMAC-signed webhooks push detections, bans and sessions to your tools. Export players, detections, bans and sessions.
Controlled agent releases
Every agent release has a version, a file hash and a minimum compatible version, and downloads only from allowlisted HTTPS hosts.
Editions
Start without a driver
Standard runs entirely in user mode. Enterprise adds optional kernel-level handle protection for teams ready for driver signing and staged rollouts.
Standard
User-mode protection for most online games
- User-mode agent and in-process sensor
- Session-bound telemetry and evidence
- Tenant console, API, webhooks and exports
- No kernel driver for players to install
Enterprise
For competitive titles with dedicated security teams
- Everything in Standard
- Optional signed kernel-mode handle protection
- Staged rollout plan with validation gates
Privacy
What Blackbeard looks at, and what it leaves alone
Anti-cheat runs on your players’ computers. They deserve to know exactly what it does. Launcher sessions identify a player only by a keyed hash of the studio’s account id.
Collected
- Integrity signals from the protected game: loaded modules, hooks, memory protection, debuggers
- Names of other programs and windows, only when they match known cheat tools
- Session, game and build identifiers, and sensor health
- Screenshots, only if a studio’s integration sends them
Never collected
- Passwords or other credentials
- Documents and personal files
- Browsing history
- Keystrokes
FAQ
Straight answers
Can Blackbeard make my game impossible to cheat or copy?
No, and nothing that runs on a player’s computer can. Blackbeard raises the cost of common tampering and gives you evidence. Real protection comes from combining it with server-side validation of everything that matters.
Does Blackbeard ban players automatically?
No. It reports evidence with its confidence and context. Your game services decide. We recommend acting automatically only on several independent, high-confidence signals, and sending everything else to review.
Do players need to install a driver?
Not with Standard, which runs entirely in user mode. Enterprise can add a signed kernel driver for handle protection, rolled out in stages.
What happens if the anti-cheat is missing or blocked?
The launcher and SDK report “unavailable” or “degraded”, never “protected”. Your server decides whether that session may play.
Where does my data live?
In the Blackbeard control plane, isolated per tenant. Only your team can see your sessions, players and evidence.
Get started
Bring Blackbeard into your next release
Studios sign in to the tenant console with the credentials their administrator issues. New studio? Write to us and we’ll set up your tenant.