Technology
How the platform is built.
An intelligence layer over the infrastructure you already run — edge and cloud processing, integration rather than replacement, and the security controls that come with handling operational data.
Architecture
Six layers, one platform
Every XiGiFy use case runs through the same stack, top to bottom. What changes between a leak-detection deployment and a ventilation one is the instrumentation and the rules at each layer — not the architecture underneath.
- 01
Sensing & edge
Sensors, meters and gateways collect telemetry at the asset. Processing at the edge means time-critical detection does not have to wait on a round trip to the cloud, and a site keeps working through a connectivity interruption.
- 02
Integration
The platform connects alongside the SCADA, BMS and metering infrastructure a site already runs, reading from those systems rather than replacing them. Existing infrastructure investment is preserved.
- 03
Data & normalization
Telemetry from different makes, models and vendors is normalized into a common structure, so data from separate systems can be compared and analysed together instead of living in separate dashboards.
- 04
Analytics & AI
Pattern-recognition analytics trained on each site's own historical data learn what normal looks like, then flag developing fault signatures rather than only firing once a fixed threshold is crossed.
- 05
Automation
Low-code rules turn a detected event into an outcome: an alert to the right person, a logged incident, or a triggered workflow — configurable without a development cycle for every change.
- 06
Presentation & reporting
Dashboards give a live view from a whole portfolio down to a single sensor, and the same data is structured for internal reporting, audits and ESG disclosure.
Engineering
Built on four core layers
Every XiGiFy deployment, across every industry it runs in, is built from the same four categories — the split the platform team itself designs and builds against.
Device & hardware integration
A device-agnostic connectivity layer over MQTT, with secure device identity and bidirectional communication. It integrates with common gateways and hubs — including Home Assistant and Raspberry Pi-based gateways — and OEM device APIs such as Tuya, eWeLink and KNX, so a site's existing device ecosystem connects rather than getting replaced.
Data platform
A unified foundation ingests, stores and processes telemetry in real time and in batch, deployable on-premises, in a private cloud, or in a public cloud. Built on a modular, open-source stack rather than one proprietary vendor's pipeline, so a deployment isn't locked to a single provider.
IoT core services
The foundational services every deployment runs on: device provisioning and lifecycle management, monitoring, control, a rule engine, scheduler and automation, multi-tenant role-based access, and subscription and billing.
Business & industry-specific development
Domain solutions — leak detection, ventilation control, energy management, smart home and smart building automation — are configured applications on top of the same core platform, not separate systems built from scratch each time.
Security
Protecting operational data
Monitoring infrastructure means handling data that matters — access records, site telemetry, incident history. These controls are built into the platform and already in production use.
End-to-end encryption
Data in transit and at rest is encrypted, protecting telemetry and account data across the platform.
Role-based access control
Control who can view, acknowledge and resolve alerts and data, scoped across sites, teams and roles.
Audit logging
Every alert and the response to it is logged, giving a defensible record for review, insurance and compliance.
Managed device lifecycle
Devices are provisioned, monitored, updated — including firmware and OTA updates — and eventually decommissioned under the same managed process, not left unmanaged once installed.
We list what is built and shipping rather than what sounds reassuring. For the status of a specific certification, or to run a security questionnaire, contact the team and you will get documentation rather than a claim.
Multi-tenancy
Access control that scales with your portfolio
The same tenant structure underpins every deployment, so growing from one site to a full portfolio is a matter of adding to it — not redesigning it.
Isolated by tenant
Each organization's data, users and configuration are kept isolated from every other tenant on the platform — a structural boundary, not just a permissions setting.
Scoped by role, site and team
Access is controlled by role-based permissions that can be scoped down to a specific site, team or asset group — a regional facilities lead does not need, and does not get, portfolio-wide access by default.
One structure, any size portfolio
The same tenant and access model applies whether you are running a single building or a multi-site, multi-region estate — adding sites extends the existing structure instead of requiring a new one.
Hosting
Deploy where your infrastructure already lives
The platform runs cloud-hosted, on-premise, or as a hybrid — edge processing at the site, central analytics in the cloud. Data residency and connectivity requirements are handled per deployment.
Cloud-hosted
Managed deployment on cloud infrastructure — device data flows to the cloud for processing, analytics and dashboarding. Suitable for sites with reliable connectivity and no local-processing requirement.
Hybrid (edge + cloud)
Time-critical detection and local control happen at the edge; longer-horizon analytics, cross-site comparison and reporting run centrally. Keeps working through a connectivity interruption.
On-premise
Full deployment within your own network and data centre — for environments with data-residency requirements, semi-isolated networks or corporate IT policy constraints.
Deployment
What rollout actually looks like
The deployment model follows from the architecture: add a layer over what exists, instrument the points that matter, and extend from there.
Works with what's there
Sits alongside the SCADA and BMS you already run
Added as an intelligence layer, not a replacement programme — existing infrastructure investment is preserved.
Sensors where they matter
Instrumented at the points that carry the risk or the cost
Risers, plant rooms, pump stations and critical equipment — not everywhere at once.
One site or a portfolio
The same architecture at any scale
Applies whether you are monitoring a single building or comparing performance across a multi-site estate.
Start narrow, extend
One problem first, the next one without starting over
Every use case runs on the same platform, so scaling up is configuration, not a new project.
FAQ
Technology questions
Have a technical or security question before you start?
Talk to the team directly — architecture, integration scope or a security questionnaire.