Some love it and some hate it: the electronic lab journal (ELN). Already a decade ago, the prediction was that in 10 years the paper lab notebook would be a thing of the past. In reality, the majority of academic labs at our university are still using paper in 2022. The transition has not been helped by literally hundreds of commercial offerings that are all mutually incompatible. We started to experiment with ELNs in 2013, testing a few commercial and open source solutions.

In 2015, we settled on eLabFTW, an open-source project with the main development happening at the Institute Curie in Paris, France. It's a web application built with PHP and MySQL (there is also a peer-reviewed publication describing it:

Deployment of eLabFTW for teaching at the University of Helsinki

With the recent update to version 4.3, the final hurdle for the large-scale deployment of eLabFTW has been taken. Everybody with a account can now log into the system with university account credentials. This makes the onboarding of many new users much easier. I am planning to use the system for our new course Recombinant DNA technology and genetic engineering. At the moment, the server is only reachable from inside the university network. If you want to use it from home, you need to use a VPN. Over the years we have been accruing about 25 users, and it will be interesting to see how the system performs when the user numbers will double or quadruple. The system runs in a docker container on an Ubuntu 20.04 LTS virtual server, which we, unfortunately, cannot upgrade or extend without additional financial support. So if you are interested to use an ELN, secure your spot today by logging into, using the "Login through your institution" option on the bottom. You will have the option to choose a team. The team administrator needs to approve you before you can use the system. If you cannot find your lab among the teams, it means that you are the first user from your lab using this system. In that case, you should choose the team "Helsinki University" and contact me via email (, because I will need to register a new team for your lab, and you will be the administrator of this new team.

Access for visitors

If you do not have a University of Helsinki account, you can still use the system if you are inside the Helsinki University Eduroam network, but you will need to use the "Register now" link, and your account needs to be approved by a system administrator.

Running it on your local machine

The system requirements of eLabFTW are fairly low, and your laptop is likely to have no problems running a local copy of the Docker container. While installing eLabFTW on a recent Windows or macOS computer is possible, it is somehow counter-productive as it does not provide network accessibility and team functionality. Even if you don't need any of that, I would suggest that you repurpose an old desktop computer for this task and run it on a regular Linux server installation. I am happy to answer all possible questions that you might have (from a system administrator's and end-user's perspective).

General advice for implementing an ELN solution

There is a review article from nature Protocols that discusses issues of ELN implementation for life science labs:  They have also done some analysis of the existing solutions, but some of their writings (especially about the commercial solutions) are a bit off. They e.g. count Textco's Gene Inspector as an ELN software, while it is nothing like that. It's a dedicated software suite for the analysis of gene and protein sequences packaged together with a text editor. Hence, including it as the longest-running commercial offering (25 years) does screw the statistics about the average lifetime of ELN software towards longer lifetimes of commercial offerings. Since we did use the Gene Inspector software, I know what I am talking about. It cannot even be called functional anymore. It's on life support and performs very poorly on contemporary hardware and hasn't been updated for about 5 years now. Also, their webpage seems to be at least partially dysfunctional, I just tried to download the "newest" update from 2017 to see whether anything has changed, but without success...