CODESCAPEAI — product studioCODESCAPEAI
All work/Engineering · 2025
02Climate-tech platform rebuilding how grids trade energy
Live · Climate Tech

Helio OSReal-time pricing engine for 9 GW of renewable capacity.

Year2025TrackEngineeringSprint14 weeksShapeLead + 4 engineersIndustryClimate Tech
Helio OS
HO · EngineeringGo · Kafka · TimescaleDB
47msmedian pricing latency
Scroll to read the case study
ArchitectureReal-time engineeringInternal toolingArchitectureReal-time engineeringInternal toolingArchitectureReal-time engineeringInternal tooling
The case study

From a 90-day windowto a body of work.

A re-architecture from monolith to a typed event-sourced core, with a trading console the energy team actually uses at 3am. Cut median pricing latency from 1.2s to 47ms. Below is the long version — the brief, the approach, and the numbers we put on the wall after launch.

Helio's pricing was running on a Rails monolith that tickled a single Postgres primary. The 3am trading desk was a Discord channel and a prayer.

We carved the hot path into a Go + Kafka event-sourced core, added a typed Rust optimiser, and rebuilt the trader console as a single screen with a typed data layer. Every screen has an undo, every action is auditable.

47ms median pricing latency, 9 GW of renewable capacity traded live, and a trading desk that finally sleeps. Pager volume fell 71% in the first month.

The build

Inside the product.A clickable tour.

01/03
Helio OS — frame 1
Frame 01 · HOHelio OS
The receipts

Numbers, not adjectives.

Four metrics the client agreed to put on the wall. Verified internally before the launch, verified again at the 90-day mark.

010msmedian pricing
020GWGW traded
030%pager volume
040wkweeks shipped
The stack

Tools, chosen on purpose.

Every technology on the list earned its place in the build — chosen for the constraint, not the trend.

01Go
02Kafka
03TimescaleDB
04React
05Rust services
How we ran it

Four pillars,one crew.

Strategy

We sat with their team, walked every existing flow, and wrote the brief on day three.

Design system

A small, opinionated component set the whole team could ship from on day one.

Engineering

Senior crew, weekly demos, real test coverage, and a deploy pipeline the team kept after handoff.

Launch + handoff

Monitored for two weeks post-launch, then handed the keys over with a runbook the team could read in a coffee.

Awwwards · SOTD × 4CSS Design Awards · Best UIClutch · Top 1% GlobalDribbble · Featured StudioFWA · Site of the Day

The trading desk doesn't ask for new features anymore. They just turn the console on and the day works.

Devansh Rao · CTO, Helio OS— on the launch, in their own words
Want a case study like HO?

Let's add your projectto the wall.

Bring a brief, a Loom, or a half-finished Figma. If we're the right crew, you'll know in the first meeting. If we're not, we'll point you to someone who is.

  • Reply within 24h
  • Senior partner on the call
  • References on request
  • First meeting is free