VRTLST Edge v2 ships with on-device inference at 38 ms

Read more

VRTLST Command

Every camera, every site, one screen

Command is the control plane. Once you are past the first line, the hard part is not the model — it is knowing which model version is on which camera at which site, and who changed it. Command is where that lives.

COMMAND 4 SITES · 212 CAMERAS · 6 MODELS all healthy
PLANT 1
PLANT 2
PLANT 3
DEPOT
LINE A
LINE B
DOCK 3
GATE A
PLANT 3 Inspect model drift · retrain suggested review

What it does

The dashboard that unifies it all

01

Staged rollouts

Push a model version to a group, a line, a site or the whole estate. Every deployment is reversible from the same screen.

02

Drift detection

Command benchmarks each deployment against its own history and flags the ones sliding, before anyone on the floor notices.

03

Access and audit

SSO, role-based permissions, and a complete record of who deployed what, where, and when.

How it works

From a camera to a decision

The control plane for your whole visual estate — deployments, model versions, alerts, access and audit.

  • Roll a model to 200 cameras, or roll it back
  • Cross-site benchmarking and drift detection
  • SSO, role-based access and a full audit trail
Book a demo
Connect the sites
Each plant, depot and air-gapped location reports into one estate view.
Group the cameras
Organise by line, cell or function so a rollout targets exactly the right set.
Roll out the model
Stage it, watch the health checks, promote it — or roll it back in one action.
Audit everything
Export the full change history for the quality system or the auditor.
212 cameras under management
4 sites in one estate view
1-click rollback on any deployment
SSO with role-based access

Specifications

The technical detail

What your integrator will ask for on the first call.

Scale
212 cameras across 4 sites, typical estate
Rollouts
staged by group, line, site or estate
Rollback
one action, any deployment
Drift
per-deployment benchmarking against own history
Identity
SAML · OIDC · SCIM provisioning
Audit
full change history, exportable

Getting started

How a Command deployment goes

The same shape every time, whichever product you start with.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. Ongoing

    It gets better

    Corrections accumulate, drift gets flagged, and new defect classes are a fine-tune rather than a project.

Questions

What people ask about Command

Something not covered? Talk to an engineer.

Do we need Command to run one line?

No, a single pilot line runs fine without it. Command earns its place at the second site, when knowing which version is where stops being something one person can hold in their head.

How does it reach an on-prem or air-gapped site?

Over a link you control for on-prem. Air-gapped sites are managed through signed model bundles that move on media, with the audit trail reconciled when they are applied.

What does drift detection actually measure?

Each deployment is benchmarked against its own history rather than a global baseline, so Command flags the line whose confidence distribution has moved, not the line that was always hardest.

Can we restrict who deploys to production?

Yes. Roles go down to the individual site, and deployment rights are separate from viewing rights.

Keep exploring

The rest of the stack

See the whole platform
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

Get started

Point it at a camera. See what it sees.

Send us one hour of footage from one line. We'll come back with what the model found in it.