Endive is a JVM‑native WebAssembly runtime that runs Wasm modules without any native libraries or JNI. Forked from Dylibso’s Chicory project, it inherits a year of development and now ships under the bytecodealliance GitHub org. The team thanks Dylibso for its incubation work and invites users to share their builds via Zulip. It runs on any JVM version from 8 onward, fitting legacy and cloud workloads.

Embedding traditional runtimes such as V8, Wasmtime or Wasmer into Java applications forces developers to bundle platform‑specific binaries and invoke them through foreign‑function interfaces. That complicates distribution and breaks the JVM’s safety guarantees. Endive runs entirely on the JVM, preserving memory safety, observability and tooling while supporting any Java environment, even highly restricted ones. The project aims to become the default Wasm runtime on the JVM, offer full spec compliance, and provide idiomatic Java host APIs. Endive also exposes a simple Java API that mirrors the Wasm module imports, streamlining integration.

Endive already implements a bytecode parser, interpreter, and a suite of validation checks; tests from the official Wasm test suite pass with green results. Roadmap items include SIMD, tail‑call, exception handling and GC support. A growing list of adopters is tracked in ADOPTERS.md, confirming that the runtime is ready for production use. Developers can contribute via the Zulip channel or submit pull requests; the project maintains separate interpreter and compiler engines to enable future ahead‑of‑time compilation. Performance benchmarks show comparable speed to native runtimes on typical workloads.