SENAITE vs commercial LIMS

When a lab writes a LIMS RFP in 2026, the same four or five names come up: LabWare, STARLIMS (Abbott Informatics), LabVantage, Thermo SampleManager, and depending on segment, Autoscribe Matrix or Siemens Unilab. Business-wise they behave similarly: proprietary source, per-user or per-seat licensing, annual maintenance fees on top, and a vendor-run implementation partner network.

SENAITE is a different animal. It is Python + Plone, GPL-2.0, developed in the open on GitHub, with no licence fee at any tier. The code is the code the core developers use in production. Companies like RIDING BYTES sell the surrounding services (implementation, validation, hosting, support) but the software itself is free to run.

Commercial LIMS costs stack in three layers: an upfront license (often five to seven figures for mid-size labs), a recurring maintenance fee at 18-22% of the licence per year, and a professional-services engagement to implement it. Add-on modules (regulatory, stability, biobanking) are priced separately.

SENAITE has no licence layer at all. What you pay for is the same thing a commercial buyer pays their partner network to do: requirements analysis, configuration, instrument integration, validation, training, hosting, support. The difference is that when the engagement ends, you own the running system outright and can hire any SENAITE-competent developer to keep going.

For a mid-size lab (30-80 users, 15k samples/year), the typical 5-year total cost of ownership on a commercial LIMS lands in the €400k-€900k range including licence, maintenance, implementation, and add-ons. The equivalent SENAITE engagement, including a proper validation package, comes in materially lower because the licence layer is zero.

With a commercial LIMS, the source is the vendor's. You get compiled binaries, an admin console, and a configuration layer. Custom logic beyond configuration (a bespoke calculation, an instrument driver, a report template) either goes into the vendor's scripting sandbox or gets built by their services team as billable work. Migration off the platform, when the day comes, is a data-export exercise plus a new implementation.

SENAITE ships full source. Custom logic lives in your own add-on next to the platform's code, versioned in your repository, deployed with your buildout. If the developer who wrote it leaves, another SENAITE developer reads the same code. Migration off SENAITE is still a data-export exercise, but the running system belongs to you the whole time it is running.

A commercial LIMS is the safer default when you are in heavily regulated pharma production with mature 21 CFR Part 11 validation SOPs and a mandate to buy from a vendor with a named support contract. The premium buys procurement peace of mind and an audit story that is already familiar to your inspector.

SENAITE is the better fit when your lab is publicly funded, cost-sensitive, needs full source access for audit or sovereignty reasons, wants to avoid multi-year licence commitments, or already uses open-source tooling elsewhere in the stack. Water utilities, environmental agencies, mining labs, clinical research groups, veterinary and animal-health labs, university labs running under ISO 17025 — SENAITE was built for exactly these settings.

The wrong reason to pick either is "everyone else in the industry uses X". LIMS choices last a decade; the fit with your operating model matters more than the brand on the RFP.