Managed delivery
SaaS operations with continuous support instead of a handover-and-leave model.
Operational excellence. Made possible by your train drivers.
Interoperable from day one. Delivered as managed SaaS. Shaped together with drivers until it works in practice.
Coming soon
Release expected Q4 2026
If you are evaluating DAS right now, this is the right time to talk. We are preparing the first public release and aligning early conversations around real operator needs.
UIC 90940
SFERA-compliant foundations
24/7
Managed SaaS delivery model
3
Deployment paths from existing app to full suite
5
Railway markets in rollout scope
Working with
Key figures
SaaS operations with continuous support instead of a handover-and-leave model.
Existing driver app, broader operational suite, or fully managed rollout.
Working toward Germany, France, Belgium, the Netherlands, and the UK.
Roadmap
We are moving from build to proof in real operations. These are the next milestones on the way to our first release.
Our first run on a real train, validating data flow and advisory logic in live conditions rather than in a lab.
A structured trial in day-to-day operation, with driver feedback and measured results shaping the first release.
DAS business case estimator
Operation type
Traction type
Annual cost savings
Best case
High
€6,600,000
Worst case
Low
€230,400
Annual CO2 savings
Best case
High
7,500 tonne
Worst case
Low
480 tonne
Payback period
Best case
Low
3 months
Worst case
High
1.1 years
Who we deliver for
The same platform adapts to different operating patterns, from energy-sensitive freight to dense commuter services and high-speed operations.
Energy-aware advice and resilient planning for long, variable operations.
Precision guidance for tight margins, comfort targets, and performance recovery.
A better operational rhythm across timetable pressure, delays, and platform changes.
Repeatable advice and clearer driver support in dense, high-frequency service.
Technology
Railway data stays close to its source. Interpretation and advisory logic run centrally. The onboard layer stays light enough to update without heavy rollout cycles.
Local source access to operator and infrastructure manager data without moving it out of secure environments.
Central normalisation, enrichment, and advisory logic that adapts when sources or rules change.
A lean onboard experience for drivers, easy to roll out and easy to improve.
Start the collaboration
We start with a focused working session around your data, your operational constraints, and the quickest path to a proof in practice. From there, we shape the right PoC and rollout path together.
Start with the basics, validate data quality, and show value quickly without demanding a full transformation upfront.
We prove the product in live operations, not just in presentations, so decisions are grounded in actual driver and operator experience.
Driver acceptance is part of delivery. We stay involved, iterate with the operator, and build confidence instead of treating rollout as fire-and-forget.
Clarify train type, data availability, interfaces, and operational constraints without overengineering the first phase.
Turn the first setup into something measurable in live practice, with driver feedback and operator priorities built in.
Move from PoC to broader delivery with continuous support, acceptance work, and the right deployment model.