CONTROL · AIVQC Server

No model version reaches the line without approval.

Server is the control point between engineering work in Trainer and real inspection on the line — it publishes only approved versions, and only to the stations you select.

Without a central publishing point, every production station could over time end up running a different model version — with no record of who put it there or when. Server prevents that: it runs as a local deployment (Docker or NAS) inside the plant network and distributes packages only to the stations you point it to.

Access to publishing new versions is controlled — not everyone with network access can change the model running on production. Every publication is recorded in a history, so a question like "which version was running on line 3 last week" has an immediate answer.

Server needs no cloud. Images, datasets and models never leave the plant network, publishing and inspection work without the Internet, and you activate the licence online or fully offline, with a file.

Local deployment

A Docker container on a Linux server, Synology NAS or Windows — inside the plant network, with no ports open to the Internet.

Access control

Publishing a new model version is restricted to authorised people, not every network user.

Release history

A full record of which version went to which station and when — the basis of inspection traceability.

Target station selection

Every package reaches only the selected Production stations, not every device on the network at once.

PACKAGE PATH

From the Deploy button in Trainer to an active recipe on the line.

Server does more than pass files along. At every step it checks who is sending, where to and what exactly — and every step stays in the history.

01
Publish
Trainer sends a verified .aivqcpkg package to a selected station on a selected line.
02
Verify
Server checks the sender's identity, limits and the package contents before accepting it.
03
Deliver
A station downloads only the packages assigned to it — never another station's.
04
Acknowledge
Production re-checks the checksums and confirms activation; the acknowledgement is recorded on Server.
05
History
Who, what, when and to which station — with the option to revoke a package or disconnect a station.

INSTALLATION

Runs on hardware you already have on site.

Server is a Docker container. The same signed installation bundle runs on a Linux server, a Synology NAS or a Windows computer with Docker Desktop. The installer checks the system and explains each step, and you finish the rest — site name, certificate, licence acceptance and the first Trainer code — on a setup page in the browser.

Container images for x86 and ARM processors, cryptographically signed — the installer checks that you are running exactly the released version.
A read-only container with data in one directory: the SQLite database, packages on their way to stations and the Server identity.
Encrypted daily backups with a recovery key and retention, and restore from the setup page.
Automatic updates in a maintenance window — with a backup before the change and rollback to the previous version. You can also require approval or get notifications only.
Health probes (alive / ready) for the monitoring you already run.
Package size limits, a storage quota and a free-disk threshold — Server will not silently fill the machine it runs on.

OFFLINE MODE

A small site? Server fits on the Trainer computer.

Not every plant has a server or a NAS. In offline mode, AIVQC Local Server installs together with Trainer as a Windows service and serves one Trainer workstation and up to three inspection stations — no separate computer and no Docker.

The service starts with Windows, so stations need the computer switched on, not Trainer open. When the site grows, you move it to a full AIVQC Server — with or without pairing the stations again.

The Trainer installer sets up the service and firewall rule itself, and you accept the licence once for both.
The local Server updates together with Trainer, always with a backup before the change.
The offline-mode panel shows the service state, stations and backups, and warns when Windows treats the network as public.
A site without Internet exchanges status and activation as files — on removable media, with no network connection.

SECURITY

Everyone has their own key and access only to what they need.

Trainer, each Production station and the administrator have separate identities and roles. A station cannot see another line's packages, and nobody outside the list can publish a model to production — even with access to the plant network.

Connection with a one-time code. The station shows which line and station it is connecting as, and the Server certificate fingerprint is compared before confirming.
Permanent credentials go straight to the application and are stored in Windows Credential Manager — the installer never displays them.
HTTPS only, on the local network. The Server port is not exposed to the Internet.
Revoke a package or disconnect a station with one command, recorded in the history.
Request and upload limits protect Server from accidental or deliberate overload.

Identity	Can	Cannot
Trainer	Register stations and publish packages	Learn station credentials or change the Server identity
Production station	Download assigned packages, acknowledge activation, send reports and images	Download another station's package
Administrator	Revoke packages, manage licensing and pairing, review reports	—

NO CLOUD

No cloud. And no Internet doesn't stop the line.

Inspection, package publishing and history run entirely on the plant network. An optional, encrypted sync with the AIVQC Relay service delivers only the licence and signed updates — it is outbound only, Relay never connects into your network, and images, datasets and models are not transferred.

A site without Internet access? You activate fully offline — with a request file and a response file. And if the connection drops during operation, publishing and inspection continue on the last signed licence.

Application updates are signed, and a station never installs them during inspection.
A licence change never alters the result of an inspection in progress.
A station without a Server connection keeps working on its stored activation, while results and reports wait in a local queue. The operator sees which computer needs switching on, and the station gives advance notice before its licence ends.

IMAGES AND REPORTS

Difficult line images go back to the engineer, not to a cloud.

A technician at the station collects images — for example only NOK or low-confidence results — and sends them with one click through Server to an inbox in Trainer, with a comment for the engineer. After import the bundle is removed from Server: Server does not become a permanent photo store.

Bug and suggestion reports from the applications work the same way: they reach Server with filtered logs, and without a connection they wait encrypted in an offline queue. Only the administrator can access them.

PLACE IN THE PLATFORM

Server is the gate between Trainer and Production.

Server receives approved packages from Trainer and delivers them to AIVQC Production on selected stations. A Production station keeps a local copy of the last verified package, so inspection can continue even during an interruption in the connection to Server.

FAQ

AIVQC Server

Does Server need a dedicated server?+

No. A typical deployment is a Docker container on an existing Linux server, a Synology NAS or a Windows computer with Docker Desktop. At a small site — up to three stations — Server can run in offline mode as a service on the Trainer computer.

Does Server need Internet access?+

Not for daily work. Package publishing and inspection run on the plant network. The outbound connection to AIVQC Relay is for licensing and updates, and without it you can activate offline with a file.

Does Server store our datasets?+

No. It stores only what is operationally needed: packages on their way to stations, acknowledgements, history and reports. Line images wait on Server only until they are imported in Trainer.

What happens if a production station loses its connection to Server?+

Production uses the last locally stored, verified version and continues inspecting. The connection to Server is needed to publish new versions, not for ongoing operation.

AIVQC PILOT

Try it on your own line.

Start with a 30-day pilot on one station and see the result on images of your own product before you decide on deployment.

Have a quality engineer and IT staff? Your own team can deploy AIVQC — you pay for a licence, not for integrator hours. Sign up for the beta →

1 Trainer · 1 station
Up to 3 defect classes
30 days + free extension
No cloud

Join the pilot →Deploying with your own team