Your classes ship inside an authenticated archive that only this runtime can open. They are parsed through a split pipeline with no single point to hook, stay encrypted in Metaspace for the life of the process, and are decoded one byte at a time inside a CPU register.
ENCRYPTEDP4JX keeps archive access, class parsing, protected linking, interpretation, JIT compilation, and runtime integrity inside a customized HotSpot security boundary.
Explore the protection architectureProtection remains active from authenticated archive access through parsing, linking, interpretation, JIT compilation, and runtime integrity checks.
A custom ClassLoader can hide files on disk, but the ordinary class definition boundary and runtime inspection mechanisms remain available.
Seven layers of defense continuously protect core code, significantly raising the cost of decompilation, debugging, and reverse engineering.
.p4jx archives carry protected application content and establish a consistent delivery boundary.
DELIVERY / SEALEDVLX HotSpot owns protected class loading, carrying the protection state into the runtime environment.
RUNTIME / CONTROLLEDVerification and linking remain inside the VM security boundary, with critical transitions covered by the same protection chain.
TRUST / CONTINUOUSInterpretation remains inside the VM protection boundary and continues under a unified runtime policy.
EXECUTION / PROTECTEDCompiled execution stays coordinated with the wider runtime protection model, keeping performance and protection states aligned.
POLICY / COORDINATEDThe runtime continuously checks critical environment and code state to preserve the integrity of the protected environment.
STATE / VERIFIEDAgent, profiler, and debugger export paths are restricted, narrowing how external tools can reach protected data.
BOUNDARY / ACTIVEProtect existing deployment shapes while preserving the runtime behavior that frameworks and scanners depend on.
Executable JARs, CLI tools, desktop software, and JavaFX applications.
Protected application classes with framework-aware resource and loader integration.
Protected web applications with virtual archive views for container compatibility.
Distribute protected implementation code while keeping the integration surface usable.
Follow the guided setup, complete the compatibility check, and generate a protected package matched to your target platform.
You can leave message here, or directly send mail to [email protected], we will get back to you ASAP
[email protected]