Skip to main content
OPEN SOURCE / LOCAL HEAP ANALYSIS

Find what keeps
memory alive.

Turn a Java heap snapshot into an investigation. Explore retained memory, trace references, query objects, and review the code—without treating a suspect as a verdict.

VS Code and IntelliJ: Marketplace installation · Standalone: separate distribution
Analysis controls depend on the installed package, platform and version.

From local heap to investigation
Local analysis · clear boundaries
  1. Local .hprofCompleted, immutable snapshot
  2. Shared Rust engineQuick Scan or full graph analysis
  3. Staged resultsShallow first · retained when ready
Present results through one host adapter
Optional AI: selected context → user action / approval boundary → configured provider

Host adapters are alternatives. Memory is the default; optional Disk mode reuses verified structures. Terminal commands can run without a browser. Motion is illustrative, not measured timing. No analysis or network request runs here.

11analysis & workflow tabs
10configured AI providers
6Scoped MCP tools
Apache 2.0open-source license
A SMALLER PATH TO CLARITY

Start with evidence.
Keep the boundaries visible.

YOUR DATA / YOUR DECISION

Local analysis.
Optional AI. Explicit limits.

The analysis engine reads your local dump. AI actions and telemetry have separate controls. Metadata can still be sensitive; approved AI fixes send the full source file.

One engine. Different environments.

VS Code, IntelliJ, terminal, browser, and MCP adapters reuse analysis—not every host capability. Setup and limitations are documented separately.

Explore the host guide →