Connect
Plug in what you already have.
87% of commercial facilities have no BMS. They have meters, circuit breakers, and maybe a few sensors. That is enough. Connect what exists. Add sensors where needed. Intelligence starts immediately.
What connects
Six categories. Any hardware. One pipeline.
No rip and replace. Wattif connects to whatever is already installed. If nothing is installed, we add sensors at cost and commission them through a Project.
Power sensors
CT-clamp current transformers, split-core sensors, energy monitors. Clip onto any circuit. No rewiring. Measure kW, kWh, voltage, current, power factor.
Environment
Temperature, humidity, air quality, light level, occupancy. The context layer that explains why energy is being consumed.
BMS feeds
Building management systems over BACnet, Modbus, or vendor APIs. Pulls setpoints, schedules, alarm history, and zone telemetry.
Meters
Utility interval data, pulse counters, smart meter feeds. 15-minute or 30-minute resolution. Historical and real-time.
IoT gateways
LoRaWAN network servers, MQTT brokers, webhook endpoints. Aggregate hundreds of sensors through a single integration point.
External data
Existing platforms push data to Wattif via authenticated webhooks. Self-serve token generation. JSON payloads. Real-time or batch.
How it works
Raw signal to actionable intelligence in five steps.
Every data source follows the same pipeline. No custom integrations. No ETL scripts. Connect the device, intelligence begins.
Raw IoT
Sensors, meters, BMS, webhooks push data in any format. MQTT, HTTP, LoRaWAN uplinks.
device_channels
Every data stream is registered as a channel. Device type, measurement, unit, resolution. Automatic discovery.
Normalize
Device adapters transform raw payloads into a standard schema. Unit conversion, timestamp alignment, gap detection.
Facility database
Clean telemetry lands in the facility time-series database. Load, generation, storage, context. Ready for agents.
Agents
Seven AI agents read from normalized data. Baselines built. Anomalies detected. Findings reported. Dollars attributed.
Device adapter registry
New devices are configuration entries, not code changes.
Add your hardware. Deploy. Done. Discovery, normalization, and UI all read from the registry automatically.
How it works
One config object per device
Define manufacturer, protocol, channels, normalization logic, and UI display. That is the entire integration.
Automatic channel discovery
When a new device connects, the registry identifies its type and creates device_channels automatically. No manual mapping.
Instant normalization
Raw payloads are transformed using adapter-specific SQL builders and row transformers. Clean data in the facility database within one cron cycle.
Registered adapters
Harvy2
Dezem · 4-ch CT clamp
Shelly Pro EM
Shelly · Power, energy, voltage
AM307
Milesight · Temp, humidity, CO2, light, PIR
EM300
Milesight · Temperature, humidity
Adding your hardware? One configuration object. No firmware changes. No custom middleware. Define channels, deploy, data flows.
Data integration
Push your data. Pull our intelligence.
Already have a BMS or monitoring platform? Push telemetry to Wattif via authenticated webhooks. Self-serve setup. Secure API keys. Real-time or batch.
Webhook endpoints
Register at /connect with a self-serve token. Push JSON payloads with device ID, timestamp, and measurements. We handle the rest.
wif_wh_* token formatAPI key authentication
SHA-256 hashed keys scoped by permission level: read, write, control. Facility-restricted. Revocable at any time.
wif_pk_* key formatEncrypted and audited
AES-256-GCM encryption for all tokens. Full audit trail. RLS enforcement. Your data stays isolated to your facilities.
SOC 2 alignedBring your hardware. We bring the intelligence.
Connect any device, any protocol, any platform. Intelligence starts on the first data point.
Get started