The instrument sits outside your workflow.
Your LIMS, ELN or proprietary lab platform needs results and status, but operators still move files or repeat steps in a separate application.
Connect / Instrument connectivity
Your instrument. Connected to the software around it.
A capable instrument can still be difficult to integrate. We build the interface between your instrument and the lab systems, automation platforms or AI agents that need to use it.
connect / Conceptual model
The customer problem
Where the next capability gets blocked.
The available interface does not fit.
A vendor SDK, REST API or SiLA 2 server exposes part of the capability. Your integration needs a consistent command model, long-running operation handling and useful errors.
The only path is through older software.
An undocumented interface or vendor DLL may be the starting point. You need to establish what is accessible before committing to a replacement control layer.
What we build
A useful scope.
A reviewable result.
Start with one instrument and one target workflow. We define the integration around the operations you need, the interface you can access and how the receiving system behaves.
- 01
An interface that fits your environment
A scoped adapter or service using the suitable API, vendor SDK, REST/OpenAPI, SiLA 2 or PyLabRobot integration. MCP can expose selected capabilities to a compatible agent client.
- 02
Workflow and data integration
Map commands, results, identifiers and instrument status to your LIMS, ELN or proprietary system. Define ownership of authentication, scheduling and data exchange.
- 03
Reliable operation handling
Implement agreed timeouts, errors, cancellations and recovery behavior. Distinguish an accepted command from completed execution and an unknown result.
- 04
Proprietary-interface investigation
For customer-authorized work, assess available SDKs and DLLs, observe communications in a controlled setup and reconstruct the required interface where feasible. A replacement host control layer is scoped separately from instrument firmware.
Relevant engineering
Our OpenAPI-to-SiLA 2 work provides a concrete example of translating an existing API into an instrument integration interface.
Before we start
A few practical questions.
Do we need SiLA 2 to work with you?
No. We select the integration around your instrument and target software. An existing REST API, vendor SDK, SiLA 2 server or another accessible interface may be appropriate. MCP is an additional option when an AI agent needs access.
Can you integrate an instrument with proprietary software?
We can scope customer-authorized investigation and integration where documentation is limited. We first assess available APIs, SDKs, DLLs and observable communications. Feasibility depends on the instrument, access and required operations; the first deliverable may be findings and a recommendation rather than a complete driver.
Can you replace the control layer?
Where feasible, we can build a host-side control service and application around the required instrument operations. Firmware changes, hardware modifications and broader device qualification need a separate assessment and scope.
What do you need to scope an integration?
The instrument and software versions, the task you want to automate, available documentation or SDKs, your target platform and access to a test environment. If something is unknown, we make its investigation part of the first milestone.
Your next project
What’s next for your instrument?
Tell us what you want to connect, simplify or automate. Let’s define the first useful step together.