Public services
Websites, APIs, SSL certificates, domains, and network checks still matter. OpsHome includes public monitoring as part of the wider view.
Homelab monitoring is no longer just ping checks
Modern homelabs are small infrastructure environments. A single operator may run public websites, private services, a NAS, Proxmox nodes, Linux hosts, Docker containers, internal dashboards, status pages, automation systems, and side projects. A simple uptime monitor can tell you whether one endpoint responded, but it often cannot explain the broader operational state.
OpsHome NOC is built for people who operate a personal homelab, NAS, Proxmox server, Docker host, or private self-hosted services and want to see the state of their environment from an iPhone. It is not just another uptime monitor. It is a NOC-style operations view built for homelab operators.
What a NOC-style homelab view should show
Private services
Use Docker Probe to monitor internal HTTP, HTTPS, and TCP targets without exposing private management panels.
Infrastructure assets
Review Synology, Proxmox, Linux, Docker, and related asset health from the same iPhone-first interface.
Events and history
See alerts, recoveries, downtime, and Docker container event timelines so short incidents do not disappear.
Public services plus Private Monitors in one view
Public monitoring and Private Monitors solve different problems. Public checks show whether internet-facing services are reachable from outside. Private Monitors show whether the systems behind your router, firewall, or NAT are healthy. A homelab operator usually needs both.
OpsHome keeps those concerns connected. A public website may depend on a private Docker container, a reverse proxy, a NAS share, or a Proxmox VM. Seeing public status, Docker Probes, infrastructure connections, Private Monitors, and recent events in one place helps you move from "something is down" to "this is probably where I should look first."
Map and group Docker Probes by location
Homelab infrastructure often has physical meaning. A Docker Probe might live on a Synology NAS, a mini PC, a Proxmox node, a Linux server, or a small remote site. OpsHome can group Docker Probes, infrastructure connections, and Private Monitors by location so the private side of the map reflects the way your environment is actually organized.
This is especially useful when the same app tracks both public and private monitoring. Public PVE endpoints can stand alone, while private PVE, Synology, Linux, and Docker infrastructure connections should be understood under the Docker Probe that can reach them.
Docker container events belong in the operations view
Containers often fail quietly. A restart or OOM kill may happen and recover before you open the app. A NOC-style homelab view should show more than current status; it should preserve enough recent event context to explain why something looked unstable.
OpsHome can show supported Docker container events such as abnormal states, restarts, recoveries, and OOM kills when collected through Docker Probe. This helps the container layer become part of the same operational story as public checks, Private Monitors, and infrastructure connections.
When OpsHome is enough, and when you need heavier tools
OpsHome is useful for quick status review, mobile alerts, private monitoring through Docker Probe, and a practical homelab operations overview. It can complement tools such as Prometheus, Grafana, Docker logs, Proxmox UI, Synology DSM, and shell access.
It is not a replacement for every deep observability stack or production incident-management system. If you need second-level alerting, complete application logs, long-term metrics retention, distributed tracing, or enterprise on-call workflows, keep using dedicated tools. OpsHome's job is to make the first look fast and clear from your iPhone.
FAQ
Is OpsHome NOC only an uptime monitor?
No. OpsHome includes public monitoring, but its main value is giving homelab operators a NOC-style view across Docker Probes, infrastructure connections, Private Monitors, Synology, Proxmox, Linux hosts, and Docker containers.
Does OpsHome require exposing my home network?
No. Docker Probe makes outbound HTTPS connections and does not require inbound port forwarding.
Is OpsHome for enterprise production monitoring?
OpsHome is designed primarily for personal homelab and self-hosted operations. For production-critical systems, pair it with dedicated on-premise alerting.
Can I use OpsHome when I am away from my desk?
Yes. OpsHome is iPhone-first and is designed for quick status review, alerts, and history when you are not in front of your homelab.
Does OpsHome replace Proxmox UI, Synology DSM, or Docker logs?
No. Use administrative tools for administration and debugging. Use OpsHome for quick operations visibility, alerts, and recent history.
Related OpsHome topics
Focused OpsHome tools
OpsHome NOC covers broader infrastructure monitoring. For narrower jobs, use the focused OpsHome tools below.
Turn your homelab into an iPhone-first NOC view
Use OpsHome NOC to review public services, Docker Probes, infrastructure connections, Private Monitors, alerts, and recent history from one place.