Helio

Helio is deployed by deploying your own copy on Vercel, which the official documentation says takes just 5 minutes.

Helio does not rely on a database and does not persistently store generation data on the server side.

Helio login credentials never reach the browser.

Helio is designed without tracking.

Helio pulls counts from the inverter manufacturer's interface in real time on each request and then performs conversion and presentation in memory, so page loading depends on the availability and response speed of the inverter manufacturer's interface.

Helio does not communicate directly with inverters but calls the cloud platform interface, so it can only cover devices connected to the ShineMonitor / SmartClient system.

Helio does not perform device control or fault diagnosis; it focuses solely on viewing data.

Helio displays the day's power generation as soon as it opens, with data coming directly from the inverter's own energy counter.

Helio reads raw energy counts from inverters via the ShineMonitor / SmartClient interface.

Helio provides real-time power, 5-minute granularity curves for any historical date, 30-day, yearly and lifetime generation history, as well as earnings calculated using user-defined currency and electricity price.

Helio is licensed under MIT and is completely free.

Helio is a knowledge-graph-based enterprise knowledge agent designed to answer questions about service dependencies, team ownership and decision provenance.

The Helio team used FalkorDB to build a synthetic fintech knowledge graph with 7 node types and 14 edge types, simulating an organization of 120 people during a payments migration.

Before generating any data, the Helio team hand-wrote 20 facts about the company in GROUND_TRUTH.md as the answer key, of which 5 questions have no answer in the graph.

In Helio's scoring framework, refusing to answer is set as an explicit scoring category with the same weight as a correct answer, which changes the objective of prompt optimization.

Using only ORDER BY count DESC returns Priya Sharma, who has the most commits, which is technically correct in quantity but completely wrong as an answer to 'who knows this service' because it ignores recency.

Helio's solution is to return two independent signals, count and recency, and refuse to blend them, for example noting that the platform team owns the payments service, Ravi Menon was still working on it recently (2026-09-28), and Priya Sharma has the most commits but is out of date.

Helio received 81 votes and ranked 20th on Product Hunt, with 5 comments.

Helio's validation gate once wrongly judged four correct refusals as failures, because it required eight spellings of 'no' to appear in the same sentence (AND logic).