I’m building OpenLIMS, an open-source Laboratory Information Management System using Django, React, PostgreSQL, Redis, Docker, and GitHub Actions.
The goal is to create a developer-friendly and configurable LIMS for small labs, research groups, and biotech teams that want to move away from spreadsheets and manual sample tracking.
Current features include:
Sample management
Inventory locations and containers
Custom fields for different lab workflows
Event/audit logging
File attachments for samples
Docker-based local setup
React frontend
Basic reports and system status pages
CI with GitHub Actions
It is still early and not validated for regulated production use, but I’m trying to build it with production-style patterns like audit trails, role-based access control, configurable workflows, and clear documentation.
I’d appreciate thoughts from people working in lab automation, LIMS, bioinformatics, or lab software:
What core LIMS workflows should I prioritize next?
What would make this useful for a small research lab?
What integrations would matter most: instruments, barcode scanners, CSV import/export, ELN, or something else?
Haha, I didn’t realize the name had that much history — maybe it is cursed
That’s good to know though. I’ll look into the older OpenLIMS projects and make sure I understand what happened with them. I’m still early, so I’m not opposed to renaming if it avoids confusion and gives this project a cleaner identity. Appreciate the heads-up!
This is cool! I guess my feedback is that there are a lot of these projects lately, and it’s probably very hard to get people to use something new.
I think the biggest value add for open source projects like this is creative new architecture solutions that solve specific problems, rather than a wholesale new LIMS system that tries to solve everything.
For instance, if you think you have a really good way to handle chain of custody attribution, share that with a write up! Discuss integration with different vendors and supplier APIs etc. I think specialization is key here, many people can spin up an entire LIMS system that works decently, but how many people have thought really hard about solving specific problems within that domain, and solving them really well? Certainly far fewer.
I agree — positioning it as a full LIMS is probably too broad early on. I’m going to narrow the focus around specific problems like chain of custody, audit trails, sample attribution, and instrument/data ingestion.
I really like your point about writing up the architecture for one hard problem instead of just promoting the whole system. Appreciate the thoughtful feedback.
Hello, just wanted to share an update:I’ve been continuing work on OpenLIMS, an open-source LIMS project for small labs and research groups.
Recent progress includes better sample and project tracking, audit/event history, basic reports/status pages, and sample comparison workflows.
OpenLIMS now also includes bioinformatics and analytical workflow support, including BLAST, sequence alignment, and mass spec data handling. The goal is not to replace large enterprise LIMS systems, but to build a lightweight, self-hostable tool that can help organize samples, files, results, and project history in one place.
Great initiative, we looked at adding one to our labs but the commercial ones were too rigid or attached to the instrument platform and the open source was definitely missing. I think there is a great need and perhaps a range of people who will contribute. I will spread this to some of our instrument suppliers, may be they can all band up and get one that becomes widely adopted in labs - universities will be a start. Keep us posted with your updates. Following your project on github.
Two things which can be key driver for adoption - support 21 CFR Part 11 and ISO 17025 - I guess doing this as “fully compliant” on an open soruce will be too expensive but if the code base supports the traceability and safety of data requirement then this will become very attractive for labs.
OpenLIMS is still early, but I’m trying to make sure it is shaped by real lab needs instead of guessing from the outside. A university lab recently approached me, and I’m starting to work with them on how OpenLIMS could be deployed or adapted for their workflows.
I’m also open to helping other labs or research groups test it, deploy it, or give feedback on what would make it useful in practice. The goal is to keep it lightweight and configurable for teams that are still relying on spreadsheets, shared folders, or custom manual tracking.
I’m also considering adding support for 21 CFR Part 11-style requirements by the end of the year, especially around audit trails, user access, electronic records, and review/approval workflows.
PlantUML’s TikZ/LaTeX export currently focuses on generating diagram structures rather than passing arbitrary raw LaTeX commands directly into the output. If you need advanced formatting, it may be worth reviewing the official PlantUML documentation to see which export customizations are supported and whether there are any workarounds using notes, sprites, or post-processing. For broader LaTeX integration ideas, the TikZ & PGF documentation is also a useful reference, especially when modifying generated TikZ code after export.
