Test integrity and your data
It reads. It does not interfere.
Your data stays yours.
Nothing is installed on a qualified setup, nothing is written into your instrument, and nothing leaves your network unless you send it. Those are design constraints, not settings.
What it does on your rig.
Read-only to start
No keystrokes into a qualified rig until you turn action on, per rig. Off is the default and stays the default until you change it for one specific bench.
The screen and the signals, nothing else
No files, no network into your instrument, no agent on the test PC. It sees what the operator sees.
Nothing to re-qualify
Because nothing is installed on the setup, the qualification you already hold is not disturbed. That is usually the difference between a pilot this quarter and a pilot next year.
Air-gap friendly
Works on isolated networks and on old software nothing can be installed onto. If the rig has never been on a network, it still does not need to be.
What happens to what it sees.
Local-first
Capture lands on the box. Nothing leaves your network unless you send it.
On-prem or your server
Weave runs where your data is allowed to be, including an isolated network.
Audit trail
Every Observation is timestamped and linked to the exact config and telemetry it came from, so the evidence chain holds when someone asks months later.
You set access and retention
Who can see what, and how long it is kept.
What it will not do.
Worth stating plainly, because it is what you will be asked in review.
It does not install software on your test PC.
It does not write files to your instrument or its storage.
It does not open a network path into your rig.
It does not send images or captures off your network on its own.
It does not send a keystroke to a qualified rig unless you turned action on for that rig.
It does not need your vendor's cooperation, a driver, or an API.
What you can see and pull.
The box serves its own page, so what it is configured to do is readable from a browser rather than taken on trust. Every alert quotes what it saw and why it fired. And it is a box on a shelf with a cable: the most complete control is still the one you can perform with your hand.
Where it is built.
Designed and built in India, and it does not depend on a vendor cloud to function. For buyers with jurisdiction or supply-chain constraints on their test infrastructure, that is worth raising early rather than discovering at procurement.
Bring it to your change-control review.
A pilot starts read-only on one rig. If review wants the detail before that conversation, ask and we will send it.