Connect & commission
Bring devices into an operational system through defined discovery, pairing, registration, and commissioning workflows.
Callysta IoT platform
Connected devices. Actionable insight.Control from the field to the dashboard.
Bring device connectivity, fleet management, data warehousing, analytics, and monitoring into one coordinated solution. Give operations teams the context to investigate events, manage updates, and respond through dashboard and mobile workflows tailored to each deployment.
From physical to digital
Devices · Sensors · Embedded systems
Callysta IoT platformConnectivity · Commissioning · Device managementData warehouse · Analytics · MonitoringEvents · Alerting · Integration · Validation
Operational insight & actionDashboards · Reports · Response workflows · Automation
A shared foundation for further domain-specific solutions.
01 / Shared foundation
More than a device.
A connected workflow.
Connect assets, manage the fleet, retain and analyse its data, and turn operational events into action. Integration and validation run across the entire lifecycle.
Manage & maintain
Manage device identity, configuration, health, and firmware throughout the fleet lifecycle—with controlled updates and recovery paths.
Data warehousing
Bring telemetry, events, and device history into a structured data foundation. Define retention, historical access, and business-system integration around each deployment’s needs.
Analytics & reporting
Turn measurements into context through historical trends, comparisons, operational indicators, and reports—helping teams understand performance and make informed decisions.
Monitoring, events & alerting
Bring fleet status and operational events into view. Define alert rules, priorities, notification channels, and escalation workflows around the people responsible for responding.
Integrate & validate
Connect embedded devices, mobile interfaces, enterprise systems, and operational applications. Validate complete workflows through application checks, real devices, and hardware-in-the-loop evidence.
Data models, analytics, retention policies, alert rules, and delivery channels are configured and qualified for each solution.
02 / Platform operations
Connect. Understand.
Stay in control.
From fleet connectivity and reliable updates to operational dashboards, mobile awareness, and the architecture for continuous operation at scale.
Monitoring dashboard · Analytics · Mobile
See the whole system. Act from wherever you are.
Bring fleet health, operational measurements, historical insight, and actionable events into a unified monitoring experience—connecting the control room with teams in the field.
- One operational view
- Bring device status, sensor measurements, trends, and event history into focused views. Historical data and analytics help teams understand current conditions and identify devices that need attention.
- Live events, meaningful notifications
- Use priorities, filters, and deployment-specific alert rules to identify conditions that need a response. Events arrive in near real time when connectivity is available; notification channels and escalation workflows require integration and qualification.
- Connected mobile workflows
- Give field teams relevant status, alerts, and device context alongside commissioning and maintenance tasks. Mobile interfaces and response workflows are scoped per solution, rather than assumed to be identical across deployments.
Scalability · Reliability · Continuous operation
Plan for growth. Stay in control.
Design for larger fleets without losing operational visibility. Million-device scale and 24/7 continuous operation are architecture objectives, with capacity and availability validated for each deployment.
- A path to millions of devices
- Distributed device management and independently scalable ingestion, processing, and storage provide a path to growth. Sizing accounts for connections, message rates, payloads, retention, and update traffic. Million-device capacity remains a design target, not a published benchmark of the current implementation.
- Designed around 24/7 operation
- Plan health monitoring, fault isolation, redundancy, maintenance, and recovery together. Availability targets and support arrangements are agreed per deployment; continuous operation does not mean zero downtime.
- Reliability from the edge to the platform
- The implemented device foundation already includes bounded reconnection, acknowledged delivery for selected durable events, and verification-gated firmware updates. We build on these behaviours with deployment-specific capacity, endurance, failover, and recovery validation before expanding the fleet.
4G · CAN bus · BLE · Sensors
From field signals to useful data.
One gateway brings together a wired CAN sensor network, supported BLE peripherals, and a managed 4G uplink.
- Stay connected in the field
- Managed 4G monitors modem sessions and uses bounded reconnection with recovery escalation. MQTT reconnects independently, and selected durable events are retried after connectivity returns; this is not unlimited buffering of all telemetry.
- Commission and recover CAN nodes
- Discover and associate multiple wired sensor nodes with acknowledged identities and stored configuration. Bus-off recovery and rediscovery after restart or update help restore operation. Devices use supported, declared drivers and configurations.
- BLE sensing & actuation
- Supported BLE peripherals connect wirelessly to the gateway, separately from the wired CAN network. Demonstrated workflows include secure discovery and pairing, PIR motion and battery sensing, and BLE alarm actuation. Peripheral support is integrated and qualified per device—not arbitrary Bluetooth compatibility.
- Configurable wired & onboard sensors
- Each CAN sensor node supports eight configurable GPIO inputs and a shared protected I²C bus. Qualified workflows include I²C discovery and access, temperature sensing, and the gateway’s onboard motion and power monitoring. Validated configuration mappings require acknowledgement and revert safely on invalid responses or timeout.
Reliable OTA engineering
An update needs a recovery path.
Over-the-air updates must account for the realities of remote devices: interrupted connections, power loss, and different hardware revisions.
- Verify the release
- Signed manifests and checks for package hash, size, hardware, version, and anti-rollback policy gate staged activation. Firmware is accepted against the intended device—not just because a download completed.
- Gateway rollback
- The gateway updates an inactive firmware slot, then checks health during a probation period. If the new image fails those checks, it rolls back automatically. Recovery and interrupted-transfer scenarios have hardware-in-the-loop evidence.
- Sensor-node recovery
- Sensor-node updates use acknowledged CAN transfer, CRC verification, a protected bootloader, reset, rediscovery, and version confirmation. These nodes support bootloader recovery, not a second application image with automatic rollback.
Near-real-time events & notifications
Know the platform received the event.
Keep important device events identifiable and available for retry until the backend acknowledges receipt. This supports operational awareness even when a connection is interrupted.
- Prioritized, identifiable events
- Stable event identities and prioritized publication help the platform distinguish meaningful events and handle duplicates safely. Selected durable events remain available for retry across reconnects.
- Backend acknowledgement
- An application-level backend acknowledgement is required before an event is removed from its durable queue. MQTT broker QoS alone is not treated as confirmation that the application received it.
- Notification channels
- Device-to-platform delivery is demonstrated. End-user push, SMS, email, escalation, and human acknowledgement need separate integration and qualification. Delivery timing depends on connectivity; no fixed latency or zero-data-loss guarantee is implied.
Demonstrated foundations include device commissioning, managed CAN/BLE connectivity, acknowledged event delivery, and guarded firmware updates. Data services, dashboards, analytics, and response channels are engineered and qualified to each solution’s scope.
03 / Platform in practice
Commission with confidence.
Verify beyond the screen.
A connected device is only useful when its identity, configuration, and operational state can be trusted.
Our commissioning workflow brings together embedded devices, mobile interfaces, secure BLE pairing, backend registration, and assigned-device inventory. Supported configurations are validated and acknowledged before they become part of the operational system.
Validation connects the application to physical hardware: controlled device inputs, state checks, and evidence from both the device and software layers.
Demonstrated engineering workflows
- Device discovery, pairing, and commissioning
- Backend registration and assigned-device inventory
- Real-device and hardware-in-the-loop validation
Communications portfolio
The right connection.
For every environment.
Our communications engineering portfolio spans metering, building automation, industrial systems, and connected products.
4G · NB-IoT · LoRa
Connectivity engineering for distributed devices, remote monitoring, and metering applications.
BLE · 6LoWPAN · Zigbee · Wi-SUN
Wireless sensing, commissioning, and network integration for smart buildings and field systems.
CAN bus · Modbus · HPLC · G3-PLC
Device and system integration across industrial buses and power-line communication networks.
Wi-SUN FAN 1.1 engineering experience
Wi-SUN FAN 1.1. A core engineering strength.
Our Wi-SUN FAN 1.1 experience connects embedded hardware, firmware, metering, and backend engineering. We help customers bring these disciplines together for smart-metering and connected-field solutions, from product design through integration and validation.
This is our broader engineering portfolio—not a claim that every protocol is enabled on every platform device. Hardware, protocol stacks, interoperability, and deployment requirements are selected and qualified for each project.
04 / Where we are heading
Built to extend.
Grounded in the use case.
Our direction is a reusable platform with domain-specific devices, integrations, and applications—not a one-size-fits-all product.
Connect measurements to operations.
Explore device commissioning, metering data integration, and utility workflows.
Connect spaces to their systems.
Explore sensing, equipment monitoring, and integration with building operations.
Connect purpose-built devices.
Bring custom electronics, firmware, and software into a coherent product ecosystem.
These are development directions. Interfaces, supported devices, operational requirements, and delivery scope are defined and validated for each implementation.
Start with your use case
Turn field data
into your next decision.
Tell us which assets you need to monitor, what your team needs to know, and how it should respond. We’ll define the devices, data services, integrations, and validation your solution needs.
Discuss your IoT project