Skip to main content
← Back to journal

Published on May 4, 2026

Formula Student: IT at the Valais Racing Team

A look back at two seasons building the IT of a Formula Student team, from the inherited ERP to a team of six.

Formula Student: IT at the Valais Racing Team

Valais Racing Team designs and builds a racing single-seater every year, with students from HES-SO Valais, to compete in Formula Student. I joined in October 2024. This article covers the side that took up most of my time, the IT.

Valais Racing Team, in a nutshell

Formula Student is an international student engineering competition. Each team designs, builds and races its own single-seater, and it is judged as much on engineering, costs and the defence of its project as on its lap times. So it is not only a matter of speed: a good part of the score is won at the desk, not just on the track.

A team is organised into two main divisions. The technical side brings together the mechanical and electrical teams, the ones that build the car. The business side handles marketing, sponsors and events. Above them, the committee runs the association. VRT is around fifty people, one season a year, and competitions that last a week. IT, for its part, did not really have a place in that chart when I arrived.

An IT function that did not exist

When I joined, IT did not exist as an entity. There was code, there were tools, there was an Odoo inherited from previous cohorts, but no overall coherence and no clear way of doing things. Everything moved in fits and starts, depending on who had the time and the appetite that week.

By default, IT fell under the business side. Its priorities were therefore set by sponsors, events and the committee's agenda, not by technical debt or by handover between seasons. We negotiated with the board for IT to become a team in its own right. Not to plant a flag, but because the stakes of an internal information system cannot be planned like a communications campaign. The discussion took a few weeks; once settled, we had our own lane and real expectations to meet. In a student association, things move fast, but you often have to make them move yourself.

Rebuilding the ERP

The first real project was the ERP. VRT ran on Odoo, with bits of custom development on top. Every season meant reconfiguring, patching things back together, and that work ate up time we did not have. The conclusion was clear: this Odoo would not be saved, better to start from a blank page.

I took a few weeks to assess the alternatives, against three criteria in this order: what the tool already does without coding, ease of implementation, and maintenance for whoever would inherit the code next. Dolibarr passed the filter: PHP and MySQL, a very simple module model, a large French-speaking community, concrete documentation. Less flashy than Odoo, but more readable for anyone opening our code two seasons later.

We forked Dolibarr rather than using the standard version. It was a commitment: each custom module becomes a small maintenance pact, and integrating upstream updates falls on us at every major release. But that was the price for adding deep modules, such as multiple signatures, automatic budget deductions or the Keycloak integration, without walking a tightrope with a public API. With two years of hindsight, I would make the same choice.

What the ERP does today

Several custom modules form the heart of the fork in production. The main ones:

  • Budget: tracking of financial commitments along three axes (team, car system and subsystem, season), with automatic deduction on every approved order. The treasurer sees the state of each envelope in real time.
  • Orders: four-step approval (team lead, CFO, CTO, CEO), email notifications at each step, output as an electronically signed PDF. It is the most used module.
  • Member: member management with a sign-up form on the site. On approval, the member is created in Keycloak, so propagated across the whole ecosystem at once, and receives a welcome email with their access.
  • Emergency: active during competitions. Participants on site can access the others' emergency information (family contact, allergies, relevant medical data), after signing a usage charter, because this data is sensitive.
  • Forms: a generic engine for competition registrations, requests from the divisions and feedback surveys. Custom fields, multi-step workflows, email alerts, PDF generation.

Other smaller building blocks revolve around these. Each answers a need a plain Dolibarr did not cover: that is precisely what justified the fork.

Around the ERP

An ERP on its own does not cover everything a team needs to function, so the ecosystem grew. Keycloak now serves as the central identity manager. Dolibarr and Nextcloud are connected to it through single sign-on, which means a member has only one account to manage, and access is cut in a single place when someone leaves. For an association whose membership turns over every year, that genuinely changes things.

Nextcloud hosts the team calendar (competitions, test days, technical milestones) and the photos taken during events. The calendar surfaces in Dolibarr through a widget, so a member finds their schedule in the same place as their open orders. The whole thing is hosted at Infomaniak, in Switzerland. It is not perfect, there are seams to smooth out and automations still to write, but the whole is coherent and entirely under our control.

Handing over

We were two at the start. At one point, I carried the IT alone. In 2026, we are six, with the arrival of the first-years. For me, it is a turning point: moving from holding the setup at arm's length to passing on the baton.

They are not touching the Dolibarr fork yet. They work first on other building blocks: VRT's upcoming mobile app, planned for the App Store and the Play Store, and the new website, coupled with the ERP to display members, whose groundwork I did before delegating parts of it to them. The idea is for them to find their footing on these areas before stepping into the fork. PHP is not the first language a first-year student masters, and Dolibarr's module model has its quirks. We will move through small, isolated projects, pair programming, and plenty of internal documentation. It is not the fastest way to ship, but it is the only one that lets the team survive my departure.

And after that

The current project is to package everything we have built, the Dolibarr fork and its modules, the Keycloak integration, the Nextcloud connection, into something that could serve other Formula Student teams. The model is still to be decided (open source, SaaS, paid support), but the idea holds: the needs of one team resemble those of another closely enough for our work to be reusable elsewhere.

For me, 2026 is the last season as an active member. After that, I move into a mentor role: following the project from a distance, lending a hand when things get stuck, passing on what I can. In theory only, because I already know I will come back to get my hands dirty as soon as the team needs it.

Two seasons at VRT are not only an ERP and servers. They are also another world, alongside my days as a developer. Test-day weekends, week-long competitions spent camping on three hours of sleep a night, woken at six by Germans blasting techno across the whole campsite, people met from all over Europe, evenings spent talking cars, code, sponsors or personal life around the same table. For someone who spends most of his time in front of a screen, it is a rare balance, and I did not measure its true worth right away.

What I take away from these two seasons is that the right tool is not the one that shines the most. It is the one the next person will be able to open without fear. And that half a project's value does not live in the code, but in the people you meet along the way.