DEV.co
Open-Source Observability · Abdenasser

neohtop

NeoHtop is a modern desktop system monitor built with Rust, Tauri, and Svelte that tracks CPU, memory, and process activity in real-time with a polished UI. It offers cross-platform support (macOS, Linux, Windows) with features like process search, filtering, pinning, and termination. The project is actively maintained (last push March 2026) and has gained significant community interest with over 9,000 stars.

Source: GitHub — github.com/Abdenasser/neohtop
9k
GitHub stars
282
Forks
Svelte
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
RepositoryAbdenasser/neohtop
OwnerAbdenasser
Primary languageSvelte
LicenseMIT — OSI-approved
Stars9k
Forks282
Open issues18
Latest releasev1.2.0 (2025-06-02)
Last updated2026-03-30
Sourcehttps://github.com/Abdenasser/neohtop

What neohtop is

NeoHtop is a Tauri-based desktop application using a Rust backend for system metrics collection and a SvelteKit/TypeScript frontend for UI rendering. It provides native performance through WebView integration and supports regex-based process filtering, theming via CSS variables, and privilege escalation for monitoring protected processes. A companion CLI variant built with Go (neohtop-cli) offers terminal-based monitoring.

Quickstart

Get the neohtop source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/Abdenasser/neohtop.gitcd neohtop# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Local Development & Testing

System monitor for developers who need real-time process, CPU, and memory visibility during local development and debugging cycles. Lightweight alternative to OS-native tools with better UX.

Cross-Platform Deployment Monitoring

Organizations needing consistent system monitoring UI across macOS, Linux, and Windows without vendor lock-in. Useful in heterogeneous development or QA environments.

Process Management for Power Users

Advanced search, filtering, pinning, and termination features appeal to users managing complex application stacks or requiring granular process inspection beyond standard system utilities.

Implementation considerations

  • Requires Node.js v16+, Rust (latest stable), and platform-specific tooling (Xcode CLI on macOS). Build and deployment infrastructure must support Tauri stack.
  • Some processes require sudo/elevated privileges; macOS users may need to run via `sudo /Applications/NeoHtop.app/Contents/MacOS/NeoHtop` and Linux users via `pkexec`. Permission model varies by platform.
  • Community-maintained packages (Homebrew, AUR, Scoop, Fedora) exist but are unofficial and not security-reviewed by the core team. Official builds are on GitHub Releases only.
  • Themes and search use CSS variables and regex respectively; customization requires frontend code changes. No plugin or extension architecture exposed.
  • Single-user, local-only architecture. Not designed for multi-user access or remote monitoring; each user needs their own installed instance.

When to avoid it — and what to weigh

  • Enterprise Production Monitoring — Not designed for server-side production telemetry, centralized logging, or SLA-backed alerting. Consider dedicated APM or infrastructure monitoring platforms (Prometheus, Grafana, Datadog) instead.
  • Headless/Remote System Administration — Requires a graphical display and runs only on desktop OS. Not suitable for headless servers, containers, or remote CLI-only environments.
  • Compliance-Heavy Industries — Limited audit trail, no role-based access control, and no formal security certification. Healthcare, finance, or regulated sectors should verify licensing and security posture independently.
  • Mission-Critical Process Monitoring — No guarantee of data accuracy, persistence, or historical retention. Lacks enterprise-grade SLAs, redundancy, or failover mechanisms for critical infrastructure.

License & commercial use

Licensed under MIT (permissive OSI license). Allows free use, modification, and redistribution in commercial and private projects with minimal obligations (retain license notice and copyright).

MIT license permits commercial use. However, no warranties or liability protection are provided. Use in commercial products is permitted but should be evaluated alongside the project's stability and your internal security/legal review. Community-maintained package versions carry unknown provenance; official GitHub Releases are recommended for production use.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitPossible
Assessment confidenceHigh
Security considerations

No security audits, penetration tests, or formal threat model documented. Runs with elevated privileges (sudo/pkexec) on some platforms; privilege escalation design should be reviewed before deployment in sensitive environments. Tauri framework handles WebView sandboxing, but application-level security practices are unknown. Community packages carry supply-chain risk; verify checksum integrity if used. No built-in telemetry or update mechanism documented; verify update sourcing.

Alternatives to consider

htop / btop

CLI-native, lightweight alternatives with decades of stability and no UI framework overhead. Better for headless/remote environments but lack modern graphical interface.

Activity Monitor (macOS) / Task Manager (Windows) / GNOME System Monitor (Linux)

OS-native, well-supported, require no installation, and integrate deeply with OS APIs. Trade customization and cross-platform consistency for native polish and reliability.

Prometheus + Grafana

Enterprise-grade monitoring stack with time-series persistence, alerting, multi-host support, and production SLAs. Overkill for local development; requires infrastructure.

Software development agency

Build on neohtop with DEV.co software developers

Download official builds from GitHub Releases or evaluate integration with your infrastructure. Assess security and privilege escalation design for your environment.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

neohtop FAQ

Can NeoHtop monitor processes on remote servers?
No. NeoHtop is a local desktop application and does not support remote monitoring or SSH tunneling. For remote infrastructure, use Prometheus, Grafana, or similar APM tools.
Do I need elevated privileges to run NeoHtop?
Not always. Basic process monitoring works as a regular user. To see all processes (including kernel and other users' processes), elevated privileges are required: `sudo` on macOS or `pkexec` on Linux.
Is there a CLI version?
Yes. neohtop-cli is a separate Go-based terminal monitor available on npm. It is maintained by the same author but is a distinct project with its own release cycle.
Can I use unofficial community packages (Homebrew, AUR, Scoop) in production?
Proceed with caution. Community packages are unofficial and not reviewed or endorsed by the NeoHtop team. Verify checksums and provenance. Official builds from GitHub Releases are recommended for production environments.

Software developers & web developers for hire

DEV.co helps companies turn open-source tools like neohtop into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source observability stack.

Ready to Deploy NeoHtop?

Download official builds from GitHub Releases or evaluate integration with your infrastructure. Assess security and privilege escalation design for your environment.