Industrial Gas Safety, Monitored in Real Time
Gastronics builds gas-sensing hardware for industrial and commercial sites, where a missed reading can mean a leak, a fire, or a life.
They needed a software platform that turned sensor data into live visibility and alarms across a complex chain of companies, distributors, and end clients. We built a multi-tenant web and mobile platform that monitors every gas and weather sensor in the field, plots them on interactive SCADA site maps, and fires threshold alarms the moment a reading crosses the line.
and their clients, all isolated
One system to onboard organizations, configure sensors, monitor gas flow and weather in real time, trigger and log alarms, and manage periodic calibration — with strict data isolation between tenants.
Complex multi-tenancy
Some customers buy sensors for their own use; others are distributors reselling to their own clients. One engineer may serve multiple clients, but two clients can never share locations, sensors, or SCADA views. Off-the-shelf tools don't model that.
Safety-critical alarms
Gas readings must trigger high, high-high, and fault alarms reliably, plus drill, fire, and communication-failure alerts. There is no acceptable margin for a dropped alarm.
Site context matters
A raw sensor value means little without knowing where the sensor sits. Teams needed sensors plotted on actual site blueprints, not listed in a table.
Compliance and calibration
Engineers perform periodic calibration with span gas and must generate downloadable reports. That workflow had to be built in, not bolted on.
Every project starts with one question:
buy, automate, build, or wait?
We find the software that already solves it, vet it against how you work, and get your team running on it. Live in days.
We connect the tools you already use so the manual steps disappear and data moves on its own.
We design and develop something custom from the ground up. Built for how your business runs, owned by you.
We tell you when holding is smarter. You leave with a clear reason and a date to revisit.
Why We Choose Build
- ✗ Buy failed: generic IoT dashboards don't model the company/distributor/client hierarchy, the role structure, or the SCADA-plus-calibration workflow this business depends on.
- ✗ Automate failed: this is the product Gastronics sells alongside its hardware. It had to be a real platform, not glue between tools.
- ✗ Wait failed: the sensors were already in the field. The software to make them useful had to exist.
Before we recommend anything, we score the project on three things: how unique the work is, what a mistake costs, and how much of it runs on human judgment.
Onboard the org. Configure the sensors. Watch the site.
Onboard
Tenant hierarchyA super-admin classifies each new customer as a company (buying for its own use) or a distributor (reselling to clients). Companies, distributors, and distributor clients each get isolated accounts and their own admins.
Provision
Role-based accessCompany and distributor admins create engineers and read-only viewers under their org. Engineers can span multiple clients; viewers are scoped to gas or fault alarms only. Access rights cascade cleanly through the hierarchy.
Configure
Sensors and gas typesAdmins register gas types (sensor gas vs. span gas, toxic vs. combustible, measured in % VOL, % LEL, or PPM) and configure gas and weather sensors per location with their alarm thresholds.
Map
SCADA site viewsAdmins upload a site blueprint, draw areas of interest, and drop sensor pointers onto the actual layout. SCADA shows every sensor's live status and reading in place, plus real-time weather: wind direction and speed, temperature, humidity, and pressure.
Monitor
Live data feed and graphsActive sensors stream readings into a live data feed and per-sensor detail graphs. Current and historical values sit side by side with their alarm state.
Alarm
Threshold and event alertsReadings crossing configured thresholds fire high and high-high alarms, logged newest-first with timestamp and value. Beyond reading alarms, the system raises drill, fire, and communication-failure alerts.
Calibrate
Compliance reportingEngineers perform periodic calibration using pre-registered span gas (brand, cylinder serial, batch, expiry) and generate timestamped calibration reports, downloadable and scoped to each engineer's locations.
Before vs. After
| Metric | Before | With the platform |
|---|---|---|
| Sensor visibility | Raw readings, no central view | Live data feed plus SCADA site maps across every location |
| Alarm handling | Manual, easily missed | Automatic threshold, drill, fire, and comm-failure alarms, all logged |
| Multi-org management | Not possible in one tool | Companies, distributors, and clients in one isolated hierarchy |
| Site context | Sensor lists | Sensors plotted on real site blueprints |
| Calibration records | Ad hoc | Built-in span-gas calibration with downloadable reports |
| Weather at site | Separate or absent | Five weather attributes live inside SCADA |
The platform gives Gastronics a software layer that sells and scales alongside its sensor hardware, turning raw device output into the live visibility and audit trail industrial safety teams require.
The Technical Build
A Laravel API and MySQL core, with responsive web and mobile clients scoped to every role.
A Laravel backend on MySQL models the full tenancy tree (companies, distributors, clients), sensors, SCADA layouts, alarms, gas types, and calibration records with enforced tenant isolation.
A responsive web application for super-admins, org admins, engineers, and viewers, each surface scoped to that role's permissions.
Engineers and viewers access live readings and alarms from mobile devices, so monitoring isn't tied to a desk.
A wizard lets admins upload site blueprints, draw and label areas, and place gas and weather sensor pointers that show live status and readings in place.
Configurable low/high/high-high thresholds per sensor drive real-time alarm triggering and logging, alongside event alarms for drill, fire, and communication failure.
A layered permission model ensures engineers can serve multiple clients while two clients never share locations, sensors, or SCADA — the core data-isolation guarantee of the platform.
Turning hardware into a business that needs software to scale?