Rail companies
Compare route options for a selected corridor. Test whether passengers can understand connections, transfers and modelled emissions, and identify missing information with your product team.
For rail & infrastructure companies
Build the foundation. Start with one corridor.
Help shape the infrastructure for sustainable travel. Test how passengers understand a rail journey, or how well your station and corridor data support it. In twelve weeks, we build one agreed prototype and assess it against shared reference cases.
Seeking pilot agreements by 31 December 2026 · Production target: early 2027, subject to readiness
Farleda has a preview of journey planning, emissions comparison and signed calculation records. Partner integrations and reporting are developed within the agreed pilot scope. The consumer beta is planned for 31 October–31 December 2026; the paid partner pilot is a separate agreement.
Two starting points
Choose the question your team needs answered.
Each pilot focuses on one corridor, station cluster or data use case. No network-wide rollout is needed to start.
Infrastructure companies
Examine a defined set of station, interchange or corridor data. Use reference journeys to expose coverage gaps, unclear transfers and limitations in how the data is presented.
Pilot scope
One outcome, agreed in writing.
A planning prototype
A limited planner view or integration for the selected corridor. Branding, interfaces and test group are specified before work starts.
Rail use case
A data-quality assessment
An agreed dataset, reference journeys and documented discrepancies. We establish licences, access and update frequency before integration.
Infrastructure use case
A decision report
Results against the agreed criteria, known limitations and an estimate for the next step. Measured test results and modelled emissions stay clearly separated.
Both pilot types
Included work, exclusions, data rights, responsibilities and price form the written statement of work. Production SLAs and custom integrations require explicit agreement.
Twelve weeks
From a shared question to a go / no-go decision.
Weeks 1–2
Define & baseline
Confirm scope, data rights and the reference cases. Agree measurable acceptance criteria, responsibilities and the review schedule.
Weeks 3–10
Build & test
Implement the agreed prototype, run the reference cases and collect structured feedback. Review progress in short regular check-ins.
Weeks 11–12
Review & decide
Document results and gaps. Decide together whether to stop, extend or prepare a separate production agreement.
After a scoping conversation, we quote the twelve-week pilot with included work, exclusions, milestones and payment terms. Consumer beta access is free; partner development is separately priced. There is no automatic annual licence or guaranteed credit. See the pricing logic →
Pilot demos
Explore an illustrative corridor report.
The demo dashboards use synthetic data to illustrate possible report layouts. They are not pilot results, reference customers or evidence of modal shift. Your pilot may need a different output.
Browse the corridor demosSample data · numbers are illustrative
Documents
For your inbox, procurement and legal.
Product summaries and working templates for an initial review. Templates are not signed agreements or a legal release.
Farleda fact sheetProduct, methodology and pilot model at a glance — made for forwarding inside your organisation.Fact sheet (German)The same fact sheet in German — for Austrian and German stakeholders.EmpCo guide for destinationsWhat Directive (EU) 2024/825 means for destination marketing — and which green claims survive it.Pilot SoW templateThe statement-of-work skeleton we scope pilots against — read it before the first call.
The EmpCo guide and the SoW template are currently available in German only — English versions on request.
Technical foundation and verification limits
Journey planning preview. The website shows actual preview screens of European route planning, comparisons and a trip overview. They are dated examples, not a guarantee of coverage for your network.
Published calculation approach. Sources, assumptions and limits are documented. A corridor pilot can compare model outputs with reference cases your team agrees in advance.
Signed calculation records. The current Passport records a planned journey and its calculation. Signature verification checks integrity through Farleda; it does not establish that a journey happened or emissions were avoided.
Verification checks whether the current record was signed by Farleda and has remained unchanged. The current HMAC check runs on Farleda’s server. Completed travel, independently verified measurements and causally avoided emissions need additional evidence. Public-key verification is a development target.
Scope a pilot
Tell us which question matters.
A short description is enough: organisation, corridor or dataset, and the outcome you need. The first conversation is non-binding; no purchase is made by submitting this form.
Let’s talk.
Email us about your organisation, your idea or your interest in Farleda. We will discuss the next steps together.
partners@farleda.euThe link opens your email app. A message does not subscribe you to a newsletter or create an app account.
FAQ
What procurement, legal and IT ask first.
What do we need to bring?
A named product or specialist contact, one use case and permission to use the required data. We agree the data inventory, licences and any IT involvement during scoping. An initial conversation needs no customer data.
How do we judge whether it worked?
Agree reference journeys and acceptance criteria first: for example route coverage, data completeness, understandable comparisons or successful completion of a planning task. Thresholds depend on your starting data; no fixed improvement or modal-shift result is promised.
Does the pilot include production operation?
The pilot is a limited test engagement. A production rollout, service levels, support, integrations and ongoing costs require a separate readiness review and agreement. Early 2027 is the target, not a contractual promise.
How are procurement and data protection handled?
Your procurement team assesses the written scope and price under your own rules. Data roles, access, retention and any required processing agreement must be settled before affected data is exchanged. The public provider inventory is available on the trust pages.
What happens at the end?
There is no automatic licence commitment. Export, deletion, prototype access and record-verification duration are specified in the pilot agreement. We assess follow-on work only after reviewing the results.
Who contracts with us?
Currently Stoicera Group, operated by Raphael Lugmayr & Sebastian Kern GesbR. A future Farleda FlexCo and a separate nonprofit association are planned, not current contracting entities. A later transfer requires the applicable contractual arrangements.
Horizon Europe · Research & collaboration
Build the next chapter of European mobility together.
We plan to apply for Horizon Europe funding. We are looking for partners to develop a credible research approach, suitable pilot cases and a shared project proposal with us.
Explore the research initiativePlanned application. The call and consortium are still to be selected; no proposal has been submitted and no EU funding has been awarded.
