Monitorify
A terminal montioring tool for linux
- Features
- CPU monitoring
- RAM monitoring
- Network monitoring
- Disk monitoring (I/O and storage capacity)
- Process monitoring
- Background daemon
- Customization menu (toggle widgets, set intervals, and change history window)
- Historical graphs
Requirements
- Python: 3.10+
- OS: Linux (relies on
/procand/sysfilesystems) - Terminal: Minimum 80 columns × 24 lines recommended
Installation
Using pipx
pipx install git+https://github.com/leonst036/Monitorify.git
Or from PyPI:
pipx install monitorify
Using pip
pip install git+https://github.com/leonst036/Monitorify.git
Using source
git clone https://github.com/leonst036/Monitorify.git
cd Monitorify
pip install .
Usage
monitorify
Background Daemon
The daemon collects metrics continuously to SQLite, even when the dashboard is closed.
Manually (foreground)
monitorify-daemon
Always-On via systemd --user
Create the service file at ~/.config/systemd/user/monitorify.service:
[Unit]
Description=Monitorify Metrics Collector Daemon
[Service]
ExecStart=%h/.local/bin/monitorify-daemon
Restart=always
[Install]
WantedBy=default.target
Enable and start it:
systemctl --user daemon-reload
systemctl --user enable --now monitorify
Check status or logs:
systemctl --user status monitorify
journalctl --user -u monitorify -f
Stop or disable:
systemctl --user stop monitorify
systemctl --user disable monitorify
File Locations
Monitorify follows XDG Base Directory conventions — nothing is written to the install directory.
| Purpose | Default Path | Override |
|---|---|---|
| Database | ~/.local/share/monitorify/monitorify.db |
MONITORIFY_DB_PATH env var |
| Daemon PID | /run/user/<uid>/monitorify/daemon.pid |
MONITORIFY_PID_PATH env var |
| Collection interval | 1.0 seconds |
MONITORIFY_INTERVAL env var |
| Data retention | 604800 s (7 days) |
MONITORIFY_RETENTION env var |
Remote
To use Monitorify remotely over SSH on your server, you can set the following parameters:
--ip– Set the target IP address.--port– Set the SSH port.--username– Set the username for the remote host.--password– Set the password for the SSH server.--key_filename– Set the path to an SSH key (optional).--host– Manage remote hosts in the database (add,list,remove).
Tech Stack
- Language & TUI: Python, Textual
- Database: SQLite
- Target OS: Linux
Uninstalling
# If installed via pipx
pipx uninstall monitorify
# Remove stored data
rm -rf ~/.local/share/monitorify
rm -rf /run/user/$(id -u)/monitorify
Metadata
Release files for monitorify 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| monitorify-1.1.0.tar.gz | 36.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| monitorify-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 80.5 kB
Release files / monitorify-1.1.0.tar.gz
| Download URL | monitorify-1.1.0.tar.gz |
|---|---|
| Size | 36.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f6c4310cc5c223cae9bdd9475e1e5ed2782a90246abfa8dbc50e266caccdd9d
|
|
BLAKE2b-256 checksum How to use checksums |
3a4d0fcba41919c22a63ae81a901fb42a520f4e865b854962e8d981b46feea1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logRelease files / monitorify-1.1.0-py3-none-any.whl
| Download URL | monitorify-1.1.0-py3-none-any.whl |
|---|---|
| Size | 43.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76adf332f0f68e1c6a02584cb73d11e6878f1d8601ef90209b6aad285d1ad25c
|
|
BLAKE2b-256 checksum How to use checksums |
62fdb556abb30003d1f5dc29ac5d3acfdda07e4401122b16579e7823afcc5044
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logSecurity for monitorify 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for monitorify-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.