Netron vs Phoenix
A data-driven comparison of two Machine learning visualization tools: popularity, development activity, licensing and installation. Updated .
Key differences
- Netron has 2.9× as many GitHub stars as Phoenix (33.5K vs 11.7K).
- Phoenix had more development activity over the last 12 months: 3,725 commits vs 926.
- Phoenix is downloaded 9× as often on PyPI (145.1K vs 16.1K per week).
- Netron is licensed under MIT; Phoenix under Elastic-2.0.
- Netron is written primarily in JavaScript, Phoenix in Python.
- Netron is the older project: its repository was created in 2010, Phoenix's in 2022.
By the numbers
- Netron
- Phoenix
Show data as a table
| Metric | Netron | Phoenix |
|---|---|---|
| GitHub stars | 33,544 | 11,704 |
| PyPI downloads / week | 16,117 | 145,091 |
| Commits, last 12 months | 926 | 3,725 |
| Contributors | 1 | 235 |
| Forks | 3,185 | 1,181 |
Development activity
Commits per month to each default branch, last 12 complete months.
- Netron
- Phoenix
Show data as a table
| Month | Netron | Phoenix |
|---|---|---|
| Oct 2025 | 85 | 235 |
| Nov 2025 | 93 | 198 |
| Dec 2025 | 89 | 156 |
| Jan 2026 | 97 | 158 |
| Feb 2026 | 103 | 587 |
| Mar 2026 | 92 | 328 |
| Apr 2026 | 58 | 289 |
| May 2026 | 68 | 287 |
| Jun 2026 | 61 | 252 |
| Jul 2026 | 61 | 463 |
| Aug 2026 | 56 | 417 |
| Sep 2026 | 63 | 355 |
Side by side
| Attribute | Netron | Phoenix |
|---|---|---|
| Description | Viewer for neural network, deep learning and machine learning models. | ML observability in a notebook with UMAP visualizations |
| Category | Machine learning visualization tools | Machine learning visualization tools |
| License | MIT | Elastic-2.0 |
| Language | JavaScript | Python |
| Status | Active | Active |
| Latest release | v9.3.1 () | arize-phoenix-v20.19.0 () |
| Last commit | ||
| Repository created | ||
| Open issues | 16 | 946 |
| Install | pip install netron | pip install arize-phoenix |
Which should you choose?
Popularity and activity are only part of the story. Consider which ecosystem you work in, the chart types and interactions you need, how much data you render, and whether the license fits your project. Both tool pages list alternatives if neither is quite right.