Solid data foundation
Official sources, CSV import, and future approved integrations are shaped into a clean market data layer.
Ukraine energy market · DAM · IDM · BM · AI
Alvo gives traders, analysts, BESS teams, risk desks, and API teams a strong market workspace: official DAM and IDM prices, forecasting, an imbalance-risk (BM) signal, AI explanations, and audit trails in one fast operating loop.
Official sources, CSV import, and future approved integrations are shaped into a clean market data layer.
Spreads, volume, thresholds, fees, and expected P&L are calculated so the team sees the action without noise.
The price and schedule model is already compatible with BESS, APIs, backtesting, and future automation.
Security headers, server validation, audit logs, and no automatic order submission in v1.
Markets & coverage
Official OREE prices, spread plan, and an AI brief for every hour.
DAM/IDM market switch in the workspace to adjust the plan.
A forecast layer over official data — validated on history.
An imbalance-risk signal so you can adjust the position in time.
State of charge, cycles, degradation, and charge/discharge schedule over prices.
Architecture
OREE and UEEX adapters, CSV import, normalization, validation, caching.
Spread detection, fees, thresholds, limits, BESS-ready constraints.
Trading brief, anomaly notes, automation suggestions, deterministic fallback.
Human approval, audit trail, RBAC-ready actions, no unsafe submit in v1.
Workflow
The first release already covers DAM, IDM, forecasting, and an imbalance-risk signal — without legally risky automatic order submission.
Public OREE prices and UEEX benchmark indexes are normalized into a single market layer.
The algorithm selects low/high hours with thresholds, fees, and limits applied.
The AI brief creates a summary, checklist, anomalies, and next automations.
The plan exports to CSV, and key actions are written to the audit trail.
Roadmap
DAM and IDM, price forecasting, imbalance-risk signal, AI brief, CSV export, audit trail.
SoC, power, cycles, degradation, and charge/discharge over DAM prices.
Backtesting, signals API, and white-label analytics for market participants.
Official integration
To start, Alvo reads open market data and does not act on behalf of a trader. The next level is official access, agreements, keys, action logs, and roles.
Security & compliance
Alvo v1 does not submit orders. It speeds up decisions, records actions, and prepares the foundation for future approved integrations.
Economics
Example based on 4 recommended pairs
After fees and thresholds
Data, plan, AI brief, export
Human approval in v1
Subscriptions
We start with monthly B2B subscriptions: each plan has clear seats, AI brief limits, API limits, and controlled capabilities. No automatic order submission and no guaranteed P&L claims.
For a first trading team that wants to move through daily DAM and IDM decisions faster.
up to 5 users · 300 AI briefs · CSVFor teams that need roles, decision history, limit control, and leadership reports.
up to 15 users · 1,500 AI briefs · read APIFor storage teams modeling charge/discharge, cycles, and degradation over DAM prices.
up to 25 users · 3,000 AI briefs · BESS APIFor clients that need Alvo as an internal API layer or white-label analytics.
custom users · custom AI/API · SLA+1,000 AI briefs or a stronger model for complex risk/anomaly cases.
Additional trader, risk, analyst, or API-client users with roles.
Approved data connectors, private CSV/API sources, legal and security review.
API preview
{
"zone": "IPS",
"date": "2026-05-13",
"volumeMwh": 5,
"mode": "human_approval"
}FAQ
No. V1 works as decision support: analysis, explanations, export, and audit trail. Order submission remains under trader control.
Usually not for analytics software, but electricity trading and representing a market participant require separate legal review.
From public Market Operator DAM data and UEEX benchmark indexes. Later we can add ENTSO-E, Energy Map, CSV, private sources, and internal client data.
AI compresses the market into actions: summary, risks, anomalies, checklist, and next automations. Calculations remain deterministic and verifiable.
Open the workspace, generate an AI brief, export the plan, and inspect the audit trail. Next we connect CSV import, BESS, and the API layer.