Trading infrastructure
built for speed
and nothing else.

M7 is not a simple API. On v6, you're managing AMQP channels, session state, automatic reconnects, and failover logic across alternate servers — all while the market is live and your positions depend on it. On v7, you're parsing Protobuf messages through compression layers before you've even looked at the orderbook.

Then there's delta sequencing and gap detection — keeping your local orderbook consistent tick by tick, without it silently drifting out of sync the moment your processing falls behind.

Most firms either pay too much for a solution that doesn't fit, or spend engineering budget on infrastructure that isn't their edge — months of work before a single order reaches the market.

And once you've built it, you own it. Every edge case. Every 3am reconnect during peak hours.

There's a better way to be in this market.

Voltnir sits between your trading software and the EPEX Intraday market. You connect to Voltnir over REST or gRPC — and that's the extent of your infrastructure problem.

Behind that interface, Voltnir runs both the v6 AMQP and v7 WebSocket streams simultaneously, manages session state, assembles and maintains your local orderbook, handles delta sequencing, order management, reconnect logic, and failover. The v7 stream alone delivers a 40% latency improvement on orderbook updates — and Voltnir ships with that out of the box.

You don't see any of it. You see the market.

Bring your strategy. The plumbing is done.

If you've built your own trading system, Voltnir gets out of your way. Connect over REST or gRPC, authenticate with a Bearer token, and you have full programmatic access to the EPEX Intraday market.

The API covers everything you need to trade: submit, modify, and cancel orders, query the live orderbook and contracts, stream real-time order and position updates, and pull a full audit trail when you need it. Order types map directly to M7 — regular, block, iceberg, balance, pre-arranged. Permissions are granular, per user, enforced server-side.

For latency-sensitive integrations, the gRPC interface adds live push streams — watch a contract, watch your orders, get pushed on every state change without polling.

Native SDKs available in Python, JavaScript, and Rust — so your team can integrate without touching a .proto file. More languages on the way.

If your system can make an HTTP call, you're connected to EPEX.

Intraday power trading doesn't pause for infrastructure problems. Voltnir is designed around that reality.

The core is written in Rust — compiled to a native binary, no JVM, no garbage collector pausing at the wrong moment. Voltnir processes an orderbook delta in 7 microseconds. The performance is structural, not tuned.

Both M7 streams run simultaneously. v6 for the full message surface, v7 for orderbook data and order execution reports — delivering the 40% latency improvement on orderbook updates that EPEX measured in production. Your API sees neither. It sees a single, stable interface.

Reconnects are automatic. Failover is handled. Gap detection and sequence verification run continuously — if the local orderbook drifts, Voltnir knows before you do. Session state is managed end to end, across both streams, without your system needing to care.

If the system is degraded — exchange disconnect, reconnect in progress, failsafe restart — order submissions and modifications are bounced immediately with a clear error. Cancellations are always accepted. You can always get out.

Stream health, latency, and tick processing time are visible in real time through the system state panel — so you always know the infrastructure is alive, not just assumed to be.

And the most honest signal we can offer: we trade on this ourselves.