eLabFTW

Open-source laboratory data management, honestly reviewed. No marketing fluff, just what you get when your research group self-hosts it.

TL;DR

• What it is: Open-source (AGPL-3.0) electronic lab notebook (ELN) for research teams — think LabArchives or Benchling, but running on your own server and billing you nothing [README][website].
• Who it’s for: Academic lab groups, research institutes, and biotech/chemistry startups that need a proper experiment tracking system without commercial ELN subscription fees. Specifically designed by researchers, for researchers [1][2].
• Cost savings: Commercial ELNs like Benchling are priced for enterprise budgets (contact-sales only). SciNote’s professional tier runs $10/user/month. A group of 10 researchers on a commercial ELN can easily spend $1,000–$2,000/year. eLabFTW self-hosted costs the price of a VPS [website].
• Key strength: Purpose-built for actual lab workflows — trusted timestamping, inventory management, equipment booking, molecule editor, LaTeX support, and a real REST API. One instance can host an entire research institute [README].
• Key weakness: AGPL-3.0 license (not MIT) and a narrower target audience than general productivity tools. At 1,291 GitHub stars, it’s a specialist tool — not a broad-adoption platform [README]. Community review coverage is thinner than for more mainstream self-hosted software.

---

What is eLabFTW

eLabFTW is an electronic lab notebook manager that runs in a browser. Researchers use it to document experiments, store protocols, manage lab inventory, and book shared equipment. The comparison to mainstream ELNs is the right mental model: it replaces the paper lab notebook and the expensive commercial software that replaced the paper lab notebook.

What makes it different from a wiki or a notes app is that it was built for the specific documentation requirements of scientific research. That means built-in trusted timestamping (for intellectual property protection), cryptographically signed entries, blockchain timestamping, and an audit log — features that matter when you need to prove the date of a discovery or defend a patent [README][website]. These aren’t bolt-ons; they’re core to why the project exists.

The project is maintained by Nicolas Carpi, a researcher at Institut Curie in Paris, with contributions from a worldwide community. It has been peer-reviewed in scientific literature — an unusual signal of legitimacy for an open-source tool [2]. The JOSS (Journal of Open Source Software) badge in the README indicates it passed academic software review. A single installation can host multiple teams from different departments or institutions, which is how universities typically deploy it — one IT-managed instance, accessed by dozens or hundreds of researchers [1][website].

The AGPL-3.0 license is genuinely important context. It means the software is free, the source is open, there are no features behind a paywall — but it also means anyone who modifies and deploys eLabFTW as a service must publish their changes. This is the stronger copyleft direction compared to MIT, which matters if you’re a SaaS company thinking about embedding it. For a research group that just wants to run it internally, it makes no practical difference [website].

---

Why people choose it

The two substantive academic reviews of eLabFTW [1][2] land in the same place: the main barrier to ELN adoption in research labs is perceived complexity and cost, and eLabFTW specifically addresses both.

On setup friction. Researchers Michael Hewera and Ulf Kahlert (Heinrich Heine University and University Hospital Magdeburg) describe setting up eLabFTW on a personal computer: “We found it to be a very straightforward process — it can be done in less than half a day by a person with average computer skills.” [1] For a lab where the average member has no DevOps background, this is a meaningful claim. Their university’s central IT already hosted an instance, but they validated that a non-sysadmin could also do it independently [1].

On open science and reproducibility. The peer-reviewed F1000Research paper [2] frames eLabFTW in the context of the reproducibility crisis in life sciences — the ongoing problem of published results that other labs cannot replicate. An ELN addresses this by making experiment documentation structured, searchable, timestamped, and shareable alongside publication data. The paper was revised three times through peer review and approved, which is the scientific community’s way of saying: yes, this tool does what it claims, and the approach is sound [2].

On cost vs. commercial ELNs. The comparison that matters most for the unsubbed.co audience is against paid alternatives. Commercial ELNs — Benchling, LabArchives, Labfolder — operate on per-user subscription models that add up quickly for a 10-20 person lab group. Benchling targets pharmaceutical companies with enterprise contracts. LabArchives runs roughly $15/user/month for professional accounts. SciNote limits the free tier to 1GB storage, 3 projects, and 5 users before charging $10/user/month. None of them give you control over your data location, and all of them can change pricing, be acquired, or shut down [website].

eLabFTW explicitly calls this out: “Cloud services can shut down, be acquired, or change privacy policy any time. The last thing you want is proprietary formats and data lock-in.” [website] The ELN data format matters because research data has to be stored and accessible for decades — long after the SaaS vendor has pivoted or been bought.

The ResearchGate thread [3] shows this tension predates eLabFTW: researchers were comparing solutions going back to 2012, with complaints about $100/year per-person licensing making commercial ELNs unsustainable for lab groups. One respondent built their own custom solution because available options were either too expensive or too rigid [3]. eLabFTW is the mature open-source answer to exactly that complaint.

---

Features

Based on the README and website:

Core lab notebook:

• Experiment editor with rich text, tables, embedded images, LaTeX math rendering, and attached files [README]
• Templates to standardize experiment structure across a team [website]
• Steps and workflow function to track multi-stage protocols [website]
• Tags, categories, and status tracking — fully customizable per team [website]
• Full-text search across all entries [website][1]
• Trusted timestamping (RFC 3161 standard — legally recognized) and blockchain timestamping for intellectual property protection [README][website]
• Cryptographically signed entries and audit log [website]

Inventory and database:

• Resource database for lab materials: reagents, antibodies, plasmids, cell lines, chemical compounds, equipment [README][website]
• Compounds database with PubChem import (CAS numbers, SMILES, InChI) [website]
• Molecule editor — draw structures directly in the browser, save in standard formats [website]
• Container system for tracking storage locations of materials [website]
• Bidirectional linking between experiments and resources [website]

Scheduling and collaboration:

• Booking calendar for shared equipment — with access controls for who can book what and when [website]
• Multi-team support: one instance, multiple independent research groups, each with their own data and permissions [README][website]
• Team Groups for fine-grained permissions — control who can view or edit each entry [website]

Export and interoperability:

• Export in PDF, ZIP, CSV, JSON, and the .eln interoperability format [website]
• eLabFTW is part of the ELN consortium promoting the .eln standard for cross-platform data portability [website]
• Public REST API for programmatic access [README][website]
• Support for scientific file formats (specifics not itemized in available data) [README]

Access and usability:

• Browser-based — works on desktop, tablet, smartphone [website]
• Available in 21 languages [README][website]
• WCAG 2.1 and RGAA v4 accessibility compliance [website]
• Todolist built in [README]
• Custom shortcuts [website]

Security:

• Regular code auditing and bug bounty program [website]
• CII Best Practices badge (passes Open Source Security Foundation’s checklist) [README]
• Multi-factor authentication [website]
• Self-contained — no data leaves your server unless you choose to export it [README]

---

Pricing: self-hosted vs. commercial ELN math

eLabFTW self-hosted (Community):

• Software license: $0 (AGPL-3.0) [README]
• VPS to run it: $5–15/month on Hetzner, Contabo, or DigitalOcean
• Minimum specs: 512MB RAM (1GB recommended), 300MB disk — Docker handles the rest [README]

eLabFTW PRO Hosting (via Deltablot):

• Managed hosting with data stored in Paris, France [website]
• Pricing not listed publicly — requires contacting Deltablot [website]
• Intended for institutions that want the software benefits without self-hosting responsibility

Commercial ELN alternatives for comparison:

• SciNote: Free tier capped at 5 users, 1GB, 3 projects. Professional $10/user/month (self-reported from documentation — verify before purchasing)
• LabArchives: Reported at roughly $12–15/user/month for academic professional accounts; classroom plans around $49/month for 100 users
• Benchling: Enterprise only, contact sales — not disclosed publicly, widely reported as expensive for small labs
• Labfolder: Similar per-user SaaS model

Concrete math for a 10-person research group:

At $12/user/month, a 10-person lab on a commercial ELN pays $120/month — $1,440/year — just for software access, with no control over where the data lives or what happens when the company is acquired. On eLabFTW self-hosted: a $10/month VPS and one afternoon of setup. $120/year, full data ownership.

Over five years (a typical grant cycle): commercial ELN ≈ $7,200. Self-hosted eLabFTW ≈ $600 plus occasional maintenance. The difference is real grant money that could fund reagents or a few months of a student stipend.

The catch: this math assumes someone on the team is comfortable with Docker. If that’s not the case, either Deltablot’s hosted option or a one-time deployment service closes that gap.

---

Deployment reality check

The documentation is explicit about requirements: Docker must be installed on the host server. Everything else — PHP, web server, MySQL — runs inside containers, which means you don’t fight with version conflicts or system-level package management [README].

What you actually need:

• A Linux VPS with at least 512MB RAM (1GB recommended) [README]
• Docker and docker-compose
• A domain name and HTTPS (Caddy or nginx as a reverse proxy)
• MySQL (bundled in the default compose setup)

Time estimate: Hewera and Kahlert [1] describe setup as completable “in less than half a day by a person with average computer skills.” This aligns with the complexity level of the tooling — Docker-based installs have become substantially easier in the last few years, and eLabFTW doesn’t appear to be an outlier in difficulty.

What can go sideways:

• The Docker requirement means a pure non-technical user still needs either some comfort with the command line or someone to do the initial deploy. The tool is meant to be deployed once and then managed through the browser UI — but that first deploy requires technical access.
• The website and documentation advertise institutional deployment as the intended mode — universities typically have IT departments handle this. A solo researcher at a startup doesn’t have that backstop [1][website].
• Deltablot provides commercial support and professional hosting for groups that need a managed option [README][website].
• The Reddit thread [4] was seeking user experience reports but didn’t surface concrete usability complaints in the available data — which could mean smooth sailing, or simply that the community review corpus for this tool is smaller than for mainstream software.

---

Pros and cons

Pros

• Actually free, no feature gating. The website states explicitly: “There are no features hidden behind a paywall, everything is available immediately, at no cost.” [website] This is unusual — many “open source” projects tier their features, reserving useful things for paid plans.
• Built for research workflows specifically. Trusted timestamping, blockchain timestamping, audit logs, molecule editor, LaTeX, scientific file format support — these aren’t afterthoughts. They’re the reason the tool exists [README][website].
• Multi-team on one instance. A university can run one eLabFTW installation and host dozens of independent lab groups, each with their own isolated data and permissions [README][website]. This is how it’s actually deployed at many institutions [1].
• Data stays where you put it. Self-hosted means no third-party sees your research data. For pre-publication results, this matters [1][2][website].
• REST API for programmatic access. Researchers can integrate eLabFTW with analysis pipelines, scripts, or custom dashboards [README][website].
• Peer-reviewed in scientific literature. The JOSS paper and F1000Research publication [2] give it a credibility signal that most self-hosted tools don’t have.
• 21 languages. Meaningful for international research collaborations [README][website].
• Active development. CircleCI CI, code coverage tracking, and regular releases indicate a maintained codebase, not abandonware [README].

Cons

• AGPL-3.0, not MIT. If you’re a company wanting to embed eLabFTW in a commercial product, the copyleft terms require publishing your modifications. Fine for internal research use; relevant if you’re building a derivative product [README].
• 1,291 stars — specialist tool. This is not a criticism of quality, but it reflects the niche. The community, plugin ecosystem, and third-party tutorials are smaller than for general-purpose tools. When you hit a problem, Stack Overflow won’t have the answer — you’ll be in GitHub Issues [README].
• Hosted pricing not transparent. Deltablot’s managed hosting has no public pricing page — you have to contact them [website]. This is standard for enterprise academic software but inconvenient for budget planning.
• Technical bar for self-hosting. Docker-based setup is not zero friction. A pure non-technical user — with no Linux or command-line exposure — will need help for the initial deployment [1][README].
• Limited independent community reviews. The review corpus for this tool is thin outside of academic publications. Most self-hosted tools have years of Reddit threads, blog comparisons, and YouTube walkthroughs. eLabFTW doesn’t have that density, which makes it harder to assess edge cases and real-world pain points [4].

---

Who should use this / who shouldn’t

Use eLabFTW if:

• You’re a research lab, biotech startup, or pharmaceutical team currently paying per-user for a commercial ELN and want to eliminate that cost.
• Your institution is willing to run a single instance hosted by IT that serves multiple research groups — this is the optimal deployment model [1][website].
• You need legally defensible timestamping and auditing for intellectual property or regulatory compliance [README][website].
• You want research data to live on your infrastructure, not a vendor’s cloud [1][2].
• Someone on the team can handle a one-time Docker deployment.

Skip it if:

• You’re not a research organization. eLabFTW is built specifically for lab workflows — if you’re trying to manage non-research documentation, a general-purpose wiki (Outline, Wiki.js) will serve you better.
• Your team needs a fully managed, zero-technical-setup solution and isn’t comfortable contacting Deltablot for hosting quotes. In that case, SciNote’s free tier or LabArchives is the lower-friction path.
• You’re a company planning to embed lab notebook functionality in a commercial SaaS product and need a permissive license — AGPL-3.0 will complicate that.

---

Alternatives worth considering

• SciNote — The closest free-tier competitor. Has a free plan (5 users, 1GB, 3 projects), open-source community edition, and commercial tiers. Some researchers consider the UI more polished; the ELN consortium interoperability work is shared with eLabFTW [3].
• LabArchives — Popular in US academic institutions, often has institutional licensing. Per-user pricing at scale. Closed source, no self-hosting option.
• Benchling — The enterprise standard in pharma and biotech. Powerful, feature-rich, expensive. Not realistic for academic labs without substantial budgets. No self-hosting.
• RSpace — Open-source ELN, similar positioning to eLabFTW. Less active development cadence than eLabFTW based on available signals.
• Jupyter + Git — What many research groups actually use for computational work. Good for code and data analysis, terrible for wet-lab protocols and inventory management.
• OneNote / Notion — Common informal lab notebooks. No timestamping, no inventory, no audit log, no scientific format support. A stopgap, not an ELN.

For a life sciences or chemistry lab that’s outgrown paper notebooks and wants to avoid commercial ELN costs, the realistic shortlist is eLabFTW vs. SciNote. eLabFTW has more features and a more rigorous security posture; SciNote has a more approachable free tier for small groups. Both self-host via Docker.

---

Bottom line

eLabFTW is the legitimate open-source answer to an underserved problem: research labs paying $1,000–$2,000/year for commercial ELN subscriptions that lock their scientific data into a vendor’s cloud. The tool is mature (peer-reviewed in scientific literature [2], actively maintained, deployed at research institutions globally), purpose-built for actual lab workflows, and has no feature gating behind a paywall. The AGPL-3.0 license means your data and your software configuration remain yours.

The honest caveats: it’s a specialist tool with a specialist community. The self-hosting path requires Docker familiarity, and the managed hosting pricing from Deltablot isn’t publicly listed. The third-party review corpus is thin compared to mainstream self-hosted tools — this review synthesizes what’s available, but there’s less independent validation of edge cases than you’d find for something like Nextcloud or n8n.

For a research group currently paying monthly for LabArchives or agonizing over Benchling’s pricing page, the math is simple: self-host eLabFTW on a $10 VPS, spend an afternoon on setup, and never pay a per-user ELN bill again. If the afternoon of setup is the blocker, that’s exactly what upready.dev deploys for clients — one-time fee, you own the infrastructure.

---

Sources

1. F1000 Blogs — Michael Hewera & Ulf Kahlert — “eLabFTW: a simple tool for open science, data quality, and reproducibility” (November 2, 2021). https://blog.f1000.com/2021/11/02/elabftw-electronic-labatory-notebook/
2. F1000Research (peer-reviewed) — Hewera M, Hänggi D, Gerlach B, Kahlert UD — “eLabFTW as an Open Science tool to improve the quality and translation of preclinical research” (v3; peer review: 2 approved). https://f1000research.com/articles/10-292
3. ResearchGate — “What is your experience with electronic lab notebooks/software to keep your experiments organized?” (community discussion, 2012–present). https://www.researchgate.net/post/What_is_your_experience_with_electronic_lab_notebooks_software_to_keep_your_experiments_organized
4. Reddit r/LadiesofScience — “Personal experience with eLabFTW?” (April 2026). https://www.reddit.com/r/LadiesofScience/comments/1sftquc/personal_experience_with_elabftw/

Primary sources:

• GitHub repository and README: https://github.com/elabftw/elabftw (1,291 stars, AGPL-3.0)
• Official website: https://www.elabftw.net
• Documentation: https://doc.elabftw.net
• Deltablot commercial hosting: https://www.deltablot.com/elabftw