Live delivery
GETPP climate MRV platform
Global Energy Transition
A climate-action intelligence platform that connects field work, participant records and verifiable smart-meter data.
The Challenge
A Delivery Shaped Around the Whole System.
Build a climate MRV platform that can work for people in the field today while accepting trustworthy energy readings from a growing device fleet tomorrow.
What We Delivered
Cuesoft delivered the public experience, GETPP application backend, data layer and training portal, then designed a smart-meter relay that makes field-device onboarding independent of central infrastructure operations.
Product and Interface Design
Experience Design Is Part of the Delivery.
Role-Specific Workspaces
Cuesoft designed the experience around the people who have to act on climate data: participants, field agents, teachers, administrators, partners and funders. Each role gets the right dashboard, navigation and next action instead of one generic control panel that exposes every workflow to everyone.
Smart-Meter Setup That Reflects the Field
The device-registration interface adapts to the information a real provider requires. A Growatt meter needs a serial, a DESS Monitor device requires its dashboard identifiers, and a Cuesoft device uses the pairing code printed on its label. The design makes those differences clear before a reading ever reaches the relay.
Evidence Is Part of the Journey
Activity, baseline and verification journeys are designed around the evidence the programme needs: form data, photo, GPS and meter readings. Review and data collection are not hidden implementation details; the interface makes each requirement and state legible to the person doing the work.
System Architecture
The Technical Foundation.
A Platform, Not a Brochure
The public site, participant-facing application and API are delivered as connected surfaces. The platform uses Firebase App Hosting on Google Cloud and Firestore Enterprise with MongoDB compatibility for the operational data layer.
A Dedicated Cellular Device Relay
The smart-meter ingress is a small Google Cloud service with a fixed resource ceiling and high request concurrency. Its only job is to verify device passports and forward raw readings to the platform that owns them.
A Recovery-Aware Data Layer
The production database has point-in-time recovery, scheduled backups and delete protection. Those controls are part of the delivery because a measurement platform is only credible when its operating data can be recovered.
Engineering Work
Details That Make the Difference.
Device Passports Remove a Fleet Bottleneck
Each device carries a short Ed25519-signed passport that names its serial and tenant. The relay verifies public keys fetched from the owning platform, so provisioning a new device does not require an operator to add a key, secret or database row to the relay.
Every Reading Is Independently Authenticated
A passport routes a device but does not authorise a reading. Each payload is signed with that device’s own secret. The platform checks the raw signed bytes, a bounded timestamp and a one-time nonce before it accepts data, preventing forged or replayed submissions.
Failure Semantics Preserve Field Data
The relay distinguishes a bad credential from an upstream outage. A bad credential is refused; a configuration or upstream failure returns a retryable response so a buffering device retains its reading rather than discarding it.
Keys Rotate Without Re-Flashing Hardware
The platform publishes public keys to the relay and can add a replacement key before changing the active signer. That makes key rotation a platform operation, not a recall of every deployed meter.
Cost and Operating Design
Spend Less on Idle Infrastructure.
Capacity Follows Device Traffic
The relay uses a small serverless footprint rather than permanently allocated device infrastructure. Requests are short forwards, readings retry, and the instance ceiling protects the client from an unbounded ingestion bill.
Managed Recovery Over Self-Operated Database Overhead
Managed data recovery and deployment controls reduce the operational work needed to run a production platform, while keeping the rollback path explicit and tested.
Edge Choices Follow Partner Reality
Cloudflare is used where an edge proxy improves public-surface protection. The USSD-facing API host remains DNS-only because that provider fails through a proxy; compatibility is treated as a security and reliability requirement, not something to hide behind an architecture diagram.
Technical Capabilities
- 01Product and UI design
- 02Frontend engineering
- 03Backend systems
- 04Climate MRV data
- 05Smart-meter ingestion
- 06Training portal delivery