Protection for software that AI has learned to read.
A language model will now decompile a binary, name its functions and explain the license check to anyone who asks. Cerberus protects the software you ship so that work stops paying off, then runs the distribution and licensing around it.
What changed
Cracking used to take a skilled person and a few weeks. Now the first pass costs a prompt.
Most protection on the market was built to tire out a human reading disassembly. Models do not get tired, and they are good at exactly the part that used to be slow: turning stripped, mangled code back into something a person can follow. The attacker no longer needs to be an expert. They need a subscription.
That moves the question for anyone shipping a desktop client or a plugin. It used to be whether a skilled reverse engineer would bother. Now it is what a model makes of your code when someone pastes it in.
What we do
We build protection against automated analysis first, and against people second.
Every build gets its own protection pipeline. We use proven tooling where it holds and write our own where it does not, and we study how current models attack protected code so the next build is harder than the last.
How it works: .
We don’t publish it.
Around it
Protection is only worth something if the build reaches the right people.
So the platform ships with it. Tenants run their storefronts, licenses and updates on Cerberus today, serving thousands of paying users between them.
- 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.
Who it is for
Teams that ship software to machines they do not control and lose money when it gets copied. We work only for the owner of the software, and we turn work away that does not fit. How we decide.
Talk to us