OpenIRIS: from one institute's system to software used across Europe

We helped the Friedrich Miescher Institute set up the development team that built OpenIRIS, its system for booking and charging for shared research equipment. It has been in continuous service since 2014, is released every week, and is now used by research institutions across Europe, from Institut Curie and Charité to the Universities of Basel and Helsinki.

At a glance

Client
Friedrich Miescher Institute (FMI) and the institutions using OpenIRIS
Sector
Scientific research
System
OpenIRIS: booking, service requests and billing for shared research facilities
In service
Continuously since 2014
Use in the last 12 months
More than 690,000 bookings by more than 20,000 researchers
Scale
Over 550 research facilities and more than 6,000 instruments and services in use
Reach
Researchers from over 200 organisations in 28 countries
Availability
99.99% across eight monitored institution portals, checked around the clock since May 2026
Speed
About 18 million requests a month, answered by the server in 26 milliseconds on average
Release rhythm
One-week sprints, now past sprint 690
Clutch review
5.0 out of 5

The challenge

The Friedrich Miescher Institute in Basel struggled to find a development company that could complete its software projects. It needed a system for its shared research equipment: who can book which instrument, when, under what rules, and who pays for it.

What began as one institute’s system now carries other institutions’ daily operations and billing. A booking that fails, or a charge that goes to the wrong research group, lands on a facility manager’s desk the same morning. The system has to keep working while it changes.

What we did

We sat down with FMI, listened to what the institute needed and advised on how to set up a remote development team. That team built OpenIRIS, and we have developed and supported it ever since.

OpenIRIS handles the whole life of a booking at a research facility: who has access and what training they need, rules on how far ahead and for how long people can book, service requests for work a facility does on a researcher’s behalf, penalties for no-shows, and the charges that go to each research group’s cost centre. Each institution configures it for its own facilities, prices and approval processes, and its users sign in through their own institution’s login.

It is a large system by any measure: a database of around 230 tables shared by two applications, single sign-on for dozens of institutions, background jobs that calculate charges and send notifications, and an integration that lets lab instruments report when they are actually in use.

How it is run day to day

A system that hundreds of facilities rely on every day cannot be stopped for a rebuild, and it cannot be changed carelessly. The routine is the same every week:

  • One-week sprints. Work is planned, built, tested and released in weekly cycles. The sprint counter passed 690 in October 2026.
  • Every change goes through test environments first. A change is deployed to a test environment, then to staging, then to a release candidate that mirrors production, before it reaches the institutions.
  • Automated tests every night. More than 500 automated browser tests run against the test environments each night, alongside automated tests of the new API. A failure is looked at the next morning, before the change moves on.
  • Every change is reviewed. Each change is checked by an automated code review as well as by a person before it is merged.
  • Production is watched continuously. Errors in the browser and on the server are reported to an error-monitoring service and triaged by the team. Performance is monitored on every request, and each institution’s portal is checked automatically every few minutes from outside, so we usually know about a problem before a user reports it.

Moving to modern technology without a big-bang rewrite

The original application is an ASP.NET MVC system on SQL Server. We are moving it to a new ASP.NET Core API one feature at a time. The old and new parts share the same database and sign-in, so each feature can move when it is ready, and be moved back if it needs to be.

Before a feature is switched over, an automated comparison runs the same actions through the old and new versions and checks that they produce the same results. The institutions see steady improvement rather than a disruptive switch-over weekend. It is the same staged approach we take when modernising older business systems for other clients.

The result

OpenIRIS has been in continuous service since 2014. In the 12 months to October 2026 it handled more than 690,000 bookings by more than 20,000 researchers, across over 550 research facilities and more than 6,000 instruments and services.

Since around-the-clock monitoring of each institution’s portal began in May 2026, the eight monitored portals have answered 99.99% of nearly 220,000 checks. The main application serves about 18 million requests a month, and the server answers them in 26 milliseconds on average (53 milliseconds for the slowest 5%).

The institutions using it include Institut Curie, the Paris Brain Institute (ICM), Aix-Marseille University, Gustave Roussy and Sorbonne Université in France; Charité Universitätsmedizin Berlin, the Max Delbrück Center, Freie Universität Berlin, the Berlin Institute of Health, the Max Planck Institute for Multidisciplinary Sciences, TU Darmstadt, Helmholtz Munich and the Institute of Molecular Biology in Germany; the Universities of Basel, Bern and Fribourg and ETH Zurich in Switzerland; the Universities of Helsinki and Turku in Finland; and the Medical University of Graz in Austria.

FMI’s Head of Informatics has reviewed the work on Clutch, where it is rated 5.0 out of 5.

What it means if you are considering us

If your organisation depends on a system that cannot stop, OpenIRIS is the clearest evidence of how we would look after it: small, frequent, tested releases rather than risky big ones; monitoring that finds problems before your users do; and modernisation in stages, with the old system kept running until each part of the new one has proved itself.

“We tried several companies when we started this project and CodeFirst came out way ahead of the others in terms of quality and speed. We are extremely happy with the services received.”
Dean Flanders, Head of Informatics, FMI

Have a system that needs a new home?

Say what it does, what it is built on and what is worrying you. We will reply with what we would look at first and whether we are the right people to help.

Tell us about your system 0800 433 7990 Monday to Friday, 9am to 5pm. A first 20-minute call is free, and we reply to every enquiry within one working day. What happens after you get in touch