# Endive > Endive is a JVM native WebAssembly runtime with zero native dependencies, hosted by the Bytecode Alliance. ## Docs - [Quick start](https://endive.run/docs/): Endive requires **Java 11** or later. SIMD support requires Java 21+. - [AI-Friendly Documentation](https://endive.run/docs/ai-friendly-docs): Endive documentation is designed to be easily consumed by LLMs, AI agents, and developer tools. All machine-readable ... - [Installation](https://endive.run/docs/getting-started/installation): Endive requires **Java 11** or later. - [Host Functions](https://endive.run/docs/core/host-functions): Host functions cross the sandbox boundary. Validate all arguments received from Wasm code — especially memory offsets... - [Memory](https://endive.run/docs/core/memory): Wasm only understands basic integer and float primitives. - [Linking](https://endive.run/docs/core/linking): In the Host Functions section we met the `Store` for the first-time. - [Execution modes](https://endive.run/docs/core/execution-modes): | Mode | Performance | Dynamic Module Loading | Requirements | Output Format | Ideal Use Case | - [Runtime Compilation](https://endive.run/docs/execution/runtime-compiler): The compiler translates Wasm to JVM bytecode without post-compilation verification. When compiling untrusted modules,... - [Build Time Compilation](https://endive.run/docs/execution/build-time-compiler): The compiler translates Wasm to JVM bytecode without post-compilation verification. Only compile Wasm modules you tru... - [Runtime Compiler Cache](https://endive.run/docs/execution/compiler-cache): The runtime compiler cache lets the Endive runtime compiler store the results of compiling WASM modules to Java bytec... - [Wasi Preview 1](https://endive.run/docs/wasi/): WASI file access does not enforce path sandboxing by default. Always use a virtual filesystem (e.g., ZeroFs or Jimfs)... - [Annotations](https://endive.run/docs/annotations/): Instead of writing host functions by hand, you can write a class containing annotated methods - [Security Model](https://endive.run/docs/security/overview): Endive executes WebAssembly modules inside the JVM. Understanding the security boundaries is essential when running u... - [Security Best Practices](https://endive.run/docs/security/best-practices): Practical guidance for running Wasm modules securely with Endive. - [CPU](https://endive.run/docs/advanced/cpu-limits): Wasm modules can contain infinite loops. When running untrusted code, always set execution timeouts via thread interr... - [SIMD support](https://endive.run/docs/advanced/simd): SIMD support is available only for Java 21+ and interpreter mode. - [WABT](https://endive.run/docs/advanced/tools): Since we use them in the build of the project, we publish a few wabt tools compiled at build time with Endive. - [Logging](https://endive.run/docs/advanced/logging): For maximum compatibility and to avoid external dependencies we use, by default, the JDK Platform Logging (JEP 264). - [Advanced Wasm Memory Customization](https://endive.run/docs/advanced/memory-customization): Different Wasm workloads will be using the memory in very different ways. - [Why](https://endive.run/docs/experimental/why): Endive is a young project and we acknowledge that we are exploring and spearheading in many aspects the usage of Web ... - [CLI](https://endive.run/docs/experimental/cli): The experimental CLI uses `inheritSystemStreams()` by default, granting the Wasm module access to stdin, stdout and s... - [Using Rust with Endive](https://endive.run/docs/examples/rust): Compiling a Rust library to Wasm is easy and can be performed using standard `rustc` options: - [Migrating from Chicory](https://endive.run/docs/migration/from-chicory): Endive is a fork of Chicory by Dylibso, Inc. ## Blog - [Endive 1.0: WebAssembly on the JVM, Now a Bytecode Alliance Project](https://endive.run/blog/endive-1.0): We're excited to announce **Endive 1.0**, the first release of the project under the Bytecode Alliance. Endive is a p... - [Finding a JVM JIT Bug the Hard Way](https://endive.run/blog/finding-a-jvm-jit-bug-the-hard-way): In early 2025, a user reported intermittent wrong results using the build-time compiler. Not a crash, just a quietly ... ## Optional - [llms-full.txt](https://endive.run/llms-full.txt): Full documentation content in a single file