Everything a protected build needs to reach its users
Protection fails quietly when the licensing around it is weak. So Cerberus runs the whole path, from the build leaving your CI to the copy running on a customer’s machine. Use all of it, or plug the parts you need into what you already run.
The parts
- Protection
- A pipeline per build, aimed at automated analysis as much as at people. Hardening, anti-tamper and checks that run where the attacker cannot reach.
- Licensing
- Keys, entitlements, seats and device limits, verified by the server. Revoke a license and it stops working.
- Distribution
- Signed builds, release channels and updates, delivered to the people entitled to them and nobody else.
- Watermarking
- Each copy traces back to the license it came from, so a leak has a name on it.
- Commerce
- Storefront, checkout, coupons, resellers and refunds, tied straight into licensing.
- Identity
- Accounts, sign-in, two-factor and passkeys, with sessions bound to devices.
- Telemetry
- Crashes, errors and tamper signals from the field, so you see an attack while it is happening.
- Support and community
- Tickets, forums and chat, with moderation, sharing the same accounts.
- Operations
- One dashboard for staff, with audited permissions, and an AI assistant that works through the same permissions.
How we work
Cerberus is a platform and a small team. Some tenants hand us the whole stack and we build and run it. Others keep their own storefront or identity and use us for protection and licensing only.
Either way we onboard directly. There is no self-serve tier, because a protection pipeline has to be designed for the build it protects.