Understand your host
See CPU, memory, storage, and process usage. Follow systemd journals and inspect the services behind your applications.
Host visibilityOPEN SOURCE · SELF HOSTED
Your VPS.
One clear view.
Bring host resources, applications, logs, and availability together. Understand what’s running on your server—and what needs your attention.
MIT licensedRuns on your serverUbuntu + systemd
Resources — CPU, memory, storage, and system services.
Actual console screens · Demonstration data, not a live server.How the workspace works
Actual console screens · Demonstration data, not a live server.How the workspace works
Works with the services you already run. Detected when available, enabled when you choose.
DockerPM2NginxPostgreSQLRedisOllama
Bring the signals together
Less jumping between tools.
More understanding.
From a resource spike to a failing endpoint, start with a shared view of your host and the services around it.
Follow your applications
Discover PM2 and Docker runtimes, inspect logs, and check database availability. Keep optional sources out of the way until you need them.
Explore integrationsKeep outages in context
Configure HTTP and TCP checks, track incidents, and send webhook alerts. See observation coverage alongside the outcome.
Checks and alertsPM2 appsDockerNginx logsDatabases
system-opsOne Ubuntu host
A workspace for your server
Built for the VPS
you actually have.
Start with the sources detected on your host. Choose what to monitor, inspect the evidence, and build a workspace that fits your setup.
- Host monitoring with native Ubuntu and systemd
- Optional integrations with visible permission and source errors
- Freshness and unknown states kept alongside the data
- Protected metrics for optional Prometheus and Grafana
A clear path from here
Get it running.
Make it yours.
Practical guides for your first install, the integrations you need, and the moments something doesn’t work.
Your first install
Install the console, open it securely, and verify your first collection.
Follow the quick startYour configuration
Set credentials, select data sources, and enable optional integrations.
Configuration guideYour next answer
Find help with discovery, permissions, updates, and empty data.
Troubleshooting guideStart on your own infrastructure
From a terminal
to a clearer picture.
Use the native installer for host monitoring, or run the console in Docker with explicit mounts and a narrower host view.
Review the installer before execution. Node.js 24 is used by the project.
Read the docsUbuntu / interactive installation
# Download, inspect, then install
$ curl -fsSL https://raw.githubusercontent.com/dineshkorukonda/system-ops/main/scripts/install.sh -o /tmp/system-ops-install.sh
$ less /tmp/system-ops-install.sh
$ sudo bash /tmp/system-ops-install.shLoopback binding by default
Docker / from the repository checkout
$ cp .env.docker.example .env.docker
# Set credentials and mounted paths in .env.docker
$ docker compose --env-file .env.docker up -d --buildOpen source, from the first command
Your infrastructure.
A project we build together.
Inspect the code. Improve a guide. Help test an integration. System Ops is MIT licensed and community maintained, with a clear place to ask questions and contribute.
Readable code. Reviewable changes.
A contribution guide, project rules, and validation requirements.
Help where you need it.
Practical docs and best-effort community support.
Clear ownership.
You operate your host, control your credentials, and choose your integrations.
Before you get started
A few things
worth knowing.
More questions? Start with the guides or ask the community.
Find supportIs System Ops free and open source?
Yes. The project’s source is MIT licensed. Dependencies retain their own licenses, and support is community maintained on a best-effort basis.
Which installation should I choose?
Native Ubuntu/systemd is the primary deployment for host monitoring. Docker includes the console with a narrower view of host services. The installation guide explains the differences.
Does it replace an external monitoring service?
Local checks cannot observe a complete outage of their own host. Use an independent observer when you need off-host availability evidence. Optional Prometheus and Grafana have their own resource costs.
Can I control all my services from the console?
Most integration views provide monitoring and log inspection. System Ops supports its own native updater and configuration workflows; it is not a general-purpose remote shell or service-control panel.
Bring your VPS into view.
Start with one host. Connect the sources you need.