C++ Vision App Obfuscation & Security

I have a C++-based computer-vision application that runs exclusively on Windows, and I need to raise its barrier against reverse-engineering without crippling frame-processing speed.

The job breaks down into three concrete goals:
• Bind each compiled build to the customer’s HWID and (optionally) current IP, so the program refuses to start when either value is wrong.
• Integrate solid anti-debugging measures capable of detecting common tools (x64dbg, WinDbg, Cheat Engine, etc.) and blocking memory dumps or live attach attempts.
• Obfuscate both code flow and strings, encrypting sensitive constants so they never sit in plaintext inside the executable.

I am open to whichever approach you believe gives the best security-to-performance ratio—commercial packers, LLVM-based passes, a custom VM layer, cloud hosting, you name it—as long as it can be fully automated in my build pipeline (CMake + MSVC / Clang).

Acceptance criteria
1. A protected EXE that still meets my current FPS benchmark (±10 %).
2. Attempting to launch the EXE on an unregistered machine or mismatched IP shows a clean rejection message.
3. Attaching a debugger, dumping the process, or scanning memory reveals only encrypted or meaningless data.
4. Delivery of integration notes or scripts so I can reproduce the protection for future builds.

If this scope matches your expertise in C++ protection, Windows internals, and code-obfuscation techniques, let’s talk details and timelines.

NEEDED BY: Thursday