CheerpJ executes Java applications entirely within the browser using standard web technologies.
It follows the browser security model by design. There is no local JVM, no plugins, and no direct access to the host system.
Execution Model
CheerpJ runs entirely in the web browser using standard web technologies.
- Java applications execute via a combination of WebAssembly and JavaScript
- Includes a Java Virtual Machine and Runtime Environment in the browser
- Deploys applications from standard
.jarfiles - No client-side JVM or plugin installation is required
This model removes the need for local Java installations and associated plugin risks
Security Benefits
- No client-side Java runtime
- No plugin-based execution
- Supports zero-trust architectures
- Supports thin clients and mobile access
These characteristics improve the overall security posture of Java application delivery
Network Model
CheerpJ follows the standard web browser networking model.
- Cross-origin restrictions apply
- Supports HTTP(S) by default. Support for TCP requires an additional proxy component.
All network access is governed by the browser security model
Limitations
Browser security constraints apply
- No direct OS-level access
- Networking is restricted by browser policies
These constraints are part of the browser execution model and should be considered during architecture design
Isolation
CheerpJ relies on browser-level isolation.
- Runs fully inside the browser sandbox
- Isolated from the local system
This ensures that Java applications execute in a contained environment with no direct system exposure
Security Assessment
Not sure about your application?
Confirm security for your application.
Submit your application details, and our engineering team will provide a compatibility assessment.