A meter that measures, a tracker that follows a vehicle, a sensor in a warehouse: the device is half the job. The other half is the program running inside it, the app you control it from and the servers where the data ends up. We do both halves, so you have just one number to call when something goes wrong.
Everything your device needs around it, piece by piece.
We configure the program running inside the device ourselves, and make its parameters editable directly from the app.
You set the thresholds and the system alerts you on its own when something goes out of range, or carries out the action you've chosen.
From your phone or computer you can see the data, change settings and control the device remotely.
No need to throw away the hardware you use: we connect to it and build the app, the control panel and the data archive around it.
We handle the entire connection: the program inside the device, the app and the servers that collect the data. We design or integrate the hardware, depending on the project, so you don't have to coordinate different vendors.
Firmware, app and server: just one number.
A device mounted on a vehicle or at a job site doesn't get the office's good connection. We choose the type of connection based on where it will be and make sure data isn't lost when the network drops.
Data stays on the device and syncs as soon as the connection is back.
We choose the connection type and how often data is sent based on how much battery the device has.
Where the hardware allows it, the internal program updates over the network, without anyone having to go get the device.
For LitBox, the device that measures household energy consumption, we built the app, the web dashboard and the CRM. Real-time consumption becomes readable numbers, to see where energy is wasted and how much is saved.
LitBox
Device
Connectivity
Data and apps
Yes, that's the most common case: we connect to the device you already use and build the app and control panel around it.
We connect through the device's APIs or the most common standard protocols (MQTT, HTTP, BLE). If the manufacturer doesn't document them, we check before we start, so there are no surprises halfway through the project.
Yes. We configure the internal program's parameters and make them editable from the app or control panel, without needing to call a technician.
No. Data is stored on the device and syncs as soon as it's back online, via Wi-Fi or 4G.
Both: in some projects we built the device, in others we connected to existing hardware. We decide together based on what's needed and the budget.
Even one. You start with a prototype that actually works, test it in the field and scale up when the numbers add up.
Free first call: together we figure out whether and how we can help.
