eLabFTW ELN overview

By Thibaut Desseignes, founder and editor · Last verified · 27 independent and 29 vendor sources

Verdict. eLabFTW is a free, open-source (AGPL-3.0) electronic lab notebook with experiment templates, a resource database with booking and inventory, RFC 3161 timestamps, Ed25519 signatures and an audit log. Institutions run it on their own servers or on Deltablot's hosting, sold at published yearly prices. It suits universities and public research institutes, which use it across Europe as one notebook for many groups. It is less suited to GxP laboratories that need a vendor validation package.

eLabFTW key facts

PriceEvery feature is in the open-source release. Deltablot sells PRO Support for self-hosted instances at 3,000 EUR a year and managed hosting from 3,200 EUR a year (32 active users) to 8,700 EUR (SecNumCloud plan); its page does not say whether prices include VAT.
HostingSelf-hosting runs on GNU/Linux in containers. Deltablot's hosting: Paris for Europe (Scaleway, or 3DS Outscale on the SecNumCloud plan), DigitalOcean in New York, San Francisco or Toronto, Vultr in Asia, Melbourne and Latin America; backups copied to Zurich.
ComplianceIn a 2022 GitHub discussion, the maintainer answered yes to a question on Part 11 compliance, pointing to trusted timestamping; no dedicated Part 11 page is published. Deltablot reports Cyber Essentials certification; the ISO 27001 and HDS listed on its price cards certify its hosting providers' data centres.
Main limitsSelf-hosting needs a Linux administrator and, from version 6, MySQL 8.4 or later. Archived experiments drop out of default searches and exports. RWTH Aachen states that eLabFTW is not software to process or analyse experimental data.
Leaving eLabFTWData exports and imports in the .eln (RO-Crate) format. Deltablot hosting customers can move to an internal instance with help formatting their data; when a hosting plan is cancelled, the data and all backups are deleted.
Who uses itUniversities in Germany (RWTH Aachen, Heidelberg, Münster, Hamburg, TU Darmstadt and six others), France (Lorraine, Montpellier) and Austria (Innsbruck), and INRAE; pilots at Kyoto and CIIMAR Porto. CNRS awarded a 2023 framework contract for an eLabFTW-based ELN.

eLabFTW assessment

Editorial reading of documented evidence, not a hands-on test. See how we assess.

Not assessed yet, for lack of independent material: Support.

A good fit for

  • Universities and research institutes that want to run their notebook on their own servers, as Münster, Würzburg, Kiel and Heidelberg do
  • Institutions that prefer managed hosting at a published yearly price, from 32 to about 1,024 active users, including a plan on SecNumCloud-qualified hosting in Paris
  • Research groups that want timestamped, signed records without a licence fee: RFC 3161 timestamping and Ed25519 signatures are part of the free software

Less suited to

  • GxP laboratories that need a vendor validation package or a documented Part 11 assessment
  • Organisations without a Linux administrator that do not want to pay for hosting
  • Biology teams that need a structured registry of sequences or plasmids, or plate management: resources are a generic item database

Strengths

  • Free AGPL-3.0 software with no feature reserved for paying customers
  • Self-hosting practised by universities: Münster, Würzburg, Kiel, Heidelberg, LMU Munich and Heinrich Heine University Düsseldorf run it on their own infrastructure
  • Support, training and every hosting plan carry a published price
  • Documented traceability: RFC 3161 timestamps from a choice of authorities, Bloxberg blockchain proofs, Ed25519 signatures with a chosen meaning and an immutable audit log
  • Exit route documented both ways: .eln (RO-Crate) import and export, free migration to Deltablot hosting and help moving back to an internal instance

Limitations

  • No vendor validation package or dedicated Part 11 page is published for GxP validation teams
  • Deltablot's own stated certification is Cyber Essentials; the ISO 27001, SOC 2 and HDS certifications listed for its hosting plans cover its providers' data centres
  • Self-hosting is supported on GNU/Linux in containers, and version 6 brought breaking changes (MySQL 8.4 or later, container run as a user)

eLabFTW pricing and editions

From 3,000 EUR a year, PRO Support for a self-hosted instance. The software is free under AGPL-3.0. Deltablot publishes yearly prices for PRO Support and each PRO Hosting plan, and a per-session training price, without saying whether they include VAT. Custom development has no published price, and neither does the central-purchasing offer Deltablot mentions for French higher education and research.

PlanForPriceWhat it includes
Open source, self-hosted organisations with their own system administrator Free The full AGPL-3.0 software with every feature, installed, configured and maintained by the customer's own system administrator on a GNU/Linux server in containers; free support through GitHub issues. [32]
PRO Support self-hosted (on-premise) instances 3,000 EUR per year Email, virtual-meeting and level 2 and 3 support with priority assistance, a 90-minute user training webinar, 20% off custom development, eIDAS-qualified timestamping and access to a training instance. [28]
PRO Hosting 32 teams of up to 32 active users 3,200 EUR per year Managed instance limited to 32 active users, 320 GB+ storage, all features, eIDAS-qualified timestamping, secure GNU/Linux infrastructure and PRO Support, hosted in Europe, the USA or Asia by location; all plans add a custom domain, geo-redundant encrypted backups, unlimited updates and ransomware protection. [28]
PRO Hosting Plus up to about 128 active users 4,985 EUR per year Managed instance for about 128 active users and 500 GB+ storage, with the same features, eIDAS-qualified timestamping, infrastructure, PRO Support and regional hosting as PRO Hosting 32, plus the services included in all plans. [28]
PRO Hosting Universe large institutions, up to about 1,024 active users 7,900 EUR per year Managed instance for about 1,024 active users and 1 TB+ storage, with the same features, timestamping, infrastructure, PRO Support and regional hosting as the other plans; presented as the all-included offer for entire research centres or universities. [28]
PRO Hosting SecNumCloud organisations requiring a French sovereign cloud, up to about 1,024 active users 8,700 EUR per year Managed instance for about 1,024 active users and 1 TB+ storage, hosted exclusively in Paris with the SecNumCloud security visa and encryption at rest, with PRO Support and eIDAS-qualified timestamping; presented as the plan for sensitive research labs. [28]
Training session any customer 470 EUR per session A 90-minute webinar to get started with eLabFTW and adapt it to the lab's workflow, in French, German or English, with access to the recording. [28]
Custom development any customer On quote Custom features accepted if they fit the project's long-term vision; the result can be shared openly with the whole community. Price not published. [28]

Prices in public records

BuyerProductScopePeriodAmount
CNRS, Délégation Midi-Pyrénées ELN based on open-source eLabFTW (implementation, evolutions, maintenance, partial operation) Services framework agreement (SaaS and on-premise modes), no lots, one tender received; awarded to a group of two SMEs, easter eggs (Paris) and carpi (Villejuif); the notice does not name Deltablot Concluded 23 January 2023; duration not stated in the notice (the 900,000 EUR estimate covers all renewals) 1,500,000.00 EUR total value excluding VAT (the description estimates the service at 900,000 EUR over its term, all renewals included) [1]

Conditions and limits

1 more conditions

eLabFTW compliance and security

Vendor-documented: a dedicated vendor page or documentation article describes it. Vendor-stated: the vendor states it without describing it in detail. Not mentioned: found neither in the vendor's material nor in independent sources.

StandardEvidenceWhat we found
21 CFR Part 11 Vendor-stated In a 2022 GitHub discussion, the maintainer, Deltablot's founder, answered yes to a question on Part 11 compliance, pointing to the trusted timestamping feature. The documentation describes the audit log, revisions, RFC 3161 timestamps and Ed25519 signatures; no dedicated Part 11 page or validation package is published. [55]
EU GMP Annex 11 Not mentioned
GAMP 5 Not mentioned
ISO/IEC 27001 Not mentioned
SOC 2 Not mentioned
GDPR Not mentioned
HIPAA Not mentioned
ISO/IEC 17025 Not mentioned
Security and hosting details (13)

What eLabFTW is

eLabFTW is an electronic lab notebook published under the AGPL-3.0 licence, with its code on GitHub. Deltablot, a single-shareholder company based in Villejuif, France, which says Nicolas Carpi founded it in 2019, maintains the project and holds the eLabFTW trademark. Deltablot states that no feature sits behind a paywall, so the version a university installs at no cost is the whole product. What Deltablot sells is everything around the software: managed hosting, support for self-hosted instances, training sessions and custom development, which it takes on provided the work fits the project’s long-term vision, with a result that can be shared with the whole community.

The notebook is organised around experiments with reusable templates, a generic database of resources (plasmids, compounds, antibodies, cell lines), an instance-wide compounds database fed from PubChem with a structure editor and substructure search, a booking calendar for resources, and an inventory of storage locations and containers. One instance can host several teams, and users choose who can see and edit each entry.

How it is sold and hosted

Self-hosting carries no licence fee, and the work falls to the institution’s own system administrator. Deltablot’s documentation limits supported production installs to GNU/Linux in containers, and expects an administrator who is comfortable with the command line, updates and backups. Free support runs through GitHub issues. PRO Support adds email, virtual-meeting and level 2 and 3 support, a user training webinar and eIDAS-qualified timestamping. Deltablot warns that self-hosted instances left without updates may miss security patches.

Managed hosting is priced in bands of active users, defined as accounts that connect at least once in a month, from 32 users to about 1,024, with a SecNumCloud plan of the same top size on servers in Paris with encryption at rest. Every hosting plan includes PRO Support and unlimited updates. Moving an existing instance onto Deltablot’s hosting costs nothing extra, and customers who leave can host their instance internally, with help formatting their data. When a plan is cancelled, the hosted data and all backups are deleted, so exporting comes before cancelling.

For a research department, this makes the budget question concrete: a known yearly figure from Deltablot on one side, server and staff time on the other.

What changed in 2026

Version 5.6, announced on 1 July 2026, added Research Organization Registry identifiers, branding improvements and better compound imports. On 11 July 2026 the project published security advisories on GitHub: the first page of the list shows ten dated that day, one rated high because archived team members kept full API access. The releases page lists version 5.6.6 on 11 July as well.

Deltablot announced version 6.0 on 11 August 2026 as a major release with many breaking changes for system administrators: the container must run as a user, and MySQL must be at least version 8.4. The release adds login rate limiting and a hardened container image, and the notes of the 6.0.0 release on GitHub list further security fixes, among them hashed token storage and a fix for an authorisation bypass when transferring entries across teams. Six patch releases followed; the notes of the latest, 6.0.6, call it non-critical. For a self-hosting institution, moving to version 6 is a planned upgrade rather than a routine update.

What the public record shows

The independent record comes almost entirely from public research, and the institutions describe their own services. Three patterns stand out.

The largest group runs eLabFTW itself. Of the eleven German universities that describe their own service, the pages from Münster, Würzburg, Kiel, Heidelberg, LMU Munich and Heinrich Heine University Düsseldorf say the software runs on university servers or as a central instance; in Austria, Innsbruck sets up one instance per institute. Practices differ: Münster’s service is free to all members, Heidelberg charges teams under its own price sheet after a six-month free trial, and Düsseldorf keeps a separate instance for teaching.

Others buy hosting. The University of Montpellier and RWTH Aachen both name Deltablot as the provider of their software-as-a-service instance, and Montpellier’s data sits with 3DS Outscale in the Paris region. INRAE runs an institute-wide offer as SaaS on SecNumCloud-qualified hosting, paid by the institute and mandatory for units that handle sensitive data. At the CNRS, a 2023 framework agreement covers an ELN based on open-source eLabFTW in SaaS and on-premise modes; the notice does not name Deltablot.

The third pattern is evaluation before rollout. Université de Lorraine chose eLabFTW after a preliminary study of available tools, and 670 people had created an account, sandbox included, one year after its April 2023 launch. University Medicine Halle selected it against a detailed criteria catalogue and ran an eight-month pilot in 15 laboratories; TU Darmstadt moved from test to production in March 2026, and Kyoto University and CIIMAR in Porto launched pilots in July 2025 and February 2026.

The evaluations report strengths and costs. Halle found that eLabFTW met essential functional and technical requirements and proved adaptable across disciplines, and Lorraine’s survey reports broadly very positive feedback. Lorraine’s report adds that the tool’s flexibility can make it complex to learn for some, and respondents asked for a better search engine; Halle reported diverse usage patterns, integration issues and varying acceptance; and a small INRAE unit says it needs local administrators and support for some users. Chemists at Lorraine asked in 2024 for structure and substructure search; the current documentation describes a substructure search in the compounds database, added in version 5.2.

Several institutions also limit what goes into their instance, from patient and health data (RWTH, INRAE) and protected personal data (Marburg) to large volumes of raw data (Montpellier). Each institution sets these rules for its own deployment.

What users report

G2 lists four reviews of eLabFTW, from November 2022 to May 2023, all four marked incentivized by G2, on a profile that Deltablot has not claimed and that names t413.com as the seller. Two call it easy to use, two value working with colleagues in it, and no complaint recurs. The fuller feedback comes from the Lorraine survey and the Halle pilot described above.

Compliance and security in practice

The software and the hosting service need to be read separately. In the software, the documentation describes the controls a regulated lab looks for: a changelog of changes outside the main text, revisions of the main text that can be compared and restored, an immutable audit log of sensitive actions, RFC 3161 timestamps from a choice of authorities including eIDAS-qualified ones, and Ed25519 signatures protected by a passphrase, each with a chosen meaning such as review or approval. The layer around these controls is not public: no validation package is published for a GMP team to build on, and Part 11 is addressed in a 2022 GitHub discussion, where the maintainer answered yes and pointed to trusted timestamping.

On the hosting side, Deltablot states that it holds Cyber Essentials certification. The ISO 27001, HDS and ISO 50001 certifications listed on its hosting plans, and the SOC 2 Type 2 listed for the Tokyo data centre used for Asian customers, certify its hosting providers’ data centres, as its compliance page explains. A self-hosting university takes both layers on itself; Heidelberg, for example, states that all data is encrypted by eLabFTW and stays on university servers.

eLabFTW capabilities

CapabilityEvidenceWhat the source describes
API Vendor-documented An HTTP API (v2) reads and writes data with a personal API key created with a name and an access level; a Python library is provided. [47]
Chemical drawing Vendor-documented A chemical structure editor in the Tools menu (since version 5.2) draws molecules and runs substructure searches on the instance-wide compounds database. [42]
Collaboration Vendor-documented Users with read access can comment on experiments and resources they cannot edit, and entries can be linked to any number of other experiments or resources. [43]
E-signature Vendor-documented Three signature types: a handwritten-style block in PDF exports, simple signatures (checkbox, comment, lock), and an advanced Ed25519 signature with a passphrase-protected key and a chosen meaning such as Review or Approval. [36]
Experiment templates Vendor-documented Templates act as skeletons for frequent experiments, with separate permissions for the template and for the experiments created from it, and can be pinned for quick creation. [44]
Inventory Vendor-documented Storage locations form a hierarchy with buildings at the root; containers record the quantity and unit stored, and the list of stored containers exports as CSV. [41]
All 16 other features
FeatureEvidenceWhat the source describes
Trusted timestamping (RFC 3161) Vendor-documented Entries are timestamped by an RFC 3161 authority: DFN.de (free academic default), Universign or Evidency (eIDAS qualified), Digicert, Sectigo, GlobalSign or a custom one; only the data hash is sent. [36]
Blockchain timestamping (Bloxberg) Vendor-documented An entry's data can be timestamped in the Bloxberg consortium blockchain; the proof (JSON file and a certifying PDF) is stored in an immutable ZIP archive attached to the entry. [36]
Changelog, revisions and immutable audit log Vendor-documented A changelog tracks all changes except the main text; revisions of the main text can be compared or restored; an immutable audit log of sensitive actions sits in the Sysconfig panel. [36]
Soft deletion and restore Vendor-documented Deleted entries change state but remain in the database and can be restored by opening them directly. [36]
Entry locking Vendor-documented An entry can be locked against further editing; only the user who locked it or an Admin can unlock it. [43]
Compounds database with PubChem import Vendor-documented An instance-wide compounds database holds CAS numbers, SMILES or InChI and hazard data, imports by PubChem CID or CAS number, and links compounds to experiments and resources. [42]
Equipment and resource booking Vendor-documented Resources can be booked in a scheduler calendar, with a booking permission that defaults to the entry's visibility; cancellations can notify users. [45]
.eln import and export (RO-Crate) Vendor-documented Data exports and imports in the .eln format, based on RO-Crate, including .eln archives produced by other ELNs that follow the specification. [40]
CSV import Vendor-documented Entries can be imported from CSV files; command-line import is recommended for large files such as a full team export. [39]
Offline desktop application Vendor-documented A desktop application for Windows, macOS and Linux records data without Internet access and pushes entries to an instance later, using its URL and an API key. [49]
Single sign-on with SAML or LDAP Vendor-documented Four authentication mechanisms: local accounts, SAML with one or several identity providers, LDAP, and headers set by the institution's own middleware. [46]
S3-compatible file storage Vendor-documented Uploaded files are stored in a local folder by default, or in an S3-compatible bucket service. [46]
Persistent identifiers and ORCID Vendor-documented Each experiment or resource gets an immutable elabid; ROR organisation identifiers appear in exports, and ORCID can be filled from the SAML response since version 5.6. [40]
Teams and per-entry permissions Vendor-stated One instance hosts several teams; users choose who can see and edit each entry, and Team Groups refine permissions. [32]
Accessibility (WCAG 2.1) Vendor-stated The vendor states that eLabFTW complies with the Web Content Accessibility Guidelines 2.1. [32]
Responsive web interface Vendor-stated Runs in any modern browser on desktop, tablet or smartphone; no native mobile app is described. [32]

Limits stated in the vendor's own documentation

What independent sources say about eLabFTW

Independent coverage: Moderate. Twenty-two independent publishers back this page: sixteen universities and research institutes describing their own eLabFTW service, a CNRS framework contract notice, a peer-reviewed article, a conference abstract, a master's thesis, an Academic Cloud announcement and G2, with four reviews from 2022 and 2023. No public record yet covers a deployment in an industrial or regulated laboratory. What this means

Limitations reported

Documented deployments

Other findings from independent sources (23)

User reviews

Alternatives to eLabFTW

AlternativeDeploymentPricingWhy consider it
SciSure logoSciSure Cloud, On-premise Quote only The University of Würzburg offers both from its IT Centre, Labfolder under a contract with SciSure next to its eLabFTW server; at RWTH Aachen, the Faculty of Medicine uses the SciSure ELN while the university's ELN@RWTH runs eLabFTW.
SciNote logoSciNote Cloud, On-premise Quote only Also publishes its code as open source (MPL-2.0 rather than AGPL-3.0) for customers to install locally, and sells Premium plans that include a local installation with vendor support.
LabArchives logoLabArchives Cloud From 330 USD per user per year, Professional plan, academic pricing Also publishes its prices, but for a cloud-only service billed per user, from 330 USD a year at academic pricing, where eLabFTW's software is free and Deltablot prices hosting in bands of active users.

eLabFTW product and company details

VendorDeltablot (SASU), Villejuif, France
DeploymentCloud, On-premise
HostingSelf-hosted on the customer's GNU/Linux servers in containers, or managed by Deltablot in Europe, North America, Asia, Australia or Latin America according to the customer's location, with a SecNumCloud plan in Paris
LicenceAGPL-3.0
Latest versionVersion 6.0.6, latest stable release, described as non-critical, 2026-10-04
ModulesExperiment templates, Inventory, Chemical drawing, E-signature, Collaboration, API
Websiteelabftw.net
Integrations (9)
Support and services (5)
Release history (5)
Company timeline and vendor figures (3)

Figures stated by the vendor:

Related pages

eLabFTW FAQ

How much does eLabFTW cost for a department of about 100 users?

The software itself is free. Self-hosted, the cost is a GNU/Linux server and an administrator's time, plus 3,000 EUR a year if you want PRO Support. On Deltablot's hosting, PRO Hosting Plus covers about 128 active users and 500 GB or more of storage for 4,985 EUR a year; an active user is an account that connects at least once in a month. The price page does not say whether amounts include VAT.

What does an IT team need to self-host eLabFTW?

Deltablot's supported production setup is GNU/Linux, in containers. An existing database service must be MySQL, not MariaDB, and version 6 requires MySQL 8.4 or later with the container running as a user. Sign-in can use local accounts, SAML, LDAP or headers set by the institution's middleware, and files can go to local storage or an S3-compatible service. The documentation expects an administrator comfortable with the command line, updates and backups.

Can eLabFTW hold health or other sensitive data?

That depends on where it runs. Deltablot's EU hosting data centre in Paris is certified HDS, and its SecNumCloud plan runs exclusively in Paris with encryption at rest; these certifications are held by the hosting providers. Institutional instances set their own rules: INRAE's offer is mandatory for units handling sensitive data but not approved for health data for now, RWTH Aachen asked pilot users not to store patient data, and Marburg forbids personal data that needs protection.

Can a French public research institution buy eLabFTW services through a public contract?

Deltablot invites French higher-education and research institutions to contact it about an offer through a central purchasing body, which its page does not name. A public notice shows one precedent: in January 2023 the CNRS Midi-Pyrénées delegation concluded a framework agreement for the implementation, evolution, maintenance and partial operation of an ELN based on open-source eLabFTW, in SaaS and on-premise modes. The procedure drew one tender, and the agreement went to a group of two small companies; the notice does not name Deltablot. It states a total value of 1,500,000 EUR excluding VAT, while its description estimates the service at 900,000 EUR over its term, all renewals included, without explaining the gap.

Does eLabFTW work offline?

A desktop application for Windows, macOS and Linux records data without Internet access and pushes entries to an instance later, using its URL and an API key. The web version runs in any modern browser, and INRAE notes that its service cannot be reached during a network outage or server maintenance.

Sources

27 independent sources and 29 vendor or vendor-supplied sources. A profile is published only when at least three independent publishers back it; this one has 22. See the methodology. Numbers match the references in the page.

Show all 56 sources

Independent sources

  1. TED 092297-2023, France-Toulouse: cahier de Laboratoire Electronique (contract award notice), Centre national de la recherche scientifique (CNRS) (accessed 2026-10-13)
  2. Cahier de Laboratoire Électronique, organisation et utilisation (CNRS Formations), Centre national de la recherche scientifique (CNRS) (accessed 2026-10-13)
  3. Rapport d'enquête sur les usages du cahier de laboratoire électronique à l'Université de Lorraine, Université de Lorraine (accessed 2026-10-13)
  4. Offre CLE eLabFTW (INRAE), INRAE (accessed 2026-10-13)
  5. Parcours d'entrée et FAQ, offre CLE eLabFTW (INRAE), INRAE (accessed 2026-10-13)
  6. Retour d'utilisation du eLabFTW dans une (petite) unité de recherche, INRAE (accessed 2026-10-13)
  7. Laboratory Notebooks (Open Science, University of Montpellier), University of Montpellier (accessed 2026-10-13)
  8. ELN@RWTH (Electronic Lab Notebook), IT Center help, RWTH Aachen University (accessed 2026-10-13)
  9. ELN at RWTH: Pilot Phase with eLabFTW, RWTH Aachen University (accessed 2026-10-13)
  10. eLab – electronic laboratory notebook (ELN), Research data management, University of Münster, University of Münster (accessed 2026-10-13)
  11. Elektronisches Laborbuch eLabFTW (ZID, Universität Innsbruck), University of Innsbruck (accessed 2026-10-13)
  12. Elektronisches Laborbuch - eLabFTW (Philipps-Universität Marburg, eResearch), Philipps-Universität Marburg (accessed 2026-10-13)
  13. Elektronische Laborbücher (Zentrum für nachhaltiges Forschungsdatenmanagement, Universität Hamburg), Universität Hamburg (accessed 2026-10-13)
  14. Zentraler Service zur digitalen Dokumentation von Experimenten (TU Darmstadt, TUdata), Technische Universität Darmstadt (accessed 2026-10-13)
  15. Electronic Lab Notebooks (IT Centre, University of Würzburg), University of Würzburg (accessed 2026-10-13)
  16. eLabFTW for Teaching (ZIM service catalogue, Heinrich Heine University Düsseldorf), Heinrich Heine University Düsseldorf (accessed 2026-10-13)
  17. eLabFTW as an Open Science tool to improve the quality and translation of preclinical research (F1000Research 2021, 10:292, version 2), F1000Research (accessed 2026-10-13)
  18. eLabFTW, CRC 1461 RDM Guide (Kiel University), Kiel University (accessed 2026-10-13)
  19. eLabFTW (University Computing Centre Heidelberg, service catalogue), Heidelberg University (accessed 2026-10-13)
  20. eLabFTW - Research Data LMU, LMU Munich (University Library) (accessed 2026-10-13)
  21. Electronic Lab Notebook eLabFTW Coming Soon to the Academic Cloud, Academic Cloud (accessed 2026-10-13)
  22. Key Insights from the Pilot Phase of Implementing an Electronic Lab Notebook (eLabFTW): Challenges & Success Factors (GMDS 2025 abstract), German Medical Science (GMDS 2025 abstracts, PUBLISSO) (accessed 2026-10-13)
  23. Pilot Service for the Electronic Lab Notebook eLabFTW (Institute for Information Management and Communication, Kyoto University), Kyoto University (accessed 2026-10-13)
  24. eLabFTW electronic lab journal deployment for teaching (University of Helsinki research group news), University of Helsinki (accessed 2026-10-13)
  25. eLabFTW: As a tool for managing and documenting scientific data. A case study of its adoption at CIIMAR, Universidade do Porto (accessed 2026-10-13)
  26. ELN at German universities (centrally hosted and operated ELN installations), NFDI4Chem (accessed 2026-10-13)
  27. eLabFTW reviews on G2, G2 (recorded manually 2026-10-13)

Vendor and vendor-supplied sources

  1. eLabFTW pricing (Deltablot), Deltablot (accessed 2026-10-13)
  2. Regulatory compliance (Deltablot), Deltablot (accessed 2026-10-13)
  3. About Deltablot (including legal notice), Deltablot (accessed 2026-10-13)
  4. Deltablot privacy policy, Deltablot (accessed 2026-10-13)
  5. eLabFTW official website, Deltablot (accessed 2026-10-13)
  6. What's new in eLabFTW 6.0, Deltablot (accessed 2026-10-13)
  7. What's new in eLabFTW 5.6, Deltablot (accessed 2026-10-13)
  8. On-Premise vs SaaS, Deltablot (accessed 2026-10-13)
  9. Traceability and auditability (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  10. Installation introduction (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  11. Prerequisites (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  12. Import / Export (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  13. FAIR (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  14. Inventory (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  15. Compounds (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  16. Experiments (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  17. Templates (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  18. Scheduler (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  19. Sysadmin guide (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  20. API (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  21. Integrations (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  22. Offline application (eLabFTW documentation 6.0), Deltablot (accessed 2026-10-13)
  23. elabftw/elabftw repository README, Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)
  24. elabftw/elabftw LICENSE (master branch), Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)
  25. elabftw/elabftw releases, Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)
  26. eLabFTW release 6.0.0, Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)
  27. eLabFTW release 5.5.0, Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)
  28. Compliance with 21 CFR Part 11 (elabftw/elabftw discussion #3669), Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)
  29. elabftw/elabftw security advisories, Deltablot (elabftw GitHub organisation) (accessed 2026-10-13)