Cloud
Managed by us
Fastest to stand up. Streams are processed in your region, models are managed for you, and nothing is shared across tenants.
The platform
One stack, from the sensor to the dashboard
Six products that were designed together rather than acquired separately. Vision is the engine, Edge is where it runs, Inspect, Guard and Watch are what it does for you, and Command is where you steer the whole thing. Nothing to stitch together.
Architecture
How the pieces stack up
Read it from the bottom. Everything rests on the edge runtime, and everything above shares the same model.
Command
Control plane · fleet · access · audit
Inspect
Defect detection
Guard
Safety & security
Watch
Monitoring
Vision
Detection · segmentation · tracking · classification
Edge
On-device runtime · cameras · gateways · air-gapped sites
Layer by layer
Four layers, one model
The reason a defect model and a safety model agree about what they are looking at is that they are the same model, looking once.
Book a demo- Edge is the floor
- The runtime that turns a camera into a sensor — on a device, a gateway or a plant server. Everything above it runs on top of this.
- Vision is the engine
- Detection, segmentation, tracking and classification. One model stack, shared by every product above it.
- Inspect, Guard and Watch are the jobs
- Each takes what Vision sees and turns it into a decision a plant can act on — a verdict, an alert, a metric.
- Command is the steering
- Which model version is on which camera at which site, who changed it, and how to put it back.
Where it runs
Three deployments, one codebase
The same model artefact runs in all three. Moving between them is a deployment decision, not a rebuild.
On-prem
Inside your network
A plant server runs the stack behind your firewall. Command reaches it over a link you control, and frames never leave the site.
Edge & air-gapped
On the device itself
Inference runs on the camera. The air-gapped configuration has no outbound connection at all — models arrive by hand and stay put.
How it goes
From one camera to the whole estate
Every deployment we have run follows the same shape. Nothing here needs a data-science team on your side.
- Week 0
One hour of footage
Send us recorded video from a single line. We come back with what the model found in it — before anyone signs anything.
- Week 1–2
One line, one model
We stand up a pilot on the line that hurts most, using the cameras already mounted. Operators start correcting it on day one.
- Week 3–4
Wired into the line
The verdict moves from a dashboard to the PLC, the MES or the alerting channel your shift leads actually watch.
- Month 2
Second line, second site
The model and its thresholds travel. Command stages the rollout so a bad version never reaches more than one line.
- Ongoing
It gets better
Corrections accumulate, drift gets flagged, and new defect classes are a fine-tune rather than a project.
Security
Built for IT to say yes
Vision projects die in security review. These are the four answers that get asked for every time, and they are architectural rather than contractual.
Your footage never trains our models
Not on any plan, not in any deployment. There is no shared model that has seen your floor.
Air-gap is a supported mode
Not a workaround. Models arrive on media, inference runs locally, and nothing dials out.
Faces blurred at capture
Blurring happens before the frame is written anywhere. There is no identity index to leak.
SSO, RBAC and a full audit trail
SAML and OIDC, roles down to the site, and an exportable record of every change.
Integrations
Fits the stack you already run
VRTLST is a sensor and a decision, not a replacement for your control system. It writes into what you have.
Control layer
- OPC UA
- Digital I/O
- Modbus TCP
- PROFINET
- EtherNet/IP
Plant systems
- MES
- SCADA
- Historian
- ERP
- CMMS
Data & messaging
- REST
- MQTT
- Webhooks
- S3 / Blob
- Kafka
People
- Slack
- Teams
- PagerDuty
- SMS
The products
All six, in one place
Vision
One model that understands every camera you own
Detection, segmentation, tracking and classification from a single deployment — no per-camera retraining.
Explore Vision Inspect
Catch the defect before it leaves the line
Sub-millimetre surface inspection at line speed, with a decision the PLC can act on.
Explore Inspect Guard
Every zone watched. Every rule enforced.
Draw a boundary once. Guard enforces it on every shift, on every camera, without a human staring at a wall of screens.
Explore Guard Watch
Know what's happening the moment it happens
Continuous monitoring across every line and every site, with alerts that reach the right person in seconds.
Explore Watch Edge
The camera that thinks for itself
A sealed edge-AI device that runs the full VRTLST stack on-board. Single PoE cable in. Decisions out.
Explore Edge Command
Every camera, every site, one screen
The control plane for your whole visual estate — deployments, model versions, alerts, access and audit.
Explore Command