SURGE is organized around four core modules that customers buy individually or together: Energy Mapping for kWh and carbon accounting, Vessel Tracking for fleet position and fuel consumption, Water Analytics for KLHK SPARING and IPAL operations, and Wastewater Logger for regulated effluent reporting. Each module ships with its own data model, dashboards, alert rules, and report templates, but all four share the same underlying tenancy, identity, and notification infrastructure — so customers running multiple modules have one login, one alert inbox, one user-management screen, and one billing relationship.

Platform features are deliberately enterprise-grade rather than dashboard-grade. SURGE exposes a documented REST API and webhook system for integration with ERP, CMMS, and BI tools the customer already runs. Native mobile applications on iOS and Android deliver alerts, key dashboards, and acknowledgement flows for operators who do not sit at a workstation. White-label deployment is available for partners reselling under their own brand. Multi-channel alerting covers SMS, email, and WhatsApp — important in Indonesian operations where WhatsApp is often the most reliable notification channel. Every action is logged to an immutable audit trail keyed to user, role, and timestamp.

Deployment options match the customer's data-sovereignty posture. The default is cloud-hosted in AWS Asia Pacific (Jakarta) under SURIOTA's managed-service operation, with 99.9 percent uptime SLA. Customers with strict on-premise requirements deploy SURGE as a Docker or lightweight Kubernetes (K3s) stack on their own infrastructure. Hybrid is increasingly common: sensitive process data stays on-premise, while non-sensitive aggregates and executive dashboards run in the SURIOTA cloud — the customer gets visibility without the regulatory exposure of pushing raw process data outside their facility.

Integration is intentionally undemanding. Any device speaking Modbus RTU or TCP, OPC UA, MQTT, REST, or even just CSV upload can feed SURGE. We do not require customers to rip and replace their existing SCADA, DCS, or historian — SURGE reads from whatever the plant already runs, normalizes the data into its own model, and presents the unified view. Existing investments are preserved; new capabilities accrue on top. This is the architectural principle that makes SURGE viable for brownfield Indonesian industrial sites where ripping and replacing is rarely an option.

Underneath the modules and integrations sits a deliberately conservative technology stack: time-series storage on InfluxDB and TimescaleDB, application layer in Python (FastAPI) and Node.js, web frontends in React, mobile apps in React Native, infrastructure as code in Terraform and Ansible. Every choice prioritizes long-term maintainability over fashion. The platform's customers expect to be running on SURGE in 2035, not on whatever framework was trendy in 2026.