DE EN
Request a demoHome Documents
DocumentsThe product profile and the technical note your IT will ask for. No registration, no email address. The documents are the point, not the lead.
Nine pages, A4. Three parties and what each of them needs, then two pages on each of the three areas - Analyzer, Testbench and Monitoring - with the screenshots at a size you can read, and how a first run starts.
One vehicle, one small site, a capture of four minutes. Enough to import a layout, analyse a log and read a verdict without asking anyone for data first. Three findings are in it on purpose, and the guide inside says which and why.
A report can be exported as one signed archive holding the report and every file it was made from. The public key, a verification script and the full instructions are on their own page, so anyone handed a package can check it without our help.
This document names every place the analyzer departs from the schemas as published, with the commit it was checked against, the passage it rests on, and the reason.
Five pages, A4. Ten deviations in three classes, each traced to a release-branch commit and to the clause that governs it, including the specification's own rule that its text outranks its schemas. Re-verified against the official repository on 14 August 2026.
A conformance verdict is worth what its rule set is worth. Where we cannot use an official file as published, you are entitled to know it before you rely on a report, not to find it in a diff. Every deviation is dropped as soon as the published file no longer needs it: the generator checks each one against the original before every run.
For your site administrators: the three ways to connect, the exact firewall rule each needs, what the analyzer does on the broker and what it never touches, how the connection is encrypted and what the licence file does on your own hardware. Plus a form to fill in with the details we need to connect.
When your MQTT broker runs on a machine that is not reachable from the internet, one outbound SSH tunnel connects it to the hosted analyzer; nothing to open on your side. Step-by-step for Windows and Linux.
The developer's guide to rules of your own: what a ruleset can express and what it deliberately cannot, the file format and the path language in full, all seven rule types with examples, and how to test a file against a real capture before it goes to production.
If your security review needs a document that is not here, such as an architecture note, a data-protection summary, a test report: just ask, and it gets written.