Most energy software is written by developers who have never watched a price move, or by traders who cannot ship. We do both, which is why our tools reach production instead of a drawer.
The screen somebody actually watches while deciding. Live prices, order book depth, spreads, positions, exposure and profit and loss that updates as the market moves — not a report generated overnight.
Getting data in, keeping it correct, and knowing when it is wrong.
| Source | What we have connected |
|---|---|
| ENTSO-E Transparency | Prices, load, generation, forecasts, outages across every European bidding zone. |
| National TSOs | ČEPS, Netztransparenz, regelleistung.net, Elexon, RTE, PSE, Terna and others — see our guides. |
| Exchanges | Day-ahead and intraday results; live intraday order book over OTE's AMQP interface with a client certificate. |
| Weather and forecasts | Ensemble wind and solar forecasts, temperature, residual load. |
Every integration stores what arrived, when it arrived, and which version it was. That sounds pedantic until the first time a number changes retroactively and you need to know what you knew at the time.
Testing whether an idea is real before money depends on it.
Before anything can be traded or reported on, the data has to be in one place and be trustworthy. Energy data management is the unglamorous half of every project we do: market data from exchanges and TSOs, meter readings, schedules, forecasts — each with its own format, its own delay and its own gaps.
| What usually goes wrong | What we build instead |
|---|---|
| Every source has its own resolution — 15 minutes, hourly, irregular — and something slips when they are joined. | An ingest layer that knows the resolution and time zone per source and survives the clock change. |
| Values get revised after publication, so yesterday's report no longer reconciles. | Versioned storage: what was known at the time stays retrievable, which is the only way a backtest means anything. |
| Market data sits in one system, own measurements in another, and the comparison happens in a spreadsheet. | One store for both, with an API your existing systems read from. |
| Nobody notices a feed has stopped until a number is missing in a report. | Per-source monitoring that alarms before anyone finds the hole. |
On top of that sits the electricity management software people actually look at — energy analytics that answer a question rather than fill a page. Our German-language version of this page goes deeper into the same ground: Energiedatenmanagement.
Custom energy software is not a phrase we love, but it is what this is: electricity trading software written for one desk and one market rather than sold to a thousand. Most of our work is software development against live market data, not configuration of somebody else's platform.
Sooner or later someone asks whether you should buy an ETRM — an Energy Trading and Risk Management platform. The honest answer depends on what actually hurts, and it is worth saying out loud that we do not sell one.
| An ETRM platform fits when… | Something built for you fits when… |
|---|---|
| You trade several commodities and need one position and risk view across all of them. | You trade one market and need depth in it, not breadth across ten. |
| Regulatory reporting — REMIT, EMIR — is a large part of the job. | Your edge is in timing and execution, and the standard screen does not show what you need. |
| You need credit limits, confirmations and settlement workflow. | Your data sources are non-standard: an order book feed, a TSO API, a model output nobody else ingests. |
| A team of twenty people has to work in the same system. | Two or three people need to decide inside a quarter hour. |
| You are comparing ETRM systems from vendors and need a system of record with support behind it. | You already have one, and what is missing is the fast layer on top of it for the market you actually trade. |
The two are not rivals as often as vendors suggest. A common shape is an ETRM as the system of record with a thin, fast layer on top for the market you actually trade — the dashboard the trader watches, writing back positions the platform then settles.
Where we are useful is that second layer, and the data underneath it. If what you need is a full ETRM, we will say so rather than build a worse one.
We are a small team and take a small number of projects. If the work is not something we can do well, we will say so at the first call rather than three invoices in.
We work the Czech intraday and balancing markets ourselves — real positions, real settlement, real losses when a model is wrong. Everything on this site comes out of that: the ENTSO-E guide, the live price tracker, the country guides.
That is the difference we are selling. Plenty of firms can write a React dashboard. Rather fewer know why your imbalance price just printed at ten times the day-ahead, or which of the four German TSOs published the number you are looking at.
A dashboard, a data integration, a backtest that you do not trust — describe the problem and we will tell you whether we are the right people for it.
Get in touch