Operational intelligence in the browser
Access connected environments from any device — triage incidents, explore topology, and run AI-assisted investigations without installing an IDE. Add the Web Client to your Opsphere platform when your team needs shared dashboards and remote ops access.
THE ACCESS GAP
Not every operator works from an IDE
Cursor-native workflows excel for engineers at the keyboard — but engineering leads, on-call SREs away from their laptop, and partner teams often need the same operational context from a browser.
Forwarding dashboard screenshots, VPN hops, and read-only links fragments incident response. Everyone sees a different slice of the truth — and nothing stays in one auditable thread.
The result: duplicated triage, slower escalations, and teams locked out of the intelligence layer your platform already provides.
Ops context trapped in the IDE
When operational intelligence only lives inside Cursor, managers and on-call leads context-switch through five tools just to answer “what’s failing right now?”
No shared team surface
Incident threads scatter across Slack, email, and personal dashboards. Without a common browser workspace, correlation work restarts with every handoff.
Remote access without governance
Ad-hoc VPN and shared credentials don’t scale. Teams need scoped sessions, RBAC, and audit trails — not another root password in a chat message.
HOW THE WEB CLIENT WORKS
Same platform, browser-native delivery
The Web Client is an optional layer on your Opsphere license — same read-only connectors and topology graph, delivered through secure web sessions for the whole team.
Sign In & Connect
Authenticate with SSO or email, open a scoped session to your organisation’s connected environments. No local install, no MCP config — just a browser tab.
Triage In The Browser
Review live topology, correlated incidents, and integration health from any device. Role-based views show each user only the environments and tools their plan allows.
Collaborate & Hand Off
Share incident context, export summaries, and escalate to engineers in Cursor without losing the audit trail. Token quotas keep AI usage predictable per tier.
WEB CLIENT CAPABILITIES
Built for shared operational access
Institutional session control, team RBAC, and the same read-only connector fabric as the core platform — optimised for browser workflows.
Team Dashboards
Environment health, integration status, and topology snapshots sized for browser review — from on-call triage to executive briefings.
Session Isolation
Each login runs in an isolated execution context with scoped credentials, configurable timeouts, and a full audit log for every query and action.
Role-Based Access Control
Administrators define which environments, tool categories, and AI features each user can reach — aligned with Team and Enterprise plans.
AI Chat In The Browser
Ask operational questions, draft runbooks, and correlate signals with the same intelligence engine as Cursor — governed by per-plan token quotas.
Multi-Environment Switching
Move between dev, staging, and production views in one session without juggling VPN profiles or duplicate logins.
Web Client Specifications
- Session bootstrap time
- <3s
- Live data delivery
- Real-time
- Concurrent sessions
- Plan-based
- Authentication
- SSO · Email
- Client platforms
- Modern browsers
- Team seats (Team plan)
- Up to 20
- Session audit log
- 90 days
- Security certification
- SOC2
- SLA
- 99.99%
TYPICAL WORKFLOW
From alert to shared context in seconds
Browser Incident Flow
What an on-call lead sees when triaging production — without opening an IDE.
PagerDuty Page While Away From Desk
On-call opens Opsphere Web Client on a phone browser; SSO session scopes to production environments only.
Correlated View Loads In Browser
Topology, failing service, and last deploy appear in one dashboard — same graph the platform team sees in Cursor.
AI Summary Shared With Team Channel
One-click export posts blast radius and suggested next steps to Slack; audit log records who viewed what.
Handoff To Engineer In Cursor
Platform engineer picks up the same incident ID in Cursor with full context — no duplicate triage.
GET STARTED
Add browser access to your operational layer.
Start with the core platform, then enable the Web Client add-on for shared dashboards and remote triage — or bundle both on the Team plan.