F

FlowStorm

Free#13 of 27 in Debuggers

An omniscient time-travel debugger for Clojure and ClojureScript.

—Not yet scored

Visit FlowStorm

At a glance

• Editor score
  Not yet scored
• Pricing
  Free plan
• Best for
  Omniscient Clojure debugging
• Free plan
  Yes
• Paid from
  None
• Supported languages
  Clojure, ClojureScript
• Facts checked
  20 Sep 2026

• Where it wins

  • Records execution for forward, backward, and time-based navigation
  • Inspects call trees, locals, arguments, returns, stacks, and exceptions
  • Supports remote debugging, programmable analysis, and custom visualization

• Where it doesn't

  • Language coverage is focused on Clojure and ClojureScript
  • Requires comfort with interactive development workflows
  • Its feature set may exceed the needs of simple breakpoint debugging

Our verdict on FlowStorm

FlowStorm is an open-source debugger for Clojure and ClojureScript, designed for developers who need to understand program behavior across an entire recorded execution rather than inspect only the current pause point. It runs on Windows, macOS, and Linux, works independently of a specific IDE, and supports Clojure applications plus ClojureScript environments in browsers, Node.js, and React Native. Its free, open-source model makes it particularly suitable for teams and individual developers already working in the Clojure ecosystem.

The defining capability is omniscient debugging through execution recording. Developers can move forward and backward through code, navigate a recorded timeline, inspect call trees and functions, and review locals, arguments, return values, and stack information. Conditional thread breakpoints and exception-unwind inspection add control when investigating complex behavior. This approach can make historical state and execution flow more accessible than conventional pause-and-step debugging, especially when the issue depends on what happened earlier in a run.

FlowStorm also extends beyond local inspection. Remote debugging is available through nREPL and WebSocket connections, while a Clojure API supports programmable analysis of recordings. Custom data visualization and value inspection provide additional ways to examine application behavior. These capabilities suit interactive development workflows and teams that want to analyze recordings programmatically. Developers focused on languages other than Clojure or ClojureScript should choose a debugger aligned with their language stack. Likewise, projects needing only straightforward breakpoint debugging may prefer a simpler tool; FlowStorm is most compelling when recorded history, time travel, and deep inspection are central requirements.

FlowStorm pricing

FlowStorm fact sheet

Alternatives to FlowStorm

• GDBA free, open-source debugger with unusually broad language, target, and remote-debugging coverage.—
• LLLDBA capable, free debugger for C/C++ and Apple-platform development.—
• WinDbgA free, deeply capable debugger for Windows applications, drivers, and crash analysis.—

See all FlowStorm alternatives →

Used FlowStorm? Be the first to review it

The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used FlowStorm for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.

Write a reviewTwo minutes · verified accounts only · read by an editor before it appears

Website

Reviews come only from verified accounts. Sign in or create an account first — your e-mail is never shown.

Your rating

5 stars★4 stars★3 stars★2 stars★1 star★

Title

Your review

0 characters · at least 80, up to 3,000

Pros (optional · one per line)

Cons (optional · one per line)

Your name (shown with your review)

Role (optional)

Company (optional)

How long have you used it?Prefer not to sayLess than a month1–6 months6–12 months1–2 years2+ years

I've used FlowStorm myself and this is my honest opinion — nobody paid or asked me to write it.

Send my reviewPosted from your verified account. Reviews appear after an editor reads them, usually within two working days.

Featured on iTechGuides

Reviewed by iTechGuides Editors · Editorial team · Updated Sep 2026

Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. It never changes a score or a verdict. How we rank.