Pre-enrichment
Buffered peptone water, 37 °C
Branch on an intermediate result. Write reagents off at the stage that used them. Issue a protocol built from what was done, not from memory.
Full product, no card. A walkthrough runs 40–60 minutes on your own typical test request, and we reply within a day.
Buffered peptone water, 37 °C
RVS broth, 41.5 °C
XLD agar, 37 °C
Pure culture, identification kit
Agglutination with antisera
Salmonella detected in 25 g
Built from the five stages performed. Waiting for approval by the head of the laboratory.
Select a stage to see who performed it, when, on which instrument, with which reagent lots.
Illustrative method and fictitious data. Cards follow the layout of the workflow editor in the product.
Test portion, medium, temperature, tolerance and dwell time are written in the stage itself. The performer does not hunt for the standard in a folder.
Stock drops when the stage is performed, not at month-end from memory.
Reagent lot and expiry date, instrument, performer and time. What ISO/IEC 17025 asks for.
A test costs what its performed stages and written-off reagents cost. Stages never carried out stay out of cost and workload.
One for the inspector, one for the bench. The same data is typed twice, and the transcription error surfaces after the protocol has reached the customer.
A Salmonella test is five or six consecutive stages that branch on the result. The logbook keeps a single final line, so neither the timings nor the reagent use per stage can be reconstructed.
Years of results cannot be exported, only registered and printed. Hence the first question IT asks when choosing a LIMS: how do we get our data back?
Not one step happens in a spreadsheet or a messenger.
Registration forms are configured for your lab without programming. A site → workshop → sampling-point cascade offers only the points of the chosen workshop, not the whole dictionary.
Print a label with a Code128 barcode and a QR code and receive samples with a scanner. The sample is blinded: the performer sees the sample code, not the customer.
Draw the route in a visual editor: branches, conditions, parallel branches, timed holds. Record the result at the stage and the reagents are written off.
If an instrument’s calibration has lapsed, the work is blocked, not just flagged.
Approval by the head of the laboratory is mandatory. Until the protocol is approved, it is not issued. It is printed on your own template.
A workshop or an external customer sees its own requests and finished protocols in a portal, and asks a question about a request in the chat next to it.
Internal quality control with Levey–Jennings charts and Westgard rules. A run that breaks a rule is flagged when the result is entered, not when someone reviews the chart.
Lots, expiry dates, balances, price. Write-off at the stage, so the cost of a sample and the consumption per customer come from actual data.
Registry with a log of verifications, calibrations and maintenance. A stage on an instrument that is out of calibration does not start.
A competence matrix says who may perform which test, with reminders about due dates.
Turnaround, SLA breaches, the share of positive and non-representative samples. Production-control programmes and the sampling schedule generate the work.
The branching workflow is one of several editors. Forms, document templates, dashboards, dictionaries and integrations change in the interface, with no new release.
Passwords and tokens are stored encrypted.
The more multi-stage methods, incoming-material control and production control you run, the more of your work today ends up in neither the logbook nor the cost calculation.
Incoming raw-material control, equipment swabs, finished products, raw milk intake, total viable count, supplier-lot traceability.
Salmonella and Campylobacter stage by stage, litter and workshop monitoring, veterinary reporting.
Diagnostics by multi-stage methods and issuing conclusions.
Sampling programmes and multi-parameter panels, with repeat tests when a result is out of range.
Multi-step preparation, duplicate agreement checks and instruments that are calibration-gated.
One method across all sites, a network-wide summary, turnaround and workload compared between laboratories.
We answer the IT and information-security questions before you sign.
XLSX and CSV from any table, an OData feed for BI, and a full database dump. On your own server the database sits inside your environment, so the dump needs no involvement from us.
One codebase, not a separate build. Run it in our cloud, or as a Docker stack on your own Linux server. Moving between the two is a PostgreSQL dump.
Samples are blinded for performers. Permissions are deny-by-default. Data isolation is enforced in the database itself. The audit log is immutable: who, what, before and after, when. A protocol cannot be issued without approval.
Go and PostgreSQL, React and Docker. Not one proprietary component. Active Directory sign-in over LDAPS, encrypted integration secrets, and a deep health check on every release with automatic rollback.
An annual subscription with public rates. Exactly one thing is counted: how many laboratories you connect. Users, samples and modules never appear on the invoice.
Tell us about your lab. We prepare a trial workspace and email you the access, usually within one working day.
30 days, the full product, no card. Confirm your e-mail and we prepare your workspace.
Start your free trialPrefer to see it first? Request a walkthrough below.
Thank you. We will be in touch shortly.