FlowStorm

Overview

FlowStorm is a tracing debugger for Clojure and ClojureScript, built for developers who need to examine an execution record instead of relying only on manually placed pauses. It is a particularly good fit for interactive, concurrent Clojure work where thread behavior and runtime values matter. The zero-cost license is compelling, but teams must meet its runtime prerequisites and account for a significant ClojureScript async/await limitation.

Key features

FlowStorm records execution without requiring breakpoints or changes to application code. That makes it useful for investigating behavior that is awkward to stop at the right moment. After recording, code stepping, value inspection, call-stack and function exploration, and exception debugging let you move from a symptom to the relevant execution path. Conditional breakpoints and time-travel debugging add targeted control when a broad recording is too large or a previous state needs another look.

Its execution timeline lays out events from different threads, exposing how instructions interleave. This is more informative for concurrency questions than a single sequential call stack, although it is most useful when a team can interpret the resulting event history. Customizable, real-time visualizations and a plugin system support project-specific views and interactions with recordings. Those extension points are a strength for specialized tooling; they matter less when conventional stepping and inspection already answer the question.

The interface can send displayed values to the REPL with one click, and recordings can be analyzed with Clojure. That keeps investigation connected to experimentation rather than making inspection a dead end. The documented language coverage includes Clojure and ClojureScript in browsers, Node.js, and React Native. An Emacs front end, Cider Storm, plus setup guidance for VS Code and IntelliJ IDEA, gives editors a practical place in the workflow.

Remote debugging is documented for SSH tunnels, out-of-process setups, Docker, and React Native. These options make FlowStorm more suitable for services or devices that are not running beside the developer, though each deployment still requires its corresponding setup. Minimum requirements are JDK 17 or later and Clojure 1.10.0 or later. Vanilla FlowStorm does not support async/await introduced in ClojureScript 1.12.145; projects that depend on that feature should consider ClojureScriptStorm instead.

Pricing

There are no paid tiers, seat charges, quotas, renewal terms, or trial period to weigh. The free plan is therefore suitable for individual developers, teams, and self-hosted deployments that can use Clojure or ClojureScript and satisfy the runtime requirements. Its trade-off is not a reduced feature tier but the product’s language scope and the ClojureScript async/await gap.

Platforms

FlowStorm supports Linux, macOS, Windows, and self-hosted use. Its documented targets include browsers, Node.js, and React Native. Editor guidance covers Emacs through Cider Storm, VS Code, and IntelliJ IDEA. Remote configurations include SSH tunnel, out-of-process, Docker, and React Native arrangements.

Who it's for

Choose FlowStorm for Clojure or ClojureScript applications where post-execution tracing, REPL-driven investigation, time travel, or thread-event analysis is central. It suits developers who want recordings without editing source code and teams willing to build specialized visualizations or plugins. It is a poor fit for projects that require ClojureScript 1.12.145 async/await support in the vanilla debugger, or for teams working outside the two supported languages.

Pros and cons

Pros

• Recording without code changes: captures execution without adding breakpoints or modifying source.
• Strong investigation toolkit: stepping, inspection, call exploration, exception debugging, conditional breakpoints, and time travel cover both broad and focused diagnosis.
• Concurrency visibility: the thread timeline shows instruction interleaving that a call stack can hide.
• Interactive workflow: one-click REPL transfer and Clojure analysis turn observations into experiments.
• Free and open source: the only plan costs nothing and permits unrestricted use.

Cons

• ClojureScript async/await gap: vanilla FlowStorm does not support the feature introduced in ClojureScript 1.12.145.
• Runtime floor: JDK 17+ and Clojure 1.10.0+ exclude older environments.
• Focused language scope: it is not a general-purpose debugger for other ecosystems.

Alternatives

For native and cross-platform low-level debugging, LLDB is a free, open-source debugger supporting Android, iOS, Linux, macOS, and Windows. IDA Pro is the choice for disassembly and decompilation: IDA Free costs 0.00 USD, while IDA Pro Essential costs 1099.00 USD.

Pick Perl Debugger when you need the debugger included with Perl, provided the program compiles correctly first. PonyDebugger targets iOS with a client and gateway server under Apache License 2.0. For embedded targets, pyOCD is an Apache 2.0 open-source option, while Black Magic Debug is for JTAG/SWD microcontrollers and requires compatible probe hardware and a suitable toolchain.

GDB is a free GNU-licensed debugger with source available. OpenOCD is another open-source option distributed through operating-system packages or source code. Browse more choices in Debuggers.

Verdict

FlowStorm is the right choice for Clojure and ClojureScript developers who want no-cost execution recording, time-travel inspection, REPL integration, and a clear view of thread interleaving. Look elsewhere if your project depends on ClojureScript async/await 1.12.145 or uses a different language or an older runtime.