What changed, and does it matter?
Each run is compared with the last, and every difference is explained.
Tesryn Lab · Security
Watches a machine that runs AI, explains what changed, and never touches a thing.
In use at Tesryn First built for workstations and servers that run AI around the clock · 2026
01 — What it is
Every few minutes it takes a sealed, tamper-evident record of what's installed, running, listening and reachable, and compares it with the last one. It explains every difference in plain terms, maps it onto who is supposed to be able to reach what, and flags what needs a person. Secrets are removed before anything is written down.
The moment it earns its keepA package changes on a machine nobody touched over the weekend, and Monday morning starts with the explanation rather than the discovery.
What it proves we can do
02 — What it can do
Each run is compared with the last, and every difference is explained.
Records are sealed and chained, so any alteration shows.
Maps what it sees onto the boundaries that are meant to hold, and flags any crossing.
Runs on a schedule with no special privileges and no extra software.
03 — How it connects
The same things we know how to do keep coming back in different industries. This is where this one sits: what it proves, and what else proves the same thing.
Sealed, verifiable records Work that writes down what happened in a way nobody can quietly edit later. Also proved by Podcast Maker, Magnetic Digital Twin, CAD Workbench, Tesryn Launch.
Watching without touching Systems that can detect and explain but hold no power to change what they watch. Also proved by Capability Distillation.
Runs on hardware you control Models and data that never have to leave the building when the material is sensitive. Also proved by Podcast Maker, Engineering Library, Command Center, Research Runtime.
The whole map — six sections, and everything that proves them.
04 — What it's held to
What it isn't. Not an antivirus and not a firewall. It tells you what's true so you can act.
05 — The recipe stays in the lab
Yours would be your own build, on your systems, and you'd own it outright: code, documentation, no lock-in. What we bring to it is the practice — we've solved this shape of problem before, so you're not paying for the first attempt. The method stays ours. And if what you need isn't here at all, that's the usual case — it's how every skill on this page started.