How I Think
Pattern Sense.
I usually see where a system is going to break before I can explain why. Even on stacks I haven't touched in years, I can find where the vulnerabilities sit and fix them at the source.
Low-level systems engineerGood security is quiet.I build it that way.
I'm Evora. I work on the layers most people never see: hypervisors that sit under the OS, protection SDKs that lock code to a machine, and reverse-engineering tooling that lets an agent drive the disassembler. Two and a half years of shipping things that only feel obvious after they land.
Open to collaborations and new work
Selected work
01
Evorion 4
Rewriting the entire auth and licensing runtime from the boot path up. HWID binding, encrypted hot sections, server-side functions so the sensitive paths never live on the client. The licensing spine for everything else I ship.
Read the runtime notes02
Shadow
Frontier-class code virtualization for x86-64. The client and the server share the runtime: the hot logic executes server-side, so no run stays unsupervised and the sensitive code never fully lands on the machine you shipped to.
Private, ask for a walkthrough03
Chimera Framework
A Type-1 hypervisor that sits alongside Hyper-V without needing a kernel driver. Page-table hooks, hypercall interception, ASID hijack on AMD. Memory introspection runs from underneath the OS, transparent to anything userland or kernel can see.
Private, ask for a walkthrough04
Chimera RE Toolkit
Reverse-engineering primitives exposed over MCP: live kernel reads, IDA with Unicorn-backed emulation for static lifting, automated signature and pattern generation. Agents drive it directly, and the analyst becomes the reviewer instead of the operator.
See the MCP surface05
EvoPack
A protection layer for Python. Source and .pyd are lifted into a hand-rolled mini-VM, so what ships is not what anyone can read.
Design notes2.5
Years developing
10+
Projects shipped
40+
Developers using Evorion
Skills
How I think.
Three habits that hold up regardless of the stack: pattern recognition, obsessive rebuilds, and reasoning across every layer in one frame.
About
Low-level, practiced like design.
The best systems work is indistinguishable from good engineering: fewer moving parts, honest interfaces, defaults that do the right thing when nobody is looking. I spend most of my time making the safe path the easy one, and deleting the paths that shouldn't exist. If it ships with my name on it, I'll keep rebuilding it until it stops bothering me.
- Now
- Shadow, Evorion 4, and the Chimera Framework
- Before
- EvoGuard, EvoraAI, and a stack of shipped runtimes
- Stack
- C / C++ · Web security · Windows internals · Agentic AI
Contact
Say hello, I don't bite.
Open for developer work.
Currently taking on runtime and tooling engagements for late 2026.