No inbound monitoring exposure
The monitoring server initiates outbound HTTPS to its broker. The apps never connect directly to the monitoring interface.
LCW Labs monitoring companion
Server Alerts
Secure mobile alerts and monitoring operations for Nagios, Icinga, Checkmk, and Sensu, delivered through LCW Labs Cloud or a broker hosted in your own environment.
Operational access
Monitoring status and actions without exposing the monitoring interface.
Server Alerts keeps monitoring systems private while giving authorised users a focused mobile and portal experience.
Cloud or self-hosted
Use the managed LCW Labs service or operate a self-hosted broker and portal in your own environment. Internal CA trust must also be deployed to every client device when private certificates are used.
Respond from the app
Receive alerts, inspect state, acknowledge issues, schedule downtime, force checks, and control notifications where supported.
Deployment choice
Choose who operates the broker.
Both models keep inbound access away from the monitoring server. The difference is where the broker, portal, database, certificates, and operational responsibility live.
Compare deployment modelsDeployment detailLCW Labs CloudSelf-hosted broker and portal
Monitoring server exposureOutbound HTTPS onlyOutbound HTTPS only
Broker and portal accessManaged by LCW LabsManaged by your organisation
Monitoring dataManaged databaseMonitoring data stays local
Security by design
Clear boundaries between users, brokers, and monitoring systems.
Production connector traffic uses outbound HTTPS to the broker. Local HTTP is accepted only for localhost development.
Outbound HTTPS to broker
The connector's broker URL must use HTTPS in production.
Hashed connector tokens
Connector tokens are stored hashed and can be rotated when access needs replacing.
Audit trail
Membership, settings, licences, enrolments, token rotations, and supported actions are recorded.
Product enquiry
Discuss Server Alerts for your environment.
Tell LCW Labs about your platforms, site count, identity requirements, and preferred deployment model.