Inverse X

Started as a personal project exploring game security and anti-cheat mechanics, it grew into a full commercial product: a kernel driver, an obfuscated C++ client loader, a hardware-bound auth backend, a React dashboard, billing, and support tooling, all built and maintained personally over two years.

The core technical challenge was the kernel driver, reading and writing target process memory while navigating EPROCESS-level integrity checks meant mapping physical memory through MDL chains and building a thorough mental model of how the Windows Virtual Memory Manager handles PTE flags. The client loader resolved its API table dynamically at startup via a custom hash-based GetProcAddress reimplementation, with all strings RC4-encrypted at compile time.

The auth layer was a Node.js microservice backed by PostgreSQL, handling around 40,000 requests a day at peak, with hardware binding derived from a deterministic device fingerprint tied into an RSA-4096 signed JWT. Running an 11,000-member product at 16 taught more about operational discipline under pressure than anything else has since, incident tooling, automated status pages, and a rapid rollback process, built specifically because there was no team to fall back on. Wound down eventually once the operational overhead stopped being sustainable solo.