Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Glances

nicolargo.github.io

  • Free plan
  • Open source
  • Windows
  • macOS
  • Linux
  • Web
  • Android
  • API
  • Self-hosted

What Glances is

Glances is a free, open-source tool for viewing real-time system statistics and running processes across platforms. Its monitoring covers CPU, memory, system load, processes, network, disk I/O, sensors, filesystems, containers, alerts, and uptime. Client/server mode supports remote monitoring through a terminal, Web interface, or API, and the built-in Web UI lets users monitor a system from a browser-equipped device. It provides XML-RPC and RESTful JSON APIs, while its Web server mode exposes a REST API. Statistics can be exported to CSV or JSON files, databases such as InfluxDB and Prometheus, brokers such as RabbitMQ and Kafka, or a REST endpoint. The project documents Docker and Podman support and describes Docker and LXC container monitoring in its README. Glances can be installed with pip, pipx, Homebrew, Linux and FreeBSD packages, or Docker images. Version 4 requires Python 3.10 or higher; the default installation omits Web interface dependencies, with separate extras for Web, GPU, containers, exports, and MCP. Version 4.5.1 and higher can provide an MCP server for AI assistants.

Who it suits

Glances suits administrators and developers who want system and process monitoring across platforms, including remote and container monitoring. Users should be comfortable managing Python requirements and optional dependencies for some features.

Good to know, and what to watch

  • Free and open source under the LGPL version 3 license.
  • Monitors CPU, memory, processes, network, and uptime.
  • Supports remote monitoring through terminal, Web UI, or API.
  • Exports statistics to files, databases, brokers, or REST.
  • Documents Docker and Podman monitoring.
  • Glances 4 requires Python 3.10 or higher.
  • Web interface dependencies are not installed by default.
  • Features such as GPU, containers, and MCP need extras.

Glances

Free

Open-source Glances

Free

Free plan

Getting started

  1. Open the Glances website and choose an installation route
  2. Install with pip, pipx, Homebrew, a Linux or FreeBSD package, or a Docker image
  3. Use the default monitor, adding optional extras for web, GPU, containers, exports or MCP
  4. Run client/server mode for remote monitoring through a terminal, web interface or API
  5. Connect exports to CSV, JSON, InfluxDB, Prometheus, RabbitMQ, Kafka or a REST endpoint

Limits to check

Glances is free, but the default installation omits Web interface dependencies. Optional capabilities such as GPU, container monitoring, exports and MCP require separate extras, and Glances 4 needs Python 3.10 or newer.

The Club's review

Overview

Glances is a free, open-source system monitor that brings live machine statistics and process activity into one view. It is best suited to administrators and technically confident users who want to monitor their own machines locally or remotely. Its range of access and export options is a strong draw, but some features require extra dependencies and version 4 requires Python 3.10 or later.

Key features

System and process monitoring

Glances covers CPU, memory, system load, processes, network traffic, disk I/O, sensors, filesystems, containers, alerts and uptime. That breadth makes it useful for checking overall machine health as well as tracking running processes, without limiting it to a single metric or workload. Server auto-discovery and script or command alert actions can also suit users who want monitoring to prompt a local response.

Remote access and integrations

Client/server mode lets users inspect a remote system from a terminal, browser or API. The built-in Web interface is a practical option when the monitoring machine is not nearby or a terminal is inconvenient. Glances also provides XML-RPC and RESTful JSON APIs, and its Web server exposes a REST API.

Statistics can be exported to CSV or JSON files, databases such as InfluxDB and Prometheus, brokers such as RabbitMQ and Kafka, or a REST endpoint. Docker and Podman support is documented, and the project also describes Docker and LXC container monitoring. Glances 4.5.1 and later can provide an MCP server for AI assistants. These integrations make it more adaptable than a monitor meant only for on-screen inspection, though users should expect to configure the routes they need.

Installation and requirements

Glances can be installed with pip, pipx, Homebrew, Linux or FreeBSD packages, or Docker images. The main catch is that the default installation does not include dependencies for the Web interface, and features such as GPU monitoring, containers, exports and MCP have separate extras. Users should check which capabilities they need before choosing an installation method. Glances 4 requires Python 3.10 or newer; Python 2 and earlier Python 3 releases are unsupported.

Pricing

Glances is free at no cost, with no free trial because there is no paid plan to try. The free plan is the open-source system monitor, but optional features require extra dependencies. There are no paid tiers or seat-based plans to weigh; the main trade-off is the setup work needed to enable additional capabilities. The project is distributed under the LGPL version 3 license.

Platforms

Glances supports GNU/Linux, FreeBSD, macOS, Windows and Android, with Web, API and self-hosted availability. This range can suit mixed environments and users who want to monitor a machine remotely. It is an agent-based monitor, rather than a hosted monitoring service. Version 4.x is supported for security updates; versions below 4.0 are unsupported.

Who it's for

Glances is a good fit for administrators, developers and other technically capable users who want a broad view of machine and process activity, especially when remote access, container monitoring or metric exports matter. It is less suitable for someone seeking a ready-to-use browser dashboard with no dependency setup: the Web interface and several other capabilities require optional packages.

Pros and cons

Pros

  • Broad monitoring coverage: CPU, memory, processes, storage, networking, sensors, containers, alerts and uptime are available in one tool.
  • Flexible remote access: Terminal, Web and API routes let users choose how to inspect remote systems.
  • Useful export choices: File, database, broker and REST exports support workflows beyond viewing metrics in Glances itself.
  • Free and open source: There is no paid plan cost, and the project uses the LGPL version 3 license.

Cons

  • Optional features take setup: The default installation omits Web dependencies, and several features need separate extras.
  • Newer Python is required for version 4: Python 3.10 or later rules out older environments.
  • Older major versions lack security support: Versions below 4.0 are unsupported for security updates.

Alternatives

For process-management alternatives, PM2 is worth considering if you want an open-source process manager with a real-time Web interface; its free Runtime plan covers that use, while its pricing model also includes paid options.

Process Lasso may suit Windows users looking for a Windows-only process tool with a free plan and paid single-PC subscriptions. Ambih Monitor is another Windows option; its free tier includes live monitoring and five-session history per project, while its Pro tier adds unlimited session history and anomaly detection.

If you prefer a free open-source monitor focused on Linux, macOS or self-hosted use, Monit is an alternative. Linux users considering another performance monitor can also look at atop. bottom (btm) is a free option for Linux, macOS and Windows. Windows users seeking a free process utility can consider ManageEngine Free Process Manager. For remote process exploration on Windows, Remote Process Explorer offers a free personal license limited to non-commercial use on one computer, as well as a paid business license.

For broader category browsing, see Process Monitoring Software, Hardware Monitoring Software and Container Monitoring.

Verdict

Choose Glances if you want a free, cross-platform monitor that combines system and process visibility with remote access and multiple export routes. Its main advantage is that range; its main drawback is the extra setup needed for optional features, along with the Python 3.10 requirement for version 4. Look elsewhere if you need a simpler, immediately configured monitoring interface or a tool dedicated to a narrower task.

The verdict

Glances provides broad system monitoring and several remote-access and export routes at no cost. Check its Python requirement and install optional dependencies for features not included by default.

Questions people ask

Is Glances free?

Yes. The listed Glances plan costs nothing and is an open-source system monitoring tool.

Which platforms does Glances support?

Supported platforms include Linux, BSD, macOS, Windows, Android, web, API and self-hosted deployments.

Can Glances monitor systems remotely?

Yes. Client/server mode supports remote monitoring through a terminal, web interface or API.

Can it monitor containers?

The project documents Docker and Podman support, and its README describes Docker and LXC monitoring.

What APIs and exports are available?

Glances provides XML-RPC and RESTful JSON APIs. Statistics can be sent to CSV, JSON, InfluxDB, Prometheus, RabbitMQ, Kafka or a REST endpoint.

What license does Glances use?

The project states that Glances is distributed under the LGPL version 3 license.

What the maker publishes

AI integration
Glances 4.5.1 and higher can provide an MCP server for AI assistants. source
Alerts
Glances includes monitoring alerts and configurable thresholds. source
APIs
Glances provides XML-RPC and RESTful JSON APIs, and its Web server mode exposes a REST API. source
Containers
The project documents monitoring support for Docker and Podman, and describes Docker and LXC container monitoring in its README. source
Container support
The official feature list names Docker and Podman container monitoring. source
CPU monitoring
The product displays CPU utilization information. source
Creator
The project identifies Nicolas Hennion as its creator and maintainer, with development by a contributor community. source
Deployment
Glances can be installed with pip, pipx, Homebrew or Linux and FreeBSD packages, and Docker images are available. source
Disk monitoring
Glances measures disk I/O. source
Documentation depth
Official documentation covers installation, quickstart, configuration, command reference, plugins, exports, APIs, and MCP usage. source
Exports
Statistics can be exported to CSV and JSON files, databases including InfluxDB and Prometheus, brokers including RabbitMQ and Kafka, or a REST endpoint. source
Exports and integrations
Supported export destinations include CSV, JSON, InfluxDB, ElasticSearch, PostgreSQL/TimeScale, Cassandra, ClickHouse, CouchDB, OpenTSDB, Prometheus, StatsD, Riemann, Graphite, RabbitMQ/ActiveMQ, NATS, ZeroMQ, Kafka, and REST. source
Extensibility
The project uses an open plugin and export-module architecture intended for developer extensions. source
Filesystem and RAID
Filesystem and RAID information are included among the monitored data. source
Hardware sensors
Sensor readings such as temperatures and fan speeds are supported. source
Installation
The documented installation paths include pip, pipx, uvx, operating-system packages, and optional extras such as web or all. source
Latest release
PyPI lists Glances 4.5.8 as released on October 11, 2026. source
License
The project says Glances is distributed under the LGPL version 3 license. source
License
Glances is distributed under the GNU LGPL version 3, expressed on PyPI as LGPL-3.0-only. source
Limit: process control
Glances does not let users renice or kill processes, so process management requires another tool. source
Limit: process-list navigation
The process view shows only the top processes that fit on screen and lacks scrolling or reverse-sort controls. source
Limit: Python weight
A Linux comparison guide says Python makes Glances heavier than htop and that some plugins need additional Python packages. source
Limit: resource overhead
An Opensource.com test reported typical CPU use of about 10% to 20%, with up to 40% of one CPU on a large active system. source
Limit: web security default
The Linux comparison guide warns that the web interface has no password unless the operator configures one. source

Checked against the maker's pages on 15 Oct 2026.