// VOLTNIR / EPEX SPOT INTRADAY

Middleware for
power trading desks.

The connection layer between your software and the European intraday power market. M7 protocol, both versions, fully managed.

Operational 99.98% uptime · trailing 90d EPEX M7 v6 + v7
// 01 · THE PROBLEM

Power markets move in seconds.
Most desks are stuck waiting on their stack.

EPEX Spot Intraday runs on M7 — a protocol that's evolved across two major versions, with strict sequencing, snapshot/delta order books, and connection rules that punish mistakes. Building this layer in-house takes a year. Maintaining it costs another engineer every year after.

The desks that move first win. The desks that babysit their connection lose.

Without Voltnir + 412 ms · stale book
14:32:07.000+ 500 ms+ 1.0 s
With Voltnir + 38 ms · live state
14:32:07.000+ 500 ms+ 1.0 s
// 02 · WHAT IT DOES

Voltnir sits between your trading software and EPEX.

You connect to Voltnir over REST or gRPC. Voltnir handles M7 — both versions — the order books, the session state, the reconnects, the gap detection. You send orders, you read the book, you trade. The market protocol is our problem, not yours.

// Client
Your software
Strategy · OMS · book runner
// Voltnir Live
Voltnir
Sessions · book state · sequencing
// Market
EPEX M7
European intraday power
// 03 · DEPLOYMENT

Voltnir runs in your environment. Not ours.

Voltnir is delivered as software you deploy on your own infrastructure — your servers, your data center, your cloud tenant. We don't host your order flow. We don't see your positions. We don't have access to your book.

Your hardware, your rules

Bare-metal, private cloud, VM, container — Voltnir runs wherever your security team is comfortable. No outbound calls to Voltnir servers required for trading.

Your data never leaves

Orders, fills, positions, strategy logic — all of it stays inside your network perimeter. We ship a binary; you run it.

Compliance-friendly

Co-location with EPEX gateways is supported. Air-gapped deployments are supported. We help with the setup; we don't operate it.

Your environment
// Your software
Strategy · OMS
// Voltnir
Middleware binary
Single egress · M7 over TLS
// External
EPEX M7
// 04 · TEAMS

Model your desk the way it actually works.

Voltnir supports virtual members — logical trading entities that map to your real EPEX memberships. The relationship between members and users is many-to-many: one user can act across multiple members, and one member can be operated by multiple users. Each user holds a set of permissions; each member carries its own MW limit.

Virtual members

Group order flow by legal entity, strategy, or trading book. Each member has its own market session, its own credentials, and its own MW limit — a hard cap on open position enforced before orders touch the market.

Users with permissions

A user is not bound to a role. Permissions are composable — submit, modify, cancel, adjust limits, read books, export audit — granted per user, per member. Add or revoke without redeployment.

Many-to-many seats

One user can operate on many members. One member can be operated by many users. Voltnir keeps the matrix; every action is attributed to the exact user–member pair.

3 Virtual members
↔ many-to-many ↔
Users 4
Member · ALPHAEPEX-DE
MW limit+ 25.0 MW
Member · BRAVOEPEX-FR
MW limit+ 18.0 MW
Member · GAMMAEPEX-NL
MW limit+ 12.0 MW
j.koenig2 seats
submitmodifycancelread-book
s.weber1 seat
adjust-limitsread-bookexport-audit
m.bauer2 seats
read-bookread-fills
l.martin2 seats
submitmodifycancel
Member edge User edge Each line is one seat · attribution travels with every action
// 05 · AUDIT

Every action, every order, every login — recorded.

Energy trading is a regulated business. Voltnir treats audit as a first-class concern, not a bolt-on.

Every order submission, modification, cancellation, and fill is logged with a monotonic sequence number, a UTC timestamp to the millisecond, the originating user, the virtual member, and the resulting market acknowledgement. Every login, every permission change, every limit adjustment is logged the same way. Logs are append-only and can be streamed to your SIEM or compliance archive in real time.

When a regulator asks who placed an order at 14:32:07.124, you have one answer, immediately.

audit.log · stream utc · append-only
2026-05-11T14:32:07.124Z ORDER_SUBMIT user=j.koenig mbr=ALPHA id=8af1c2
2026-05-11T14:32:07.131Z ACK_EPEX id=8af1c2 seq=44012
2026-05-11T14:32:07.892Z ORDER_FILL id=8af1c2 qty=4.0 MW px=82.40
2026-05-11T14:33:11.005Z LIMIT_UPDATE user=admin mbr=ALPHA delta=+50k
2026-05-11T14:33:18.220Z LOGIN user=s.weber ip=10.4.2.7
2026-05-11T14:34:00.001Z ORDER_CANCEL user=j.koenig id=8af1c2
Append-only storage
No edits, no deletions.
Stream to SIEM
Syslog, Kafka, file — your choice.
Per-user attribution
Every action ties back to a real person, not "system".
// 06 · API

Clean REST. Clean gRPC. Documented and stable.

If you've built your strategy, plug it in. Voltnir gives you the market access layer; the trading logic stays yours.

REST covers the obvious surface: place orders, modify, cancel, read the book, list contracts, query positions. Versioned, idempotent where it counts, JSON over HTTPS. Use it from any language. Good for tooling, dashboards, lower-frequency strategies.

gRPC is the same surface plus streaming order book deltas, fills, and session events at wire speed. Use it for latency-sensitive strategies. Protobuf schemas are stable across versions; client stubs ship for Go, Rust, Python, Java, and C++.

No webhooks. No retries with exponential madness. The API does what it says.

curl · POST /orders api · v1
POST /api/v1/orders
{
"member": "ALPHA",
"side": "BUY",
"qty_mw": 4.0,
"px": 82.40,
"contract": "PH-2026-05-11-15",
"type": "LIMIT"
}
 
// → 201 Created id=8af1c2 seq=44012
// 07 · DESK

Don't want to build a UI? Use ours.

Voltnir ships with a full trading desk application. Live order book, order management, position view, cash limits, live metrics. Built on the same API any client would use — battle-tested because we use it ourselves.

desk.voltnir.local / member / ALPHA SESSION 04:21:18 ● LIVE
Order book · PH-15 depth 8
PX €/MWhQTY MWΣ
83.102.018.5
82.903.516.5
82.704.013.0
82.555.09.0
82.504.04.0
Mid 82.45
82.406.06.0
82.303.59.5
82.105.014.5
81.902.016.5
81.754.020.5
New order member ALPHA
PH-2026-05-11-15
4.0MW
82.40€ / MWh
Cash limit✓ within
Position limit✓ within
Throttle window✓ 42 / 60
Position · Cash · PnL live
Net position + 12.0 MW
Realized PnL + €4,820
Unrealized PnL + €312
Cash used €1.84M / 5.00M
Open orders 7
Today · fills 142
Live order book with depth, color-coded by side
One-click order entry with pre-flight limit checks
Cash, position and exposure visible at all times
// 08 · RELIABILITY

Built for the way power markets actually behave.

/ 01
Automatic reconnect.
If the M7 session drops, Voltnir reconnects, re-syncs state, and replays missed sequences before the desk notices.
/ 02
Both M7 versions.
v6 and v7 supported in the same binary. No fork, no parallel deployments.
/ 03
Gap detection.
Every sequence number is verified. Missing messages trigger a state refresh before stale data can affect a trade.
/ 04
Snapshot + delta.
Order book maintained as a snapshot, updated by deltas. Faster than rebuilding from a stream.
/ 05
Throttling aware.
Voltnir knows EPEX's short- and long-window rate limits and never blows through them.
/ 06
No surprises in production.
Same binary in test as in prod. Configuration is the only thing that changes between environments.
"
We are our own customer.
Voltnir runs Voltnir on Voltnir. If something breaks, we feel it before you do.
// 09 · GET ACCESS

Talk to us.

Voltnir is sold by license. Onboarding includes deployment support, M7 credential setup, and a co-located test environment.

[email protected] Amsterdam · London · Cologne Currently onboarding new desks