Cloud SCADA under your brand
Modbus → MQTT → live monitoring, history, alarms and setpoints. Multi-tenant, RBAC and branding — without building from scratch.
2–4 wks
to pilot
1000+
sites
30 min
sandbox demo
Who it's for
System integrators
Turnkey SCADA under your brand: multi-tenant, RBAC, object scope.
OEM & manufacturers
Cloud monitoring for your equipment: logo, domain, API, on-site collector.
Energy & utilities
Centralized fleet monitoring: dashboard, alarms, history, operator mode.
MSP & cloud providers
SCADA as a service: Docker, Helm, on-prem or managed SaaS.
Problem → solution
| Pain | WL-SCADA |
|---|---|
| Every project from scratch | Single platform, equipment catalog configuration |
| Years to market | Ready stack: UI + API + collector + MQTT + DB |
| No white-label | Logo, color, domain, tenant isolation |
| Legacy SCADA | Modern web, REST, SSE live, audit |
Platform capabilities
Live monitoring
SSE push, online/offline, data quality. Hierarchy: customer → site → groups → registers.
Alarms & history
Journal, ack/clear, filters. InfluxDB charts, 30–90 day raw retention.
Setpoints with audit
PLC writes: API → MQTT → collector → Modbus. Monitor/control separation.
White-label
App name, logo, accent color, custom domain per tenant.
RBAC & scope
Admin/operator/viewer roles. Scope by customers and sites.
Edge collector
Modbus TCP/RTU, tiered polling, outbox, hot-reload. 1 collector = 1 site.
Platform UI
Dashboard — overview, collector, alarms
Alarm journal
Site catalog
History and charts
Site card — equipment groups
Live register table
Modbus register directory
Equipment catalog
Audit log
Architecture
Modbus on site → MQTT → ingest → Redis (live) + InfluxDB (history) → Next.js UI
- 1Collector polls Modbus on schedule
- 2Telemetry to MQTT (values + history)
- 3Backend writes live to Redis, history to InfluxDB
- 4UI: REST + SSE for operators
- 5Setpoints: API → MQTT → collector → Modbus write
Stack
Delivery models
OEM license
White-label + rollout under partner brand
On-prem
Docker Compose or Helm in customer perimeter
Managed SaaS
NineLab cloud, you sell under your brand
30-day pilot
Fixed estimate, typically 2–4 weeks to acceptance
Approach comparison
| Criterion | Build from scratch | Legacy SCADA | WL-SCADA |
|---|---|---|---|
| Time to pilot | 12–18 mo | 3–6 mo setup | 2–4 wks |
| White-label | Expensive | Rare | Built-in |
| Web UI | From zero | Desktop | PWA, dark mode |
| Multi-tenant | Separate | No | Yes |
| Edge + cloud | Design | Partial | Collector + SaaS |
Rollout steps
Presales and sandbox tenant demo
Infrastructure: MQTT, DB, frontend
Tenant, branding, equipment catalog
On-site collector, RBAC, scope
Acceptance tests and handover
FAQ
Modbus TCP/RTU today. OPC-UA and SNMP on roadmap for OEM requests.
Yes: Docker Compose, Helm/K8s, no public cloud required.
Each tenant gets app name, logo, color and optional custom domain (CNAME).
Per-entity JWT tokens, revoke, TLS on MQTT. Setpoint writes require permissions and audit.
WL-SCADA is a licensed product. Custom is bespoke development for unique processes.
Depends on model (OEM / on-prem / SaaS) and site count. Fixed pilot estimate after a short brief.
WL-SCADA is for lawful dispatch and monitoring of industrial equipment. The customer is responsible for site safety and applicable regulations.
