An IT environment doesn't have to be large to be complicated.
A homelab might run Proxmox VE, Docker, a NAS, and a handful of self-hosted apps. A small office might depend on internal servers, business websites, and cloud services. An IT administrator might need to keep an eye on several hosts, many service endpoints, and infrastructure spread across different networks.
The scale differs, but the daily questions are the same: Is the service up right now? Can people reach the internal app? Is the infrastructure healthy? After an outage, can I quickly see what changed? And when users can't reach a service, is there somewhere they can check its status?
OpsHome NOC is a lightweight monitoring and operations platform built around those questions. It combines public service checks, private network monitoring, Docker and infrastructure integrations, incident history, a browser-based Web Console, and Status Pages for external visitors.
Whatever the size of your environment, OpsHome NOC does one thing: it lets you see the state of your services and infrastructure at a glance.
- Product website: https://app.opshome.run/
- Documentation: https://docs.opshome.run/
What Is OpsHome NOC?
OpsHome NOC is a lightweight network and infrastructure monitoring platform for homelabs, self-hosted services, home offices, small businesses, and any other setting where you need to watch network services and IT infrastructure.
It is built around these capabilities:
- Service monitoring: Check public services, plus HTTP, HTTPS, and TCP endpoints inside private networks.
- Infrastructure visibility: View Proxmox VE, VMware, Synology NAS, Linux, and Docker environments through integrations.
- Events and history: Review state changes, alerts, recoveries, and event timelines.
- Mobile operations: Check status anywhere from the iPhone app.
- Browser-based operations: Use the Web Console to view monitoring and infrastructure information on a larger screen.
- Service status sharing: Show selected service status to users, customers, or other visitors through Status Pages.
OpsHome NOC does not try to replace dedicated log analysis, observability, or infrastructure management platforms. It adds a unified monitoring and status layer on top of the systems you already run.
Current version: OpsHome NOC v1.16 (as of October 2026).
Available metrics and features depend on the platform, connection method, permissions, and the scope of each integration. Please refer to the official documentation and your actual deployment. The sections below describe capabilities directly and do not repeat this caveat.
1. Public Monitoring and Private Network Monitoring
The two kinds of checks answer different questions.
Public monitoring verifies that websites, APIs, and other public endpoints are reachable from the outside. It suits business websites, public services, and SSL certificate checks.
Private network monitoring answers another question: from inside the network where the service actually runs, can it be reached? Typical scenarios include:
- Virtualization hosts and self-hosted apps in a homelab;
- File servers and internal business apps in a small office;
- Websites exposed through a reverse proxy whose backends stay on a private network.
Private network monitoring supports distributed deployment. As long as they belong to the same account, you can run Probes in different places, such as home, the office, a server room, or a VPS, and view them together in one place.
A successful public check doesn't mean your internal apps and infrastructure are healthy. And opening management interfaces just so an external system can monitor internal services creates security risk. The two approaches complement each other, giving you both an outside view and an inside view of your services.
2. Docker Probe: Connecting Private Networks
Docker Probe is the key component of private network monitoring. You deploy it on a Docker host that can reach your target services. It checks the configured services from inside the network and works with infrastructure integrations to collect data.
The Probe connects to OpsHome Cloud over outbound HTTPS. In general you don't need inbound port forwarding, and you don't need to expose internal services to the internet just to monitor them from the cloud.
Typical uses:
- Checking internal HTTP and HTTPS services;
- Testing TCP service reachability;
- Monitoring Docker container status and container events;
- Collecting infrastructure information.
Security recommendation: When deploying a Probe, mount the Docker Socket read-only, and use dedicated least-privilege accounts or API tokens for integrations such as Proxmox and Synology.
Related documentation:
- Docker Probe installation: https://docs.opshome.run/docs/docker-probe/install/
- Private HTTP, HTTPS, and TCP monitors: https://docs.opshome.run/docs/private-monitors/http-https-tcp/
- Synology integration: https://docs.opshome.run/docs/synology/add-synology/
3. Infrastructure Monitoring: More Than Checking Whether a Port Is Up
A service that answers requests isn't necessarily running on healthy infrastructure. A virtualization host may still be reachable while its storage or virtual machines have problems. A NAS may be online while some of its resources are already abnormal. So besides availability checks, OpsHome NOC provides infrastructure information through integrations:
- Proxmox VE: View nodes, virtual machines, LXC containers, storage, and resource metrics. Connect with a dedicated API token and scope its permissions as needed.
- VMware ESXi / vSphere: View hosts, virtual machines, datastores, and resource information. The exact fields depend on your actual deployment.
- Synology NAS: Depending on DSM version and collection method, view system status, resources, storage, disks, and network information.
- Linux and Docker: Combine host information, container status, and service checks to understand the basic health of your runtime environment.
Apply the principle of least privilege to monitoring credentials, and avoid granting unnecessary administrative rights.
Related documentation:
- Infrastructure assets: https://docs.opshome.run/assets.html
- Proxmox API token guide: https://docs.opshome.run/articles/proxmox-opshome-api-token-guide.html
4. Incident History and Troubleshooting
The value of monitoring lies not only in spotting problems but also in keeping enough information to see how a problem unfolded.
OpsHome NOC provides an Incident Workspace that links events from monitors and infrastructure assets. It shows active and resolved incidents, severity, duration, affected resources, an evidence timeline, and recovery information. Combined with Docker container events, it helps you tell apart:
- A public endpoint that is unreachable;
- A private service that failed an internal check;
- A container that restarted or entered an abnormal state;
- Infrastructure that is reporting an anomaly;
- A brief outage that has since recovered on its own.
For the specifics of how much history is kept, see the official documentation: https://docs.opshome.run/
These records help narrow down your investigation, but they cannot automatically diagnose every failure. Root-cause analysis still requires infrastructure management tools and application logs.
5. Web Console: Browser-Based Operations
The mobile app is ideal for quick status checks and receiving alerts. The Web Console is built for viewing your whole environment on a desktop, tablet, or wall display.
Main capabilities:
- Monitor matrix: Public checks and private Probe targets in a single matrix, showing availability, latency, protocol, and current state at a glance.
- Assets topology: Compute, storage, utilization, and workloads across Synology, Proxmox, VMware, and Linux.
- Incident context: Start from an active risk and trace it to affected resources, evidence, and incident history.
- Wall display mode: Turn a browser into a long-running status board.
- Experience: Light and dark themes, adapted to large desktop displays, iPad, and mobile browsers.
The Web Console is read-only by design. It is for reviewing state and investigating incidents. It provides no infrastructure control and does not replace the management interfaces of Proxmox, VMware, Synology, or Docker. Sign-in uses the same Apple account as the app (Sign in with Apple), and OpsHome never receives or stores your Apple Account password.
What the Web Console displays depends on your plan tier. See Section 9 for the limits of each plan.
To get started, add monitors and assets in the iPhone app, then open https://console.opshome.run/ in a browser. Your data syncs automatically.
Learn more: https://noc.opshome.run/console/
6. Status Pages: Showing Service Status to Users and Customers
Internal monitoring answers "how do operators understand the state of the system?" Service users have a simpler need: Is the service working right now, and is there a known outage?
A Status Page is a public-facing page. You choose which monitors to publish, and visitors can see the following without opening your monitoring dashboard:
- The current online state of each service and its latest check;
- 24-hour, 7-day, and 30-day uptime summaries;
- Response times;
- Recent incidents and recovery.
Sharing and control:
- Share by link or QR code. Scanning the QR code in the OpsHome app verifies that the page was issued by OpsHome.
- Access code protection is supported, and sharing duration can be set from 24 hours to permanent.
- Public pages never expose real IPs, domains, or internal network details.
- You can disable or delete a Status Page at any time from the app.
Typical scenarios: a small business showing customers the status of key services; a self-hosted app operator sharing a status page with users; a homelab owner giving family a single place to check. Meanwhile, administrators keep investigating with their internal tools.
You control what is public. Publish only services that are appropriate to share.
Learn more: https://noc.opshome.run/status-pages/
7. Three Entry Points, Three Roles
| Entry point | Main audience | Core purpose |
|---|---|---|
| iPhone app (iPad supported) | Operators | Configure monitoring, check status on the go, follow up on alerts |
| Web Console | Operators | Read-only browser monitoring, asset viewing, wall display |
| Status Pages | Users, customers, and other visitors | Show the service status the operator chooses to make public |
The iPhone app is available anywhere, the Web Console is for deeper observation, and Status Pages handle external communication. Together they cover the whole path from spotting a problem to understanding it to telling others.
8. Scope and Limits
OpsHome NOC suits individuals, small offices, business teams, and IT administrators who want a clear view of how their services are running. How well it fits depends on your devices, integrations, and actual needs.
It is not a replacement for log analysis, metrics platforms, distributed tracing, or security analytics systems, and it doesn't replace sound network segmentation, permission management, and credential protection. Its role is to add a layer of monitoring, observation, and status communication on top of your existing systems.
9. Getting Started
You don't need to connect everything at once. Start with your most important services and expand from there:
- Add public monitors for your key websites and APIs.
- Deploy a Docker Probe on a host that can reach your private network.
- Add Private Monitors for internal apps.
- Connect integrations such as Proxmox, VMware, and Synology as your environment requires.
- Check status and operations information in the iPhone app or the Web Console.
- When you need to communicate externally, set up a Status Page.
Get the App
OpsHome NOC is a free download on the App Store (requires iOS 17.6 or later). Core monitoring works without a subscription and without a credit card:
https://apps.apple.com/us/app/opshome-noc/id6763890679
Plans
| Free | Pro | Studio | |
|---|---|---|---|
| Price | $0 | $2.99/month or $24.99/year | $5.99/month or $49.99/year |
| Public monitor targets | 30 | 100 | 250 |
| Monitor types | HTTP / HTTPS / TCP / SSL / ICMP | All types, including UDP, DNS, Domain | All types and infrastructure integrations |
| Docker Probes | 1 (Synology) | 12 (multi-platform) | 25 (multi-platform) |
| Private Monitors | 2 | 50 | 150 |
| Asset sources | Synology assets | 12 (Proxmox VE, VMware vSphere, Linux, Synology) | 25 |
| Status Pages | 1 | 3 | 5, with 20 monitors per page |
| Minimum check interval | — | 3 minutes | 3 minutes |
| Telegram push alerts | — | Custom Telegram setup | Custom Telegram setup |
| Also included | Push alerts, SSL expiry reminders |
Prices are shown in USD. Your App Store may display a different local price.
Founder Benefit: Eligible early accounts registered before May 1, 2027 permanently keep 30 public monitors, 3 Synology Docker Probes, 6 Private Monitors, and 1 Status Page.
Official resources:
- Product website: https://app.opshome.run/
- Web Console: https://noc.opshome.run/console/
- Status Pages: https://noc.opshome.run/status-pages/
- Documentation: https://docs.opshome.run/
- Docker Probe installation: https://docs.opshome.run/docs/docker-probe/install/
- Private HTTP, HTTPS, and TCP monitors: https://docs.opshome.run/docs/private-monitors/http-https-tcp/
Closing
IT environments differ in size and purpose, but the core of monitoring is the same: know whether your services are healthy, understand the state of your infrastructure, and get useful information when something goes wrong.
Through public monitoring, Docker Probe, infrastructure integrations, and incident history, OpsHome NOC helps you keep track of how your services and infrastructure are running. The iPhone app and Web Console serve operators, and Status Pages serve external visitors.
Your Infrastructure. One Glance Away.
Top comments (0)