features
Protection that holds up against real threats.
Obelisk is built to withstand emerging threats and the advanced reverse engineering tool ecosystems that come with them.
No source code required
No symbols, no changes to your build pipeline, nothing to integrate. Point Obelisk at the binary you already ship and get a protected one back.
Binary safety and speed as a priority
Exception handling, security checks, and program behavior are verified intact on every single build before it ships.
how it works
The binary transformation process
01
Lift
Every instruction gets decoded and mapped before anything is touched. The engine builds a complete model of what the binary is and what every byte means.
02
Transform
Arithmetic is rewritten into equivalent forms that are a nightmare to read. Code paths get duplicated and flattened.
03
Relocate
The transformed code moves to its new home. Exception tables and guard metadata are rebuilt to match the new addresses. The program still unwinds and recovers like it did before.
04
Re-point
Every pointer, table entry, and reference to the moved code is rewritten to its new location. The engine refuses to ship anything it cannot account for.
05
Remove
The original code is deleted from the shipped binary. Nothing original remains to analyze or diff against.
what you get
The protection stack
Obfuscation is applied directly to the compiled binary, targeted at specific functions or across the whole build. The protected path never depends on a helper process or a license server.
01
No original code left to find
The original code section is fully removed from what you ship, whether you protect ten functions or the entire build.
02
Logic rewritten, not just hidden
Arithmetic and control flow are mathematically rewritten into equivalent, obscured forms.
03
Keeps your binary's shape
The protected binary keeps the original's shape. Same PE structure and the same sections. Your build pipeline and deployment flow need no changes.
04
Advanced Obfuscation Methods
Novel obfuscation primitives that stack multiple layers to add complexity. Advanced control flow modification to flatten the decompiler graphs, opaque predicates to plant deceptive structures, and block duplication to give a protected function its own shape. Algorithms that thwart static analysis by computing values that only exist at runtime.
05
Exception handling stays intact
Exception unwinding and stack-cookie checks are rebuilt to match the new code layout, so they keep working exactly as they did before.
06
Fast enough for your release schedule
Rewriting and obfuscation applied in minutes.
built for
Built for where protection actually matters
[ cybersecurity ]
Cybersecurity
Validate how your tooling and research actually hold up against manual and AI assisted reverse engineering. Ideal for red teamers who need their tooling to survive real scrutiny, not just dodge a signature.
[ gaming ]
Gaming
Protect your build against cracking and cheats.
[ enterprise ]
Enterprise software
Ship protected builds your customers can trust won't crash, all while protecting your intellectual property.
Twin-only release architecture
The original code section is deleted from shipped outputs entirely. Every executable cell is lifted into the engine's reconstructed twin plane. There is no original stream left to diff against.
MBA rewriting, formally verified
Arithmetic expressions are replaced with semantically equivalent mixed Boolean-arithmetic forms, drawn from a catalogue whose equivalence is formally verified before use.
Kept-floor inviolability
The lift/lower machinery accounts for every byte of the original code floor. Kept cells, spill regions, runtime-copied code, and dispatch tables each get their own placement and relocation rules.
Layout-stable by default
Protection ships without rewriting the binary's layout shape, so your existing tooling and deployment assumptions keep working.
Metadata rebuilt, not bolted on
SEH/pdata unwind directories, guard metadata, and GS cookie sites are reconstructed to match the new layout.
in scope today
Native Windows x86/x64 PE files, executables and DLLs. Point Obelisk at the binary you shipped, it hands back a protected one. No source, no symbols, no build changes.
on the roadmap
.NET assemblies, drivers, and Linux targets. If your stack is one of these today, tell us. It shapes what gets prioritized next.
Build with confidence.
See pricing, or get in touch if you want to talk through your specific target first.