Lime LIMS

A LIMS that follows your method: every stage, every branch.

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.

  • In production at a large agricultural holding.
  • Open stack: Go, PostgreSQL, React, Docker. No proprietary components.
  • Audit trail, deny-by-default permissions and mandatory approval, built for ISO/IEC 17025.
Detection of Salmonella spp. in 25 g of raw meat One method, two outcomes. Switch the plating result.
Plating result

Pre-enrichment

Buffered peptone water, 37 °C

18 h
Reagents written off
Peptone water225 ml
Not performed · 0 reagents

Selective enrichment

RVS broth, 41.5 °C

24 h
Reagents written off
RVS broth10 ml
Not performed · 0 reagents

Plating on selective medium

Branching

XLD agar, 37 °C

24 h
+Typical colonies
−No typical colonies
Reagents written off
XLD agar plates2

Biochemical confirmation

Pure culture, identification kit

24 h
Reagents written off
Identification kit1
Not performed · 0 reagents

Serotyping

Agglutination with antisera

24 h
Reagents written off
Antisera kit1
Not performed · 0 reagents

Protocol

Salmonella detected in 25 g

Built from the five stages performed. Waiting for approval by the head of the laboratory.

Report due
Sat 7 Mar, 04:48
4 d 21 h after intake
Reagent write-offs
5 lines
One per stage performed
Stages performed
5 of 5
 

Every stage is its own record

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.

  • The method inside the stage

    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.

  • Write-off at the moment of work

    Stock drops when the stage is performed, not at month-end from memory.

  • Traceable at every stage

    Reagent lot and expiry date, instrument, performer and time. What ISO/IEC 17025 asks for.

  • Cost from what happened

    A test costs what its performed stages and written-off reagents cost. Stages never carried out stay out of cost and workload.

The method has stages. The record has one line.

  • Two logbooks for one sample

    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.

  • Intermediate stages leave no trace

    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.

  • The archive belongs to someone else’s system

    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?

From intake to an approved report, in one system.

Not one step happens in a spreadsheet or a messenger.

  1. 1

    Register and receive

    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.

  2. 2

    Run the workflow

    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.

  3. 3

    Approve and release

    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.

Control charts with the rules already applied.

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.

Control sample, assay valueMean 50.0 mg/L · SD 0.8 · illustrative data
In control12s warningRule broken (action)
Hover, tap or focus a point to read the rule that applies.
  • Reagents and cost

    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.

  • Instruments

    Registry with a log of verifications, calibrations and maintenance. A stage on an instrument that is out of calibration does not start.

  • People

    A competence matrix says who may perform which test, with reminders about due dates.

  • Dashboard

    Turnaround, SLA breaches, the share of positive and non-representative samples. Production-control programmes and the sampling schedule generate the work.

What your administrator changes without a ticket.

The branching workflow is one of several editors. Forms, document templates, dashboards, dictionaries and integrations change in the interface, with no new release.

Forms and templates

  • Sample registration form: which fields, sections and input order.
  • Protocol and act templates: your own DOCX file with placeholders.
  • Dashboards: drag tiles, hide the rest.

Integrations

  • Your own SMTP: e-mails go out from your company’s domain.
  • BI feed: Power BI over a token, limited to an IP allowlist.
  • Directory sign-in: Active Directory over LDAPS.

Passwords and tokens are stored encrypted.

Laboratory resources

  • Reagents: the laboratory maintains the dictionary itself.
  • Instruments: registry, calibration and maintenance log.
  • Authorizations and training: competence matrix, due-date reminders.

Talking about a sample

  • Laboratory chat: channels, mentions, attachments, links to samples.
  • Support channel: a question to support straight from the system.

A network of laboratories

  • One summary for all sites, with a jump into a specific laboratory.
  • Laboratories and users are created from one place.
  • Switch between laboratories without a second login.

For labs where one test is more than one step.

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.

  • Food, meat, dairy and feed

    Incoming raw-material control, equipment swabs, finished products, raw milk intake, total viable count, supplier-lot traceability.

  • Poultry and livestock

    Salmonella and Campylobacter stage by stage, litter and workshop monitoring, veterinary reporting.

  • Veterinary laboratories

    Diagnostics by multi-stage methods and issuing conclusions.

  • Environmental and water

    Sampling programmes and multi-parameter panels, with repeat tests when a result is out of range.

  • Chemical and materials testing

    Multi-step preparation, duplicate agreement checks and instruments that are calibration-gated.

  • Laboratory networks

    One method across all sites, a network-wide summary, turnaround and workload compared between laboratories.

Your data is yours. Your IT can check the rest.

We answer the IT and information-security questions before you sign.

Data export

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.

Cloud or your own server

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.

ISO/IEC 17025 discipline

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.

Stack

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.

Assurance

  • ASVS 5.0: OWASP self-assessment, levels L1 and L2 checked against the source code.
  • Support: first response to a critical incident within 4 hours in business hours, under the support contract.
  • Source-code escrow: a contract clause that discloses the source if support is discontinued.

Ask for the IT and security material

One price per laboratory. Everything included.

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.

1 laboratory€10,000per laboratory, per year
5 laboratories€9,000per laboratory, per year
10 laboratories€8,000per laboratory, per year
15 laboratories≈€6,700per laboratory, per year
More than 15By agreementper laboratory
Included
  • The full functionality of the system, at any scale
  • Configuration and onboarding for your processes
  • Support with an SLA, and product updates
  • Bug fixes, always free
  • A BI feed for your analysts
Separately, on request
  • Integration with laboratory instruments and internal systems
  • Installation on your own server, under a separate contract
  • Custom development specific to your enterprise only
After your request
  • A demo of 40–60 minutes on your own samples and methods
  • A quote fixed for your number of laboratories
  • A pilot on real samples before production use

Start with your own method.

Tell us about your lab. We prepare a trial workspace and email you the access, usually within one working day.

  • The full product, no feature limits
  • Sample data to explore on day one
  • No card and no commitment

Start your free trial

30 days, the full product, no card. Confirm your e-mail and we prepare your workspace.

Start your free trial

Prefer to see it first? Request a walkthrough below.

Tell us about your lab

What would you like?