OpsHome NOC and Console shown across desktop, tablet and mobile devices
OpsHome NOC has always been centered around iOS.
A phone is ideal for quickly checking service status, asset health, incident changes, and private infrastructure. As the number of monitored resources grows, though, larger screens become useful too: reviewing the whole environment from a computer, browsing incidents on an iPad, or keeping infrastructure status visible on a dedicated display.
That is where OpsHome Console comes in.
With Console, the monitoring, asset, and incident views from OpsHome NOC can also be used in browsers, on tablets, and on larger displays. Windows, macOS, Linux, iPad, and mobile browsers can all become ways to view the same OpsHome environment.
One Console, Multiple Screen Sizes
Console is designed to adapt to different browser and screen sizes.
On desktop browsers, the larger workspace makes it easier to review monitor matrices, infrastructure assets, trends, and incident details.
An iPad in landscape mode works well for viewing a broader operational picture, while portrait mode is convenient for browsing incidents and asset information.
On mobile browsers, the layout reorganizes the information hierarchy so that important status, incidents, and resources remain readable.
For homelabs, workbenches, or long-running monitoring setups, Display Mode can keep Console visible on a dedicated screen.
Desktop, tablet, and mobile all use the same Console experience, with the layout and information density adapting to the available screen space.
OpsHome Console responsive interface across desktop, iPad, iPhone and external display
Overview: See What Is Happening Now
When Console opens, Overview provides a current summary of the OpsHome environment.
The page brings together resource counts, active risks, infrastructure health, Active Incidents, 24-hour trends, and assets that need attention.
You can check Overview first to understand whether the environment is healthy, then move into Monitors, Assets, or Incidents when more detail is needed.
If Critical or Warning conditions are present, they are reflected in the overall status and Priority Assets without requiring you to inspect devices one by one.
For day-to-day monitoring, this reduces a lot of unnecessary navigation.
OpsHome Console Overview showing system health, active risks, infrastructure trends and priority assets
Monitors: Public and Private Monitoring in One View
OpsHome NOC supports monitoring types including HTTP, HTTPS, TCP, ICMP, SSL, and Domain checks.
The Monitors page in Console is designed for reviewing multiple targets on a larger screen. Each monitor can show its current state, latency, availability, and recent trend information.
Alt text:
OpsHome Console Monitors view showing public and private service monitoring
Cloud Monitors and Private Probe Monitors are organized separately, keeping public checks and internal network monitoring easy to distinguish.
Homelab and SOHO environments often include a mixture of web services, NAS systems, internal management pages, databases, Docker services, virtualization platforms, and applications that are only available on the local network.
Those internal services do not need to be exposed to the public internet just to be visible in Console.
Private Monitoring without Port Forwarding remains one of the core ways OpsHome handles private infrastructure. Internal resources stay inside the private network, without requiring public port forwarding for NAS systems, databases, or internal web services simply to check their status remotely.
Assets: Monitor the Infrastructure, Not Just the Service
Knowing whether a service is online is useful, but it does not always tell the whole story.
A NAS may still be reachable while its storage is approaching capacity. A virtualization host may remain online while CPU, memory, or datastore conditions require attention. A Linux host can also experience resource pressure while its services continue to respond.
OpsHome therefore includes asset-level monitoring as well.
Current infrastructure coverage includes Synology, Proxmox, VMware, and Linux, together with related virtual machines, containers, storage, and workloads.
The Assets page in Console brings these systems together in a single infrastructure view.
OpsHome Console Assets view showing virtualization, NAS, Linux and infrastructure telemetry
Each platform keeps the information that matters to it. Virtualization environments emphasize compute resources and workloads, NAS systems focus more heavily on storage and disk health, and Linux hosts provide general system-level visibility.
That gives OpsHome coverage across:
Virtualization · NAS · Docker · Linux
Service status and infrastructure health can be reviewed within the same OpsHome environment, making it easier to understand what needs attention.
Incidents: More Context on a Larger Screen
Phone notifications are useful for telling you that something happened.
When you want to look deeper, a larger screen is better suited to showing the full incident context.
Console includes a dedicated Incident Workspace for both active and recovered incidents, with severity, start time, duration, affected resources, incident summaries, and timelines.
OpsHome Console Incident Workspace showing incident details, affected resources and timeline
Incidents can be switched quickly from the list, while the detail area keeps the relevant context and resource information visible.
This layout is especially useful for longer-running Warning or Critical conditions, as well as for reviewing incidents that have already recovered.
Console keeps the experience read-only, allowing users to focus on monitoring results and incident context.
Light and Dark
Console includes both Light and Dark themes.
Light Mode works well for everyday desktop use and bright environments. Dark Mode is better suited to monitoring displays, nighttime use, and long-running Display Mode setups.
Changing themes does not change the underlying features or data; it only changes how the interface is presented.
Theme support is also available across desktop, tablet, and mobile layouts.
OpsHome Console Overview shown in light and dark themes
Sign In With the Same Apple Account
A web service often means another account and another password to manage.
OpsHome Console continues to use the same Apple account experience as OpsHome NOC.
Existing OpsHome NOC users can sign in to Console with the same Apple account, without creating a separate Console username or password.
Authentication is handled by Apple. OpsHome does not receive or store the user's Apple ID password.
The sign-in connection uses encrypted communication, and Console establishes a time-limited browser session.
This keeps the App and Web Console experience consistent without adding another set of login credentials.
Beyond the iPhone, Open a Browser
OpsHome NOC continues to provide the quick, portable monitoring experience on iOS.
Console adds several practical ways to use the same environment:
Review a larger monitoring matrix on Windows or macOS.
Keep an OpsHome view open next to a Linux workstation.
Browse assets and incidents from an iPad.
Run Display Mode on a dedicated screen.
The same OpsHome data can stay visible across phones, desktops, tablets, and larger displays.
For a product that originally used the iPhone as its primary interface, Console expands OpsHome into more everyday monitoring environments.
OpsHome NOC + Console
The current OpsHome experience can be summarized around four areas:
Private Monitoring
No Port Forwarding
Virtualization · NAS · Docker
Secure by Design
OpsHome NOC provides the mobile monitoring experience on iPhone, while Console brings the operational view to browsers, tablets, and larger displays.
For a quick status check, open the app.
For more room to review resources, trends, and incidents, open Console.
For continuous visibility, keep Console running on a dedicated display.
Console: https://console.opshome.run
Website: https://app.opshome.run
Documentation: https://docs.opshome.run
Top comments (0)