Railway Software Engineering
MetaProject provides software engineering for railway and transport product companies: onboard systems, signalling and traffic control, operations and planning software, and infrastructure inspection and analytics. Our engineers work inside your QMS and tools. You keep the product and the safety case; we deliver the engineering and the evidence behind it.
Demand and regulation are both growing faster than most rail engineering teams. New operators, retrofits and tenders keep adding work to the same roadmap, and the EU Cyber Resilience Act now applies to products already in the field.
Who we work with
What makes rail software different
What we work on
Three ways to add capacity
Dedicated product squad
3–10 engineers who join your roadmap and work in your tools under your management. Operational in 1–3 months; take the team over after 12 months.
Capability on demand
1–5 senior specialists for a defined gap, such as RAMS analysis, a compliance gap assessment, DevSecOps or verification set-up. They hand over and step out.
R&D hub
A remote unit of 5+ engineers with its own lead, working to your governance and QMS across several product streams.
All three models run inside your QMS and compliance framework, and you can switch between them as your needs change. How the handover works: Delivery as Training and Exit by Design.
Why rail teams work with us
Case: scaling the engineering behind real-time rail optimisation
When to bring us in
Railway software FAQ
Yes. Our engineers work inside your QMS and produce the lifecycle evidence your process requires: requirements, architecture and design specifications, test specifications and verification reports for each V-model phase. You keep the Manufacturer role and the safety case; we deliver the engineering and the evidence.
A fixed-scope, fixed-price review of a product against the EU Cyber Resilience Act: the vulnerability reporting duties that apply since September 2026 and the essential requirements that apply from December 2027. You get the gaps, a scoped solution and a prioritised remediation plan.
Individual specialists join in weeks. A dedicated squad of 3–10 engineers is usually operational in one to three months, including onboarding into your QMS, tools and domain.
Yes. A dedicated squad can be bought out or taken over in full after 12 months. In capability-on-demand assignments, findings, artefacts and know-how are handed into your documentation and team before the expert steps out.
You do. Engineers work in your systems, environments and repositories. In the R&D hub model they share patterns through our Centre of Excellence, while your IP and data stay yours.
Bring your backlog to a 60-minute team planning session: we propose a team composition and send matching CVs within a week. Or start with a CRA readiness assessment at a fixed scope and price.