Choose the first scene
Agree on one high-risk area: a freezer room, cryo storage area, gas utility, incubator group, equipment bay, or inventory workflow.
Products
Software, hardware, and edge response for regulated lab operations.
Products are organized around what a buyer can actually adopt: lab management software applications, AIoT hardware for physical signal capture, and the edge response layer (Sci-Edge) for local response when sites need offline continuity or edge intelligence.
Software applications
Guardian, Equipment, Inventory, Samples, Space, Procurement, Qualification, Waste
Daily operating modules that turn physical events into accountable workflows and audit evidence.
AIoT hardware Sensors, SciBox, gateways, meters, scanners, and workflow devicesConfigurable hardware that captures the lab conditions and actions software records usually miss.
Edge response layer Sci-Edge — offline-first continuity, local rules, agents, and edge AI computeOn-site intelligence for restricted networks, sensitive rooms, and offline-first deployments.
Product entry points
Start from the product surface your team is trying to buy.
A lab manager may begin with Guardian monitoring. QA may evaluate audit evidence and validation readiness. Facilities may start with hardware in freezer rooms, gas areas, or equipment fleets. IT may require the edge response layer (Sci-Edge) for restricted sites. The layers are separate entry points, but they compound into one physical context layer.
01
Lab management software
Applications teams can deploy by workflow.
Monitoring, equipment, inventory, samples, space, procurement, training readiness, and waste workflows.
02AIoT hardware
Physical signal capture by scene.
Cold storage, environmental monitoring, process monitoring, power, equipment, and inventory devices.
03Edge response layer
Local autonomy where cloud-first is not enough.
Offline continuity, local rules, protocol adaptation, edge agents, and on-site AI compute.
Typical first rollout
What happens after you decide to start.
A first deployment usually starts with one critical scene rather than the full platform. The goal is to get physical signals, response workflow, and the first audit-ready evidence packet operating around a real lab risk.
Map signals and owners
Confirm what needs to be captured, who owns alerts, which SOPs apply, and what record QA or EHS will need to review.
Deploy hardware and software
Install sensors, SciBox or gateways, configure Guardian and related modules, set thresholds, escalation paths, and user roles.
Produce the evidence packet
Review signal history, alerts, acknowledgement, corrective action, ownership, and exportable records before expanding to the next scene.
Software applications
The eight modules buyers expect to find under Products.
These modules can be adopted in phases. Most teams start from one high-risk scene, then add the adjacent workflows that explain what was affected, who responded, and which records survive review.
Guardian
Critical condition and safety-signal monitoring, alerting, escalation, response history, and audit-ready event evidence.
Equipment
Instrument assets, booking, utilization, maintenance, service records, and lifecycle governance.
Inventory
Reagents, chemicals, consumables, stock levels, expiry, SDS context, returns, and demand signals.
Samples
Sample location, custody, storage maps, handling events, exposure context, and retrieval history.
Space
Rooms, benches, storage zones, utilities, occupancy, environmental health, and site capacity context.
Procurement
Purchase requests, approvals, budget context, supplier activity, and demand tied to actual lab usage.
Qualification
Training, competency, authorization, renewal schedules, and role readiness tied to workflows.
Waste
Hazardous waste generation, labeling, storage, pickup, disposal, incident context, and EHS reporting.
Adoption logic
Start with one layer, then combine layers where the site demands it.
Products do not need to be deployed as a big-bang suite. A customer may start with Guardian and a freezer room, add inventory or sample context, then introduce Sci-Edge where data export, network continuity, or local response requirements make edge deployment the better path.
Start with software
Use Guardian, Equipment, Inventory, Samples, Space, Procurement, Qualification, or Waste when the immediate need is operational control.
Start with hardware
Use AIoT hardware when the first gap is physical evidence from cold storage, gas, equipment, rooms, utilities, or inventory actions.
Start with the edge response layer
Use Sci-Edge when restricted networks, sensitive data, local rules, or offline continuity shape adoption.