Watch the devices on your property and act on what they report.
A device monitoring system that works with all of your operational data inside Calisto Pro. Register sensors, trackers, locks, cameras, meters and gateways in one place. Work every alert they raise from one inbox, with your automations acting on it.
The Monitoring App for Devices
Sensors, trackers, locks, cameras, meters, and gateways in one registry, with an inbox and rules that act on both. Every device you run, on one screen.
Alert Path
Inbox. Acknowledged. Incident. Resolved.
Alerts
The inbox, the history, and the log.
Incidents
What the devices caught. Investigated and closed.
Device Fleet
Every connected device. Registered, monitored, managed.
Monitoring
Monitor it yourself. Or let Calisto watch for you.
GPS Tracking
Every tracked asset. One map.
Pace of Play
See who is behind before the day runs late.
Temperature, leak, energy, occupancy. One fleet.
Device health, battery and last-seen across every sensor class you run. A probe that stopped reporting two days ago is a row, not a discovery.
0
device types in one registry
0
stages on the alert path
0
alert states in history
0s
fleet map refresh
One
alert inbox across everything
Zero
standalone dashboards to check
Inbox. Acknowledged. Incident. Resolved.
Whatever raised it and whoever owns it, every alert your devices send moves along one path.
Signal classifies the event and emits it. What happens next is a rule you build in Automations, from the Create Rule action on the event catalog.
The inbox, the history, and the log.
One live queue with severity, device and time on every row. Dismiss an alert and it leaves the queue but stays in history, so clearing an inbox never destroys a record.
Pending alerts only. Filter to new, or search by alert, description or device.
Every alert including resolved ones, across five states. Read-only.
The same stream as log lines: time, level, source, message.
What the devices caught. Investigated and closed.
Every incident with its number, severity, status, property and elapsed time, filtered across five states or searched by name, number or property. Opening a row is where the work happens.
A Signal incident is something a device caught: a temperature excursion, a gas reading, an equipment fault, a power loss. Safety incidents reported by a person live in Assure and access incidents in Access. The three cross-reference each other and never merge.
A short form for what no device caught: property, incident type, severity, description. The property is validated before the record is written.
Escalate from the list or from the record, with a written reason. Escalated incidents are counted separately on the header.
Notes, handler and a read-only timeline beside status, severity and property. Resolve with notes, or add one. Severity is fixed at report time.
The alerts are triaged. The incidents are tracked. Now the devices behind them.
Every connected device. Registered, monitored, health tracked.
Type, location, status, battery, firmware and last seen on every device, over a readings chart with its threshold lines.
Every connected device. Registered, monitored, managed.
Centralize your connected inventory across locks, readers, sensors, and equipment.
Locks and Readers
Health only here: online state, firmware, battery. Credentials and remote unlock are managed in Calisto Access, and the row links straight there.
Type, status, location, battery, firmware and last seen on every device, counted online, offline and low battery.
One sectioned form rather than a step-gated wizard, and a CSV import that registers a batch in one paste.
A readings chart carrying its threshold lines over the raw points, with a connection test and an export beside it.
Every event Signal emits, each row carrying a Create Rule action that opens Automations.
Every list narrows to the unit you have selected, and reads in that unit’s own terminology.
Monitor it yourself. Or let Calisto watch for you.
Work the alert inbox with your own team, or pay Calisto's to work it around the clock. Both choices run on the same services and monitors, against the same property.
Self-Monitoring
Your team works the alert inbox. Each service names its escalation preference ahead of time, and monitors pause and resume around planned work.
24/7 Monitoring by Calisto
Calisto's operations team works the same inbox around the clock, follows the runbook recorded against each incident type, and escalates by the preference set on the service. Charged as a monthly fee.
Services
Every monitored service on a property with its type, status, monthly fee, auto-renew setting and last check.
Monitors
Named monitors with a health state and a last check. Pause one for planned work and resume it from the same control.
Every tracked asset. One map.
The map plots every device reporting a position, with the same devices listed beneath it and one click between the two views. Devices are registered once, so nothing is enrolled twice.
Fleet Map Refreshes 15s
Every reporting device as a marker with its name and status, without a page reload.
Geofences Circle or polygon
Zones drawn as a circle or a polygon over the same map. Create, edit and delete them.
Fleet List Read-only
Status, coordinates, speed, battery and last seen, counted moving, parked, offline and low battery.
See who is behind before the day runs late.
Every active unit against its target cycle time, colour-coded on pace, behind or critical, with the alerts and the history on the same screen. The thresholds that fire an alert are authored in Automations.
A unit that stops reporting is marked position unknown, never drawn at the last coordinates it sent.
Where Signal touches everything else.
5 of these 6 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.
Automations
Signal emits classified device events and the event catalog Create Rule action opens Automations, where the rules that act on them are built.
Access
Locks, card readers and panels open in Access, which owns credentials, schedules and remote lock and unlock for the same hardware Signal health monitors.
Assure
Human reported safety incidents are recorded in Assure; Signal incidents are device detected anomalies that cross reference them and never merge.
Today
The Today alerts screen reads the Signal alert feed and the Today cockpit carries a Signal device tile.
Purview
The active business unit selected in Purview scopes every Signal list and supplies the terminology its labels use.
Inbox
Signal posts inbound alert messages to Inbox through its ingest endpoint.
No setup cost. Pay when you start using.
Device monitoring for connected sites.
Recommended for you
Works well together.
Calisto Automations
Calisto Access
Calisto Assure
Calisto Ops
Daily dashboard, helpdesk, dispatch, accounting, compliance, and HR
Learn more →Calisto Today
Calisto Purview
Included with every Calisto account
Account configuration and data rules.
Learn more →Calisto Inbox
Everything included in Calisto Signal.
- Live alert inbox: up to 100 pending alerts, refreshed every 30 seconds
- Four severity bands: critical, high, warning, info
- Acknowledge, dismiss, or request suggested classification per alert
- Suggested classification reads the alert title, description, and device
- Dismissed alerts stay in history (clearing the inbox never destroys a record)
- Inbox counts: pending, critical, new, and linked to an incident
- Inbox filter to new only; search across alert, description, and device
- Alert history: read-only record with five-state filter and search
- Device logs: time, level, source, and message with level filter
- Configurable thresholds: offline, low battery, weak signal, heartbeat interval
- Device-detected anomalies with number, severity, status, property, and timing
- Five status states: open, acknowledged, escalated, resolved, dismissed
- Resolve with notes, annotate, or escalate with written reason
- Incident record: notes, handler, and a read-only timeline summary
- Severity is fixed at report time and is not rewritten on the record
- Manual incident reporting with property validation
- Auto-open incidents from alerts (configurable)
- Severity counts: total, open, critical, resolved, escalated
- Refreshed every 30 seconds
- Scope: device anomalies only (human-reported goes to Assure, access to Access)
- Every device with type, status, location, manufacturer, battery, firmware, provisioning, last seen
- Six device categories: locks/readers, cameras, climate, water/safety, sensors, fitness
- Locks and readers health-tracked here; credentials and remote unlock owned by Access
- Cameras carry their own event stream into the alert inbox
- Single sectioned registration form: type, vendor, connection method, hardware address, reporting interval, thresholds
- CSV import for batch registration
- A sensor with stale data is flagged offline rather than showing an old reading as current
- Device record with readings chart, threshold lines, and raw data points
- Connection test, configure, and export readings per device
- Cellular: eSIM profile with data used, allowance, and remaining
- Sensor feed across occupancy, temperature, humidity, water, energy, air quality, door contact
- Per-sensor warning and critical thresholds, editable in place
- Every event type Signal emits with trigger, category, severity, payload shape, and recent count
- Log of the last 100 emissions per event type
- Create Rule action on each row opens Automations
- Signal emits events, never decides the response
- Self-monitoring (included): your team works the alert inbox
- 24/7 monitoring by Calisto (optional add-on): trained operations team, monthly fee per service
- Monitored services per property with type, status, monthly fee, auto-renew, escalation preference
- Named monitors with health state, pause, and resume
- Escalation preference, preferred language, emergency phone, and special instructions per service
- Live map: every position-reporting device plotted, refreshed every 15 seconds
- Fleet list: status, coordinates, speed, battery, last seen
- Counts: total, moving, parked, offline, low battery
- Geofences: circles or polygons drawn on the map, counted by shape
- Fleet list search by name or status
- Devices registered once on the device screen (no double enrollment)
- Live unit with location, party size, current stage, expected stage, and deviation
- Colour-coded status: on pace, behind, critical
- A unit with a stale position is marked position unknown, never drawn at its last coordinates
- Pace alerts: raise, acknowledge, resolve, or dismiss
- Pace alert counts: total, active, acknowledged, critical
- Pace history with record count, average and worst deviation, and slow records
- Alert thresholds authored in Automations
- Reports is a live analytics viewer: four tabs held in the URL, nothing to queue and nothing to download
- Report tabs: incidents, device uptime, sensor trends, fleet utilization
- Incidents report: total, open, resolved, escalated over a severity breakdown and a per-property table
- Device uptime report: total, online, offline, and percentage online per device
- Approvals queue: devices and services in pending setup with category, subject, property, raised date, and state
- Approve or reject with a comment; approving activates the service, rejecting cancels it, and a decided row cannot be decided again
- Knowledge base articles: title, summary, category, status, view count, last update
- Playbooks: per incident type with default severity, instructions, emergency contacts, special instructions, escalation preference
- No trigger, condition, or action builder in playbooks — rules belong to Automations
- Settings: business identity, contact and hours, and the venues and spaces being monitored
- Settings: default escalation and language, auto-open incidents, notify on critical or on every alert, alert webhook, auto-provisioning, default heartbeat interval
- Settings: offline, low battery, and weak signal thresholds; monitoring dashboard window and refresh rate
- Optional classification step labels incoming events by type and severity
- All lists scoped to the active business unit, in that unit’s own terminology
- Automations (event catalog with Create Rule action)
- Access (locks and readers health-tracked here, policy owned there)
- Assure (device anomalies here, human-reported safety incidents there)
- Today (alert feed and device tile in the daily cockpit)
- WiFi (access point fleet read from Signal)
- Purview (business unit scope and terminology)
- Inbox (alert messages posted via ingest endpoint)
- Dispatch (maintenance task assignment)
Questions about Calisto Signal
Sensors, trackers, locks, cameras, meters, controllers and gateways. Treating them as one class is the point: the alert from a freezer and the alert from a door arrive in the same inbox with the same handling.
Battery and firmware are tracked per device, which is what catches the sensor that stopped reporting rather than the one that reported a problem. The silent device is the dangerous one.
It is worked from an inbox and can raise a task in Dispatch or a finding in Assure, so an alert ends in a fix with an owner instead of a notification somebody dismissed.
Yes. Devices are registered against your account rather than bought from us, which is why Signal is a layer over the hardware you already own.
The pricing section on this page reads the live catalogue and is the authority. Signal works without the rest of Calisto Ops.
Yes, including readings, alerts and how each one was resolved, in standard formats.