nrgonDeveloper

The nrgon platform

VERSION 0.1 · 2026-10-12 · developer.nrgon.net/

Software for energy storage in Southeast Asia: planning, monitoring, dispatch and settlement for batteries at homes, shops, factories, data centres and on the grid.

Goals

Open standards

HTTPS, S3, Redis, OCI containers, Markdown, JSON, CSV, YAML. No nrgon-only protocol.

Reuse

A piece built for one project is shaped for the next: a tariff library, an adapter, a report.

Any data

Meter readings, telemetry, bills, tariffs, weather, swap logs, documents. Stored as received, original kept.

One place

Applications, components and data run on the same platform. A result in one is an input to the next.

Architecture

SOURCESDevices and metersPartner cloudsOn-site teamsEDGEEdge networkSTORAGEBuckets, rawRedis, latestDrive foldersCOMPUTEComponentsUSEApplications

Devices and partner clouds push to an HTTPS endpoint at the edge. The endpoint writes the raw message to a bucket and the latest value to Redis. People on site put documents and photos in the project's Drive folder. Components read from all three and write their results back. Applications read the results.

Layers

ApplicationsAI EMS, operator portal, configurator, showroom, botsComponentstariff library, measurement and verification, protocol adapters, reportsDatadata.nrgon.net, site and asset data, documentsFundamentalscompute, containers, Redis, buckets, Drive folders

Platform describes the fundamentals. Data describes formats and where each kind of data goes. Components describes how software is shaped for reuse. Design holds the visual and writing rules.

Region

Singapore. Compute, storage and the edge are in the Singapore region of their providers. Latency to Bangkok, Ho Chi Minh City, Kuala Lumpur and Jakarta is under 50 ms.