IoT Utility Metering SaaS Platform

Managing multi utility meters across sites with spreadsheets and supplier portals is slow, fragmented and hard to scale. MeterHub replaces that with a cloud IoT and SaaS platform where AWS IoT gateways stream readings into a time series store, and a multi tenant web portal turns them into dashboards, alerts, reports and invoices. Ingest stays asynchronous, so high volume telemetry never slows the user experience.

Client is a UK based technology and metering solutions provider serving facilities managers, energy managers and multi site operators. Their commercial SaaS portal, MeterHub, monitors electricity, gas, water and heat across client estates. It supports sub metering, tenant billing and operational analytics from a single hub.

Fragmented meter data across spreadsheets and multiple supplier portals Manual, slow tenant recharging and sub-meter billing cycles Limited real-time visibility of consumption spikes, leaks, and anomalies Difficulty scaling from a few meters to large multi-site estates No clear role model separating administrators, staff, and tenant/consumer access Need for commercial packaging (trial, plans, usage-based pricing) alongside technical monitoring High-volume IoT telemetry that must not degrade application performance

MeterHub is built as a hybrid IoT and SaaS architecture. Physical meters feed into SP Wales AWS IoT gateways, which publish MQTT payloads to AWS IoT Core. An Influx Writer Lambda normalises and classifies readings, writes them to InfluxDB, and asynchronously invokes a Meter Sync Lambda to register meters in PostgreSQL when the gateway is known. An Express.js API on Amazon ECS serves the product layer: authentication and multi-tenancy, locations and meters, alerts, reports, billing PDFs, Stripe subscriptions, and Super Admin gateway provisioning. Redis and BullMQ handle heavy report and invoice generation in the background. A React application provides dashboards, analytics, alerts, reports, billing, and account/subscription workflows, while a separate landing site drives acquisition, pricing, and leads. Time-series queries go to InfluxDB first (with Redis caching); PostgreSQL holds tenancy, templates, history metadata, and commercial state.

• Node.js + Express.js (backend API, auth, business logic, workers) React + Vite + Tailwind CSS
• Recharts + Leaflet (analytics charts and site maps)
• PostgreSQL ( users, gateways, meter registry, templates, Stripe state)
• InfluxDB (primary time-series store for meter readings)
• Redis + BullMQ (queues, caching, background report/billing jobs)
• AWS IoT Core + AWS Lambda (MQTT ingest, reading write, meter sync)
• Amazon ECS, Docker, Amazon ECR (API deployment)
• Amazon S3 (IoT credential packages, report and billing PDFs)
• Stripe (SaaS checkout, portal, webhooks, usage quantity sync)
• Nodemailer / SMTP (alerts, password reset, report and invoice emails)

Single portal for electricity, gas, water, and heat across multiple sites Near real-time monitoring without blocking the UI, because ingest is asynchronous Faster tenant billing via invoice templates, PDF generation, and email delivery Earlier detection of spikes and leaks through configurable alerts and history Clear access control: consumers see only assigned meters Commercial readiness with Starter / Professional / Enterprise plans, trial, and usage-based billing Scalable data plane (InfluxDB) separate from product state (PostgreSQL), ready for future analytics consumers Independent deployability of landing page, app, API, and Lambdas across test and production environments

MeterHub successfully delivers a production multi-utility remote metering SaaS platform, by combining AWS IoT ingest, serverless writing to InfluxDB, a secure multi-tenant Express API on ECS, and a React portal for monitoring, alerts, reports, tenant billing, and Stripe subscriptions. By separating the IoT data plane from the application and commercial plane, the platform captures meter activity reliably at scale, keeps the user experience non-blocking, and remains easy to extend with additional consumers and features over time.