Trace any process, port, container, or file back to its origin and understand why it's running.
From $4/mo (free plan available)FreemiumDeveloper Tools
Visit Website FreemiumVisit Website
Tracked since2026
The Bottom Line
- Price
- From $4/mo (free plan available). Compare plans
Key facts
- Traces processes, ports, containers, or files to their origin.
- Provides causality chain for running system components.
- Offers both CLI output and an interactive TUI dashboard.
Pros
- Provides explicit causality, unlike traditional tools
- Simplifies troubleshooting complex system interactions
- Available as a single static binary for easy installation
- Supports multiple operating systems (Linux, macOS, FreeBSD, Windows)
- Offers both CLI and interactive TUI for different use cases
Cons
- Community packages might lag behind GitHub releases
- Requires command-line familiarity for full utilization
What is witr?
witr (Why is this running?) is a command-line interface (CLI) and Text-based User Interface (TUI) tool designed to answer the fundamental question of why something is running on a system. Unlike traditional tools like `ps`, `top`, or `lsof` that only show the current state and metadata, witr explicitly reveals the causality chain. It traces processes, services, ports, containers, or files back to their exact origin, detailing how they were started and which systems are responsible for their current existence.
This tool is invaluable for developers, system administrators, and anyone troubleshooting system behavior. It provides a single, human-readable output or an interactive TUI dashboard that makes complex system interactions transparent. witr helps users quickly understand the often indirect and multi-layered causes behind running components, whether they originate from supervisors, containers, services, or shells, thereby streamlining debugging and system analysis.
Key Features
- Trace processes to their origin
- Trace ports to their originating process
- Trace containers to their startup command
- Trace files to their associated process
- Interactive Text-based User Interface (TUI)
- Machine-readable JSON output
- Static binary distribution for multiple platforms
- Guided tutorial and free-play sandbox in browser
Pricing Plans
Free TrialPricing checked Oct 1, 2026
| Plan | Price | Details |
|---|---|---|
| Free | $0 USD per month |
+3 moreShow less
|
| Team | $4 USD per user/month |
+9 moreShow less
|
| Enterprise | Starting at $21 USD per user/month |
+7 moreShow less
|
Is witr worth the price?
Good value
GitHub's pricing is generally fair and competitive, especially with its generous Free tier offering unlimited public/private repositories.
The Team tier at $4 per user/month provides excellent value for growing teams needing advanced collaboration features. The Enterprise tier starting at $21 per user/month is on the higher end but justified for large organizations requiring extensive security and compliance.
This structure is best for developers and teams of all sizes, from individual open-source contributors to large enterprises.
Hidden Costs & Gotchas
CI/CD minutes overages
Package storage overages
Potential for user minimums
Reviews
$99Free with your review
Write a reviewReview witr, get a free AI guide
Share your experience and we will send you Improve Your Thinking Patterns Using ChatGPT, free.
Explore More
witr FAQ
What specific types of system components can witr trace?
witr can trace various system components including processes, services, network ports, containers, and files, linking them back to the exact chain of events or commands that initiated them.
How does witr differ from standard Linux/Unix commands like `ps` or `lsof`?
While
ps and lsof show what is currently running and their metadata, witr goes a step further by explicitly showing why something is running. It reveals the complete causality chain, including indirect causes across supervisors, containers, and services, which traditional tools require manual correlation to uncover.Can witr be used to analyze containerized applications?
Yes, witr is designed to trace components within containerized environments, allowing users to understand the origin and startup chain of processes and services running inside containers.
What are the advantages of using the interactive TUI over the CLI output?
The interactive TUI provides a dashboard-like view that allows for dynamic exploration and visualization of the causality chains, which can be more intuitive for complex scenarios compared to parsing machine-readable JSON or standard CLI output.
Is there a way to try witr without installing it on my local machine?
Yes, you can try witr in your browser through a simulated Linux box, which offers a guided tutorial and a free-play sandbox without requiring any local installation.
Source: github.com