Protection¶
PyLocket applies maximum protection to every build automatically. This includes military-grade encryption, anti-reverse-engineering measures, memory protection, and binary hardening. No configuration is needed — every build receives the full protection suite.
What Gets Protected¶
- Function bodies: Every Python function, method, and lambda expression
- Class bodies: All class-level code
- Module-level code: Top-level module initialization code
What Is Not Protected¶
- Non-Python files: Images, configuration files, data files, HTML templates, and other static assets
- C extension modules: Compiled
.pydand.sofiles from C/Cython are not modified by PyLocket - Function signatures and docstrings: Names, argument lists, and docstrings remain visible in stubs
- Module names and directory structure: Package layout is preserved
Tip: If you need to protect non-Python data files, encrypt them at the application level and decrypt them within your protected Python code.
See Also¶
- How Protection Works — High-level overview of the protection pipeline
- Security Model — Security architecture overview
- Performance — Runtime performance information