What OpsLink is

OpsLink is the operator’s menu, off the coin door. It is a web page served by the cabinet itself, so anything on your network with a browser can drive it.

This is the phone's whole job

vPinOps runs on Windows, macOS and Linux — not on phones or tablets. Your phone’s part in a virtual-pinball setup is to be the remote, and OpsLink is how it does that. Nothing to install on the phone. Nothing in the cloud. It is a local web view onto the cab’s own service.

What you can do from it

Browse the library

Every table, its art, its state — validated, unchecked or held with a reason.

Launch a table

Pick it on the phone, it starts on the cab.

Import

Send a .vpx, .vpxz, .directb2s or an archive from the device you are holding, then run the usual import with previews and name choices.

Settings

Paths, screens, the OpsLink password. The things you would otherwise crouch behind a cab to change.

Why the architecture is remote-first

The cabinet’s service is the real product; the front end on the cab’s own screen is one client of it. That is why the operator half works on all three platforms today while the wheel is still landing — the service does not depend on there being a wheel in front of it.

It is also why a phone, a laptop, an iPad and a wall tablet all work without a separate app for each: they are all just browsers.

What it is not

• Not a cloud service. There is no account, nothing is uploaded anywhere, and it does not work from outside your network — by design.
• Not an app. There is nothing to install on the phone.
• Not a second front end. It manages the cab; it does not play tables on your phone.

Next

• Connecting to OpsLink — the address, the password, and the firewall