Getting started

You do not need anyone else to start.

Shared platforms usually ask you to wait — for a counterparty, a consortium, a standards programme. RailExchange is useful to a single participant on day one, because your own movements are already scattered across your own systems.

Day one, alone

Your movements in one place, across the systems you already run. Value before anyone else joins.

Then share a view

Send a live view to a customer or counterparty. No account for them, no integration, no negotiation.

They join when ready

When the other side connects its own data, the handoff closes and both sides gain at once.

Getting your data in

Bring your data as it is.

railML is where we are heading. It is not the price of entry. We ingest what your systems already produce today, and the mapping is our work rather than a project for your team.

Send what you have

Flat files, TMS exports, GPS feeds, EDI messages or an API — whatever comes out of your systems today.

We do the mapping

Normalisation into the RailExchange model happens on our side, not yours.

Converge over time

As parties adopt the common schema, richer functions unlock — attribution, prediction, cross-network reporting.

Outbound in your format

A client adapter delivers data back the way your systems already expect it.

Standards-based by design, not standards-gated on entry

What it takes

Weeks, not quarters.

Week 1
Send an extract
One data extract, in whatever format it comes out of your systems today.
Week 2
See your movements
Your operation is live in RailExchange. Value lands before any counterparty is involved.
Week 3
Share a live view
Give a customer or counterparty a view of the movements they care about.
Ongoing
Coverage compounds
Each party that connects closes another handoff. Nobody has to go first alone.

No procurement. No integration project. No consortium to convene. You are not evaluating a trial — you are using a service, and you keep using it for as long as it is worth having.

What good looks like

How you will know it is working.

Measured against your own baseline

Movements visible without manual entry
Time from an event happening to it being visible
Status enquiries answered without a phone call

Judged

The operations team opens it without being asked to
At least one counterparty asks for access of their own
You would put it in front of a customer

The last one is the one that matters. A tool people will show to a customer is a tool that works.

Commercial model

Priced like infrastructure, not like a pilot.

There is no trial, no evaluation window and no decision date. You subscribe from the first month at the smallest tier, and you stay at that tier until you want more.

What you pay for

Connected parties and data feeds

Not seats, not users, not messages. The price moves when your coverage moves, and not otherwise.

How it is quoted

Published tiers

The same price for the same tier for everyone. No bespoke negotiation.

Term

Monthly

Cancel with a month's notice. You keep your data and the mapping we built for you.

As others join

Your price holds

A counterparty connecting makes your coverage better without making your invoice bigger.

The ask

One data extract, and one person to point at it.

That is the whole ask. No procurement, no integration project, and no lock-in — the subscription is monthly and you can stop whenever it stops earning its place.

Book a session

Next step: A short session to look at one of your existing data extracts together.
What we need: Someone in operations who can send a file and answer questions about it.
Timing: Live inside two weeks of that session.