What we can prove, what we've shown, and what we won't claim
A commercial-proof cleanup found a few public claims about LIMS BOX that weren't backed by evidence — including a fabricated customer case study. This page is the record of what was found, what changed, and an ongoing, plain-language account of what we can actually stand behind. It will be kept current as the product and its public proof evolve.
Verified
Independently checkable facts — about the open-source technology, hosting, and founder background — not claims about customer relationships.
SENAITE is open source and publicly available
GPL-licensed, full source on GitHub. Anyone can audit the code LIMS BOX runs on.
SENAITE's provenance
Created by RidingBytes GmbH (Bonn, Germany), founded by Ramon Bartl and Lukas Graf — a public fact about the open-source project, not a claim of an active relationship between RidingBytes and LIMS BOX.
Hosting infrastructure holds SOC 2 Type II attestation
LIMS BOX runs on cloud infrastructure that maintains SOC 2 Type II attestation — a claim about the infrastructure provider, not a certification LIMS BOX itself holds.
Founder background
Hudson (Hud) Taylor — MS Biochemistry (UCSD / Salk Institute), Certified Water Specialist (California), prior senior LIMS development role at the State of Alaska Department of Health public health lab. See /about.
Demonstrated
Working capability, shown against local or fictional seed data rather than a live paying customer.
Personnel Pack admin UI
Personnel list, competency status, and person-detail views (competency, training, sign-offs, procedure authorizations) — captured from a local seeded fictional demo, no real lab data. See /personnel-pack.
Survey-Ready Export
ZIP export (index + one PDF per person) and a standalone PDF export, verified working end-to-end against local fictional seed data.
SENAITE chat-to-write voice integration
A voice-command interface that writes to a SENAITE instance, demonstrated in a local, offline Docker-based SENAITE environment for the Pelican-case hardware deployment — a separate system from the public lims.bot website chat widget below.
Public website chat (LIMS BOT)
Grounded, citation-backed FAQ answering only. Automated tests enforce that it never fabricates an answer, never writes data, and never emits a locked forbidden compliance phrase (see tests/bot/engine.test.ts).
Proposed
On the roadmap. Not yet built, and not claimed as shipped anywhere on the site.
Sample tracking & chain of custody module
On the roadmap — not yet shipped as a standalone module.
Configurable result pipeline
Instrument → QA → release → archive workflows that labs can define themselves. Roadmap item.
Native instrument integrations
Direct connections to common platforms (e.g. Roche, Abbott) beyond today's CSV/XML file-based import. Roadmap item.
Mobile check-ins
Staff certifications, sample receipt, and training sign-offs from a phone. Roadmap item.
Not Publicly Claimable
Claims that were live on the site and have been removed or reframed. Kept here as a durable record so they don't quietly reappear.
Active technical collaboration with SENAITE's founder
Previously stated on the homepage and partners page. No current authorization or evidence supports an active collaboration with Ramon Bartl — removed.
"Clear Creek Environmental Testing" case study
A named customer case study with attributed testimonials (Rachel Moreno, David Park) that was not a real, approved customer. The page is now explicitly labeled a hypothetical, illustrative scenario with no company name and no attributed quotes.
Generic-attributed customer testimonials
Pain-point quotes attributed to unnamed roles ("Environmental Lab Manager," "Lab Quality Coordinator") on the environmental and clinical pages read as real customer quotes. Reframed as explicitly illustrative — not attributed quotes.
An active, currently-running pilot cohort
No enrolled, verified pilot customers exist yet. Site copy now describes the 5-lab early-adopter pilot as opening/recruiting, not already running.
Formal partnership or consulting relationship with RidingBytes
"Technical consultation," "we contribute upstream," and "backed by the people who built the LIMS engine" implied an active, endorsed relationship beyond using their open-source software. Removed.
Unqualified "compliant / certified" badges for the software itself
CLIA §493.1407, 40 CFR Part 136, ISO 15189 §6.2.4, and 21 CFR Part 11 certify labs and personnel, not software. Site copy now uses "designed for / built for / ready" language instead of "compliant."
Specific historical usage figures
A blog post cited a precise beta customer count and a sweeping "every lab we talked to" claim that can't be substantiated. Softened to general, non-specific framing.
Questions about any claim on this page or elsewhere on the site — email us directly.
Contact Us