Application Capabilities Overview
What Are Application Capabilities?
Application Capabilities are ready-made domain logic modules built on top of the Core Platform. Each Capability provides a complete set of models, logic, workflows and integration points for a specific functional domain — ready to be used by applications, automation rules and external integrations.
A Capability is not a standalone product and not simply an API. It is a module that operates on top of the Core Platform, using its device model, event stream and control mechanisms to deliver domain-specific behaviour that multiple applications or customers can share.
For example, the Security and Alarm Capability does not just expose lock and sensor endpoints. It includes partition and zone models, alarm state logic, arming and disarming workflows, notification routing and integration with detection devices — packaged as a reusable module.
Where Capabilities Fit
Capabilities occupy the layer between the Core Platform and Applications:
┌────────────────────────────────────────────┐
│ Applications │
│ (mobile app, web admin, AI copilot…) │
├────────────────────────────────────────────┤
│ Application Capabilities │
│ (security, HVAC, video, access…) │
├────────────────────────────────────────────┤
│ Core Platform │
│ (devices, protocols, runtimes, data…) │
└────────────────────────────────────────────┘
The Core Platform handles device connectivity, normalization and infrastructure. Capabilities consume these services and add domain-specific logic. Applications then consume Capabilities to deliver complete user experiences.
This separation means:
- the same Capability can be used by multiple applications (mobile app, web admin, AI agent);
- domain logic is implemented once and tested independently of any specific UI;
- adding a new application does not require reimplementing alarm logic, HVAC schedules or video management from scratch.
Current Capabilities
Security and Alarm
The Security and Alarm Capability provides a complete model for physical security management. It introduces the concepts of partitions and zones built on top of the normalized device model, and implements alarm state logic including detection, arming, disarming, alarm triggering and notification workflows.
It covers:
- partition and zone definitions;
- alarm state transitions and trigger logic;
- integration with motion detectors, door/window sensors, sirens and keypads;
- notification routing on alarm events.
Thermostat and Environmental Control
The Thermostat and Environmental Control Capability provides models and logic for managing HVAC and climate control across a space or facility. It abstracts over individual thermostat devices and provides zone-based temperature management, scheduling and HVAC configuration.
It covers:
- climate zones and setpoint management;
- operating modes (heating, cooling, fan, auto);
- scheduling and time-based profiles;
- HVAC equipment configurations.
Explore Thermostat and Environmental Control
Video Management
The Video Management Capability provides integration with camera devices and recording infrastructure. It abstracts over camera hardware and provides a consistent interface for live view, recording, event-triggered capture and retrieval.
How Capabilities Are Used
Capabilities can be consumed in several ways:
- Applications — the mobile app, web admin interface and vertical applications use Capabilities as the domain logic layer, rather than building their own alarm or HVAC logic.
- Automation Rules — the rule engine can read Capability state and trigger Capability actions, for example arming a security partition when a scheduled event fires.
- Integrations — external systems and AI agents can interact with Capabilities through the REST API and MCP servers, receiving structured domain state rather than raw device data.
Relationship to the Device and Resource Model
Capabilities build on the normalized resource and capability model of the Core Platform. A partition in the Security Capability is backed by normalized sensor resources. A climate zone in the Thermostat Capability is backed by normalized thermostat resources. This means Capabilities work across device brands and protocols without modification.
Learn more about Device Normalization
Where to Continue
| Goal | Recommended Page |
|---|---|
| Understand physical security and alarm management | Security and Alarm |
| Learn about HVAC and climate zone control | Thermostat and Environmental Control |
| Explore camera integration and recording | Video Management |
| Understand how Capabilities sit on the Core Platform | Core Platform Overview |
| See how applications consume Capabilities | Applications Overview |
| Integrate Capabilities via API or AI agents | Integrations Overview |