PocketNOC vs the Orion Web Console mobile view
Last updated: 2026-05-24
The Orion Web Console has a mobile-responsive view. Here is what it does well, what it does poorly, and when a native mobile client is worth installing.
Short answer
The Orion Web Console mobile view is free, in-band, and built into every Orion install. It works. It is also a 2014-era responsive HTML view of a UI designed for a 1080p desktop monitor, accessed through a mobile browser that has none of the affordances people expect from a phone app: no push notifications, no biometric lock, no offline state, no privacy screen in the app switcher, no app icon to long-press for quick alerts. If the mobile experience matters to your on-call team, the gap is large enough to be worth a native client. That's where PocketNOC fits.
At a glance
| PocketNOC | Orion Web Console mobile view | |
|---|---|---|
| Cost | Free demo, $99.99/yr Pro (pricing) | Included with Orion |
| Native iOS / Android | Yes | No (responsive web only) |
| Push notifications | Yes (Pro) | No |
| Biometric app lock | Yes | No (browser session only) |
| Privacy screen in app switcher | Yes | No |
| Touch-optimized UI | Yes | Partial (responsive HTML) |
| Works against your existing Orion install | Yes (SWIS API) | Yes (web URL) |
| Requires network reachability to Orion | Yes | Yes |
| Configuration (alerts, groups, reports) | No (by design) | Yes |
| Per-module screens (NPM/SAM/NTA/NCM/IPAM/DPA) | Yes, auto-detected | All, in the web UI |
What the Orion Web Console mobile view does well
It is free and it exists. Open the same Orion URL you use on the desktop in a phone browser, and the responsive design kicks in. You log in with the same account, you see real Orion data, and you can navigate to nodes, alerts, and resource pages. Nothing to install, nothing to license. If you are evaluating Orion or only need mobile access a few times a year, this is the right answer.
It also has full feature coverage. Anything you can do in the Orion Web Console you can do in the mobile view, including configuration: editing alerts, creating views, running reports. PocketNOC is intentionally scoped to monitoring; the Web Console is your tool for everything else.
Where it falls down for on-call work
No push notifications. Critical alert in Orion → nothing on the phone unless you (a) have email open and (b) Orion is configured to email you on alert. By the time the email lands and the notification sound plays and you unlock the phone and tap the email and follow the link to the web console and log in, you have lost a couple of minutes you didn't need to lose. With PocketNOC on the same network, the SWIS API gives the app the same alert state Orion's internal alert engine sees, and the app fires a native push immediately.
No biometric lock on the data. Once you log into the Orion Web Console in Mobile Safari, the session cookie sits there. Anyone who picks up the unlocked phone can see your infrastructure. PocketNOC locks the data behind Face ID / Touch ID with a configurable timeout, separate from the device lock.
No privacy screen. The app switcher on iOS and the recents stack on Android both show whatever was on screen. The Orion Web Console mobile view shows node names, IPs, and alert text. PocketNOC blanks the screen when the app goes inactive.
UI assumptions from a desktop layout. Orion's web UI was designed around 1920×1080. Responsive CSS scales it down, but tap targets are small, scroll behavior is awkward, and many resource pages still require horizontal scroll or pinch-zoom. PocketNOC's UI was designed for one column on a phone, no compromise.
Browser session lifecycle. The Web Console session expires. The browser sometimes loses scroll position when the phone wakes from sleep. The back button does unpredictable things inside a single-page app. None of that is PocketNOC's problem because the app holds state natively between sessions.
What you give up moving to PocketNOC
It is a third-party app. If you have an enforced policy that no software outside SolarWinds' shipping bundle is allowed to touch the Orion server, PocketNOC won't fit. The mitigations: read-only Orion account by default, no inbound network exposure required, no monitoring data on PocketNOC servers, source available for security review on request.
It is a subscription. $99.99/year per device, or $9.99/month, via App Store / Google Play.
It is monitoring-only. You can view node health, alerts, performance charts, storage volumes, interfaces, and service state. You cannot create alerts, edit thresholds, or modify the Orion configuration. The Web Console is still where that work happens.
What you get back
A mobile experience that was designed for the phone, by people who actually do on-call work. Push notifications that arrive within a few seconds of an Orion alert firing. Biometric lock on the data. Per-module screens that hide what you haven't licensed. Trust On First Use for self-signed certs so you don't need a public certificate just to make this work.
When to use which
| Situation | Use |
|---|---|
| Once-a-quarter need to spot-check Orion from the road | Web Console mobile view |
| Active on-call rotation expecting fast incident response | PocketNOC |
| Configuration changes (new alerts, edit groups) | Web Console (desktop or mobile) |
| Need biometric lock on infrastructure data | PocketNOC |
| Need push notifications | PocketNOC |
| Zero-budget evaluation | Web Console mobile view |
| Frequent enough to justify per-engineer subscription | PocketNOC |
Setup PocketNOC against your existing Orion
If you already have the Orion Web Console reachable from a phone (via VPN or any other path), PocketNOC works against the same SWIS port, typically 17778. Install on iOS or Android, point at https://your-orion-server:17778, accept the certificate via TOFU on first connect, log in with a dedicated read-only account. The app auto-detects your licensed modules.
Setup walkthrough: /docs. Common remote-access options: Cloudflare Tunnel.
Bottom line
The Orion Web Console mobile view is the right answer for occasional mobile access. PocketNOC is the right answer when mobile is the workflow. When you are paid to be reachable and the phone is the first thing you reach for at 3am, the browser is not the right tool. They solve different problems and coexist on the same Orion install without conflict.
For teams evaluating third-party mobile clients, also see PocketNOC vs SolarWinds Mobile Admin and PocketNOC vs Grafana Cloud.
FAQ
Does the Orion Web Console mobile view cost anything?
No. It is part of every Orion install. There is no additional license and nothing to activate on the server side. The cost is in user experience and the operational shape of how you reach it from a phone.
Can I use the Orion mobile web view without exposing my Orion server to the internet?
Yes, but only if your phone is on the same network as the Orion server. That means corporate VPN, a tunnel like Cloudflare Tunnel, or a mesh network like Tailscale or ZeroTier. The same reachability constraints apply to PocketNOC. Neither option requires the Orion server to be publicly accessible.
Does PocketNOC replace the Orion Web Console?
No. The Web Console is still where you configure alerts, run reports, manage groups, and perform administrative tasks. PocketNOC is scoped to monitoring: viewing what is happening, acknowledging alerts, reading performance charts. Administrative changes remain in the Web Console.
Why not just bookmark the mobile web URL?
Because the mobile web view does not have push notifications, biometric lock, a privacy screen in the app switcher, or persistent native state between sessions. It works when you are already in a browser and need a quick check. It is not a repeatable workflow for on-call engineers who need sub-30-second access at 3am.
Will the Orion Web Console mobile view get better?
The mobile-responsive layout has been stable for many years. It is not the primary focus of SolarWinds' current product investment. It reflects the state of the web UI at the time the responsive design was implemented. What it does not do is use what phones can offer natively: push notifications, biometrics, privacy screens, and touch-first layouts. That gap is what PocketNOC fills.