PIQIU Product
BCE
Shipping a Java application also means shipping a lot of readable bytecode. BCE is built for teams that need more control over what they distribute and where it can run.
Visit BCE ↗Authorized use
BCE is for software you own or are authorized to protect and distribute.
Protection happens before distribution.
BCE lets a software owner select sensitive classes, packages, embedded JARs or dependencies, then prepare a protected application together with the runtime files needed for an authorized target.
The aim is not to claim that inspection becomes impossible. It is to make selected implementation details harder to recover and to add control over where a packaged application is licensed to run.
What can be part of a BCE workflow
- Selected Java classes and packages
- Regular, dependency and executable JARs
- Spring Boot and WAR packaging structures
- Machine-bound authorization
- Long-term or time-limited licenses
- Windows, macOS, Linux, Docker and Kubernetes targets
A realistic boundary
Protection raises the cost of inspection.
Obfuscation, protected runtime loading and licensing address different parts of a distribution problem. They work best alongside ordinary security engineering and a clear release process.
Read the Java bytecode note →