Device-Based Licensing for Lab Software, Explained

Licensing is the part of a software purchase nobody wants to read and everybody ends up arguing about. For laboratory software it matters more than usual, because a lab does not grow the way an office does. You do not hire ten people and need ten logins. You add an analyzer, retire another, move a third to a different bench, and the number of people looking at the screen barely changes.

This guide explains the three common licensing models, why device-based licensing fits how labs actually work, what happens when your instrument fleet changes, and what to check about offline and air-gapped environments before you sign anything.

The Three Licensing Models You Will Meet

Almost every lab software quote falls into one of three shapes. Knowing which one you are looking at is half the negotiation.

• Per-seat (per-user). You pay for each named person or concurrent session. This suits software that people sit in front of all day, such as a full laboratory information system with order entry, validation and reporting screens.
• Per-site (enterprise). One price covers a hospital or a group. It is simple to budget, but you often pay for capacity you never use, and a small clinic can find itself priced like a hospital.
• Per-device. You pay for each machine the software runs on, or for the instruments it connects. The cost follows the thing doing the work.

None of these is universally right. The question is which unit in your lab actually scales. For an interface layer that sits between analyzers and a hospital system, the unit that scales is the machine and the instruments attached to it, not the number of people who log in.

Why Device-Based Licensing Fits Lab Reality

Consider what middleware does. It runs quietly on a workstation or a small server, holds connections to your analyzers, parses what they send, and delivers results to your HIS or LIMS. Most staff never open it. A per-seat model would charge you for people who never use it and say nothing about the part that actually carries load: the connections.

Device-based licensing lines the cost up with the work. A lab with one workstation and three analyzers has a small footprint and a small bill. A lab with a second workstation in another department adds exactly that. There is no penalty for hiring a night-shift technologist, and no surprise when a locum covers a week.

LISBridge works this way. It is a native desktop application, so each license is tied to a device, and the packages are tiered by the number of devices and the number of instruments you connect. Pricing scales with your lab's size, and plans are available for clinics, hospitals and distributors. For the details that apply in your region, see the pricing page.

What Happens When You Add or Retire an Analyzer

This is where licensing models are really tested. Instrument fleets change constantly: a hematology analyzer is replaced after seven years, a chemistry system is added when the clinic opens a new service, an older unit is moved to a satellite collection point.

Before you buy, ask the vendor three concrete questions.

1. What does adding an instrument cost, and does it need a new contract? If every new analyzer triggers a renegotiation, the licensing model is working against you.
2. What happens to the license when an instrument is retired? You should be able to reuse that capacity for its replacement rather than paying twice.
3. Can the license move between machines without a support ticket? Workstations die. A technologist's PC gets replaced during a refresh cycle. If moving a license means waiting days for the vendor, your results stop flowing while you wait.

On that last point, LISBridge supports self-service device unbind and re-bind. When a workstation is replaced, you release the license from the old machine and bind it to the new one yourself, with no ticket and no waiting. For a lab running 24 hours a day, that is the difference between a ten-minute task and a lost shift.

Adding instruments is similarly low-friction on the software side. With 37 instruments supported out of the box, including 17 that support bidirectional ordering, most analyzers you add are already covered. If you are mapping out which of your own instruments are supported, the device connectivity page lists the connection options for RS-232 serial, TCP/IP and file-transport analyzers.

Offline and Air-Gapped Considerations

Many licensing schemes quietly assume an internet connection. The software phones home on startup, checks a server, and refuses to run if it cannot reach it. That is a reasonable design for a web application. It is a poor one for a laboratory.

Labs lose connectivity. Rural clinics run on unreliable links. Some hospital networks deliberately isolate the instrument VLAN from the internet, which is good security practice. If your result pipeline depends on a license server being reachable, then an outage in someone else's data center can stop patient results from reaching the record.

Ask any vendor these questions directly:

• Does the software need to contact the internet to start, or only to activate?
• If the connection drops mid-day, does it keep running, and for how long?
• Can it be activated and operated in a fully air-gapped environment?

LISBridge uses offline license enforcement. License keys are validated locally, so an internet outage does not interrupt result delivery. Combined with crash-safe local storage that keeps results through a power cut or unexpected restart, the intent is that connectivity problems in the wider world never become missing results at the bench. If you want to see how the pipeline behaves end to end, how it works walks through the connect, parse, process and deliver stages.

Comparing Quotes Fairly

When you have two or three quotes in front of you, they rarely use the same unit, which makes them hard to compare. A practical way to normalise them is to write down your current and planned setup in a few lines: how many workstations will run the software, how many analyzers connect to each, and how many of those need bidirectional ordering. Then ask each vendor to price that exact scenario, plus one change, such as adding a fourth analyzer in year two.

Watch for costs that sit outside the headline number: separate fees per protocol or per instrument driver, charges for parser updates, or support tiers that gate basic fixes. A model that looks cheaper per device can cost more once those are added. Ask what is included in updates, too. In LISBridge, parser updates arrive silently in the background through WASM, with no restart and no downtime, so keeping current does not mean scheduling a maintenance window.

Frequently Asked Questions

Is device-based licensing cheaper than per-seat?

It depends on your lab. For middleware that few people log in to, device-based licensing usually tracks real usage more closely, so small and mid-sized labs often find it more predictable. It is worth modelling your own device and instrument counts rather than assuming.

What counts as a device?

Typically it is the computer running the software. Packages are then tiered by how many such devices you run and how many instruments you connect. Confirm the exact definition in writing before purchase.

What if my workstation fails?

You should be able to move the license yourself. With LISBridge you unbind the old device and re-bind the license to the replacement without opening a support ticket.

Does the software need the internet to keep running?

Not with offline license enforcement. Keys are checked locally, so a connectivity outage does not stop the application from receiving and delivering results.

Is there a way to try it before committing to a license?

Yes. There is a free trial that needs no credit card, so you can connect an instrument and see real results before deciding anything.

Start your free trial — no credit card required. lisbridge.com/pricing