LLM Decompile Shield
Obfuscation and detection for indies worried about LLM decompilation
- Problem
- Developers fear that anyone with an LLM subscription can turn a binary into semantically equivalent source code, exposing core algorithms. There is little lightweight, practical protection guidance or tooling aimed at solo developers and small teams.
- Solution
- A build-time toolkit: semantics-preserving source transformations, control-flow and constant obfuscation, splitting critical logic into a server or WASM, plus runtime dispatch and integrity checks. It also scores each function for 'LLM recoverability' so developers know what is most at risk.
- Users
- Indie developers and small teams shipping desktop software whose core value is algorithms or business logic.
- MVP
- CLI tool; semantics-preserving identifier and control-flow transforms; critical-function marking and splitting suggestions; obfuscated build output; LLM recoverability report.
- Revenue
- Open-source core with a paid subscription for advanced obfuscation rules and CI integration; or per-project license.
- Why now
- LLM decompilation is improving fast, and classic obfuscators target human reverse engineers, not LLM semantic understanding.