Sell software in the browser without giving it away.
Your paywall, your licence check and your keys all run on someone else's machine. TrustSig Protect makes that code unreadable, and makes every crack die at your next release.
Your app ships with the lock and the key.
Whatever runs in the browser, anyone can open and read.
Your app decides who paid for what, and that decision runs on the visitor's machine.
Someone finds the check, changes the answer to yes, and reloads the page.
They pass the patched copy around, and your paying customers are competing with a free one.
- Licence checkProtected
- Paywall logicProtected
- Key handlingProtected
- Page layoutUntouched
- AnalyticsUntouched
Your logic goes in readable and comes out as noise.
Same app, same behaviour, nothing left to read.
You pick the parts that matter: the licence check, the paywall, the keys.
Protect turns those parts into instructions that only our own engine knows how to run.
Open the file afterwards and there is no code to follow, no names to search, no check to flip.
Every release is a new lock.
A crack that works today is dead on your next build.
Each build is scrambled differently, down to the last byte.
A patch written against one release does not fit the one after it.
Whoever cracked you starts from zero every time you ship.
Cracking your app stops being worth the time.
Nobody can make browser code unbreakable. We make each crack slow to build and dead on your next release, so the people doing it move on to easier software.
- Debugger attached
- Function patched
- Browser code swapped
Session ends
Touch it while it runs and it stops.
Debuggers, patched functions and swapped browser code end the session.
Protect keeps checking its own code the whole time your app is open.
Attach a debugger or patch a function and the session ends on the spot.
The attacker gets no error and no hint about what gave them away.
Web app piracy, answered
No, and nobody can promise that for code running in a browser. It makes each crack slow to produce and short-lived, so copying your app stops paying for itself.
Only the functions you choose run inside the protected engine. The rest of your app runs exactly as it did before.
No. You pick the functions worth protecting and ship the protected build in their place.
JavaScript and WebAssembly, including Rust compiled to WebAssembly.
Get in touch.
Tell us what you ship, what needs protecting, or whatever you want to ask.