Case Study · IoT Intelligence

Building a Scalable IoT Intelligence Platform for Cold-Chain & Industrial Environments

NerasTech — turning distributed IoT device data into real-time visibility, alerts and operational intelligence with MQTT, real-time processing, time-series storage, multi-tenant dashboards and mobile access.

NerasTech IoT Monitoring Platform MQTT · Multi-Tenant
NerasTech multi-tenant IoT monitoring platform

From Sensor Data to Operational Intelligence

IoT deployments generate enormous volumes of data. The real challenge is turning that data into something operations teams can actually monitor, understand and act upon.

For NerasTech, Mountain Lamp Technologies developed a scalable IoT monitoring platform designed to collect, process, visualize and analyse data generated by IoT devices deployed across cold-chain and industrial environments.

The platform brings together device connectivity, real-time data processing, time-series storage, analytics, alerting, dashboards and mobile access into a unified ecosystem.

IoT Data → Processing → Intelligence → Alerts → Action

Hero pipeline
1
DeviceSensor data
2
MQTTConnect
3
IngestValidate
4
ProcessReal-time
5
StoreTime-series
6
AnalyseRules & trends
7
AlertNotify
8
ActWeb / mobile
Cold-chain IoT sensors in the field
Cold-chain IoT sensors in the field

Project at a Glance

A production-oriented IoT intelligence platform for multi-customer cold-chain and industrial monitoring.

Deployment snapshot
ClientNerasTech
DomainIoT / Cold Chain / Industrial Monitoring
SolutionIoT Monitoring & Intelligence Platform
ConnectivityMQTT
ProcessingReal-time IoT Data Processing
MessagingRabbitMQ
DatabaseMongoDB Time-Series
ApplicationsWeb + Mobile
ArchitectureMulti-Tenant
AnalyticsReal-Time & Historical
AlertsRule-Based Alerts & Notifications
AccessRole-Based Access Control
Project highlights
MQTT
Device connectivity
RT
Real-time processing
TS
Time-series storage
Rules
Alert engine
Multi
Tenant isolation
App
Web + mobile
MQTT IoT gateway for device telemetry
MQTT IoT gateway for device telemetry

The Challenge: IoT Data Was Growing. The Platform Needed to Grow With It.

As IoT deployments expand across customers and locations, simply receiving sensor data is not enough. NerasTech required a more scalable and production-oriented architecture—modernising the backend data-processing architecture and creating a unified monitoring experience for IoT data.

What the platform needed to answer
Device online?Live connectivity status
Current readings?Sensor values now
Trends over time?Historical behaviour
Threshold crossed?Exception detection
Scale & tenancy requirements
Customer / site ownershipWho owns each device?
Alert acknowledgementWho handled the event?
Secure isolationCustomers see only their data
Growing volumesArchitecture must scale
Multi-tenant IoT operations dashboard
Multi-tenant IoT operations dashboard

The MLT Approach: Building the Intelligence Layer Around IoT Data

MLT developed a platform architecture that separates data ingestion, processing, storage, APIs and applications. Rather than allowing devices to directly drive application logic, IoT data passes through a structured processing pipeline.

Resulting architecture
IoT Devices → MQTT BrokerExisting device ecosystem
Data Ingestion Service → RabbitMQValidate, transform, queue
Real-Time Processing ServiceStatus, storage, alert evaluation
MongoDB Time-Series → API → Web / MobileIntelligence delivered to users

01 — IoT Device Connectivity

The platform receives data from existing IoT devices through MQTT, allowing the solution to work with the existing device ecosystem without requiring firmware changes during the implementation phase.

Documented device types
iSenseSensor endpoints
iCPUEdge / controller units
Hawk-IMonitoring devices
MQTT payloadsIngestion entry point

Why this matters: the platform can evolve independently from the underlying device layer—so the IoT ecosystem can grow without redesigning the entire software architecture for every new device or deployment.

02 — Reliable Data Ingestion

The Data Ingestion Service is the entry point for IoT data. Separating ingestion from downstream processing allows the platform to handle data more reliably and scale processing independently.

Ingestion service responsibilities
MQTT receptionMessage intake
Device validationKnown endpoints only
Payload validationSchema / integrity
TransformationNormalize readings
Raw archivalKeep source records
Queue publishRabbitMQ handoff
Error loggingTrace failures
Retry handlingResilient delivery

03 — Real-Time Data Processing

Once data enters the pipeline, the Real-Time Processing Service converts raw IoT messages into usable platform data—and scheduled jobs support aggregation plus operational functions such as offline-device detection and alert auto-resolution.

Processing layer manages
Sensor processingStructured readings
Data storagePersist to time-series
Device statusOnline / offline tracking
Alert evaluationRule checks
NotificationsTrigger user alerts

04 — Time-Series Intelligence

IoT data is inherently time-based. A temperature, humidity or other sensor value becomes meaningful when viewed against time, location, device, customer, historical trends and operational thresholds.

The platform uses MongoDB Time-Series storage for efficient handling of device readings and aggregated data—including device readings, 5-minute aggregates and 30-minute aggregates—enabling historical analysis without repeatedly scanning raw high-frequency data.

Time-series storage model
1
Raw readingsHigh-frequency values
2
5-min aggregatesShort-window trends
3
30-min aggregatesOperational summaries

05 — Intelligent Alerts

Don't just show the data—tell someone when something needs attention. The platform includes a rule-based alert engine that shifts IoT from passive monitoring to exception-driven operations.

Configurable conditions
Greater thanUpper threshold
Less thanLower threshold
Equal toExact match
Between rangeDefined band
Documented alert workflow
1
ReadingReceived
2
EvaluateRule check
3
CreateAlert record
4
NotifyPush / in-app
5
AckUser confirm
6
ResolveAuto / manual

06 — Centralized Dashboards

Browser-based monitoring covers customers, sites, devices, historical trends, alerts, analytics and device status—with visualization formats including line charts, bar charts, gauges, donut charts and statistical widgets.

What operators can monitor
Customer dashboardsOrg-level visibility
Site monitoringLocation context
Device monitoringEndpoint health
Historical trendsBehaviour over time
Alerts & analyticsExceptions first

07 — Multi-Tenant IoT Architecture

A major architectural capability is multi-tenant design. The hierarchy is Organization → Sites → Devices → Sensors. Each customer operates within its own logical data boundary, with isolation enforced across API, database, dashboard and alert layers.

Tenant hierarchy
1
OrganizationCustomer boundary
2
SitesLocations
3
DevicesEndpoints
4
SensorsReadings
Why this matters
Isolated dataOrg users see only their org
Admin oversightPlatform-wide management
One codebaseMany customers
Provider-readyScale end-customer fleets

This allows an IoT platform to support multiple customers without creating a completely separate software platform for every deployment—especially suitable for IoT solution providers managing deployments across multiple end customers.

08 — Web & Mobile Access

IoT intelligence shouldn't remain inside a control room. The platform provides web and mobile access so users can monitor devices and alerts remotely. Push notifications are supported through Firebase Cloud Messaging.

Mobile application access
DashboardsOperational views
SitesLocation browse
DevicesEndpoint status
AlertsException inbox
Push notificationsFCM delivery
Profile / orgAccount context

09 — Secure Access

The architecture supports distinct roles—Administrator → Organization Administrator → Organization User—with different levels of access to organizations, devices, dashboards and alerts.

Security capabilities
JWT authAPI identity
RBACRole-based access
MFAStronger login
Tenant isolationData boundaries
HTTPS + hashingTransport & secrets
Sessions / rate limitsAbuse protection

10 — From Device to Decision

The real value of the project lies in the complete data journey—the MLT IoT Intelligence Pipeline.

MLT IoT Intelligence Pipeline
DEVICE → CONNECTSensor generates data · MQTT transports it
INGEST → PROCESSValidate payload · convert to structured info
STORE → ANALYSETime-series history · rules & trends
ALERT → ACTNotify users · respond on web or mobile

Technology Architecture

Built as a production-oriented IoT platform with documented separate production infrastructure and CI/CD deployment practices.

Technology components
ConnectivityMQTT
BackendNestJS · TypeScript
MessagingRabbitMQ
DatabaseMongoDB Time-Series
InfraRedis · AWS S3
WebNext.js · React · Tailwind
MobileReact Native
NotificationsFirebase Cloud Messaging

Business Impact

What the platform enables
Real-time visibilityDistributed devices, one view
Faster responseRule-based exceptions
Historical intelligenceBehaviour over time
Multi-customer scaleIsolated tenants
Web + mobile accessBeyond the control room
Extensible foundationAdd apps & analytics
IoT monitoring alone
  1. Sensors send data
  2. Raw readings accumulate
  3. Hard to scale across customers
  4. Exceptions found late
IoT intelligence platform
  1. Structured ingestion pipeline
  2. Real-time + time-series insight
  3. Multi-tenant isolation
  4. Alerts → web / mobile action

Conclusion: From IoT Monitoring to IoT Intelligence

The NerasTech project demonstrates an important capability of Mountain Lamp Technologies: we don't stop at connecting sensors. We build the software intelligence layer that sits between devices and the people responsible for the operation.

From MQTT ingestion to real-time processing, from time-series analytics to alerts, and from dashboards to mobile applications, MLT can create the complete software ecosystem required around an IoT deployment.

Connect. Process. Understand. Act.

Planning a scalable IoT monitoring or cold-chain intelligence platform?

Mountain Lamp Technologies can help design and deliver the connectivity, processing, time-series analytics, alerting and web/mobile experience your IoT deployments need.

Back to all case studies
Get in touch

Ready to plan a scalable IoT monitoring platform?

Share a few details about your cold-chain, industrial or multi-tenant IoT deployment and we’ll help design the right architecture.

No pitch decks. Just a hello — we’ll take it from there.