The problem: connecting physical devices to software people can use
A sensor on a boat or in a field produces raw data. On its own, that's useless to the person who needs to act on it. Life9sys needed software that takes messages from many devices over whatever connection they have, turns them into readable information, and lets users react, including sending commands back to the device.
They also sell three different products (Marine Intelligence, Farm Connect, and Water Metering System), and technical products are hard to explain on static pages.
How the IoT platform moves data from device to dashboard
Devices never talk to the dashboard directly. They send data through a communication layer to the backend, which processes it and exposes it through APIs. That separation keeps the system organised and makes it safe to add new device types or new screens later.
Sensors, trackers, and controllers
Collect readings in the field or receive commands.
Wi-Fi or 4G
Whichever connection is available where the device sits.
MQTT or HTTPS
MQTT for lightweight, frequent device messages; HTTPS for standard requests.
Backend and APIs
Receive, process, and store device data, and expose it safely.
Live dashboard
Current readings, alerts, and controls that send commands back.
Realtime dashboards, alerts, and remote device control
The dashboard shows current readings from every connected device in one place. When something needs attention, the system raises an alert instead of waiting for someone to notice. Alerts reach the dashboard in about 300ms, across 20+ devices sending 1,000+ readings a day. Users can also send control actions back to devices, so the dashboard is a control panel, not just a report.
A company website that explains technical IoT products
I built the site from Figma, giving each product its own showcase so visitors can understand Marine Intelligence, Farm Connect, and Water Metering separately. Custom dropdown menus on desktop and a sidebar on mobile keep the three product lines easy to find.
Animations, cursor effects, and carousels add depth where they help explain the products, without hiding the content behind them.
The Life9sys website
Results
Key decisions
MQTT alongside HTTPS
MQTT is built for small, frequent device messages on unreliable connections. HTTPS covers standard requests. Supporting both fits more devices and networks.
Keep devices away from the dashboard
A backend and API layer between devices and screens controls what data gets through and makes the system easier to extend.
One responsive site instead of separate mobile and desktop versions
One codebase to maintain, and every page works on any screen.
Related reading