The platform under every LabMission application
Connections, data streams, queries, dashboards, agents and your own code, governed by provenance and access rights and reachable through APIs and an MCP server. Your team works on it on a visual canvas, an agent works on it through MCP, and both go through the same review.
- HTTP
- MQTT
- WebSocket
- IoT hub
Applications inherit rather than reimplement
Attribution, audit, access control, retention and change control belong to the platform. Every application, every agent and every workbench inherits them, so your quality team learns them once.
- Compliance behaviour belongs to the platform, so every application behaves the same way
- One data model underneath, so information moves between applications without a project
- New capability arrives for every application at once
- What your quality team learns about one application holds for the next
- PeopleThe canvas and the applications
- AI agentsThe MCP server
- CodeThe API, SDK and workbenches
All three work through the same proposals, rights and record.
- Connections
- API sources
- Simulators
- Files & manifests
- Live streams
- Queries
- Data stores
- History & export
- Surfaces
- Interfaces
- Agents
- Workbenches
- Provenance
- Access rights
- E-signatures
- Change control
What a LabMission workspace is made of
Each block is a node on the workspace canvas. People place them by hand, agents propose them, and code deploys them, and all three are reviewed the same way.
Connections
Receive data as it happens, over HTTP, MQTT, WebSocket or an IoT hub.
Learn moreAPI sources
Poll a REST API on a schedule, with bearer, API key or basic auth, and map the response.
Learn moreSimulators
Generate realistic data to build and test a flow before the instrument arrives.
Data streams
Every reading is an event, time-stamped and attributed to the source that sent it.
Learn moreQueries
Named queries over live and recent data, each one publishable as its own API.
Data stores
Governed tables with rights down to who can read, create, update or delete.
Surfaces
A scope that groups connections, queries, agents and interfaces around one job.
Interfaces
Dashboards and screens bound to queries and actions, written as a spec or as code.
Agents
Agents that run inside a surface, plus any external agent through the MCP server.
Learn moreWorkbenches
Your own code from a repository or package, run in your workspace under its rights.
Learn moreAccess rights
Rights and role configurations, held as records you can review and propose.
Learn moreProvenance
Events, amendments and signatures, hashed into a chain and kept in immutable storage.
Learn moreHow every change becomes evidence
Provenance is configured per workspace: the hashing algorithm, whether approval and a second person are required, whether the before-and-after state is captured, and how long records are kept.
- 01A changeBy a person, an agent's approved proposal, or a process
- 02Its reasonFrom the reason categories you define
- 03Its signatureReview, verification, approval, authorship…
- 04Hashed & chainedSHA-256, 384 or 512, linked to the last
- 05RetainedImmutable storage, for up to 400 years
Rights, roles and people, in three layers
Access rights say what can be done. Configurations bundle rights into roles. Access cards give roles to people and teams. The same layers govern people, agents and workbenches.
Everything on the canvas is also an API
Workspaces, access, data stores, files, queries, live streams, history, provenance and licensing are all reachable over a REST API, described by a generated OpenAPI spec.
Three ways to run LabMission
Evaluation
A workspace provisioned for you, to try with your own data.
Fully managed
We run and operate the platform so your team can focus on the science.
Your own cloud
Deployed into your own Azure subscription through a landing zone: key vault, logging, monitoring and a data-residency policy.
Platform capabilities, one page each
Audit Trail & ALCOA+
The record is made as the work happens.
Electronic Signatures
Approvals that mean something, and say what they meant.
Roles & Access
People see the work they are entitled to, and nothing else.
Configuration & Change Control
Your quality team reads the system, not a description of it.
Connectivity
Connect the lab systems you already have.
Real-Time Operations
Records tell you what happened. Operations need what is happening.
Compliance & validation
How the system reaches and holds a validated state.
See the platform underneath a real application
We'll walk a live workflow in Sample Management and open the workspace behind it: the connection, the query, the proposal and the record.