Downloads
Very little of the ForensicsGuard platform is a public download, and that is deliberate. This page sets out exactly what anyone can obtain here, what is provided to organisations evaluating the platform, and what is only ever delivered directly to an identified customer.
Public
Two things, both of which are meant to be public — one because it describes the platform, the other because it is what lets you check the platform without trusting us.
The commercial overview: what each component does, how they work together, and where the platform fits. It is sent on request rather than posted as a standing file, so what you receive is the current version rather than whichever one was last uploaded.
The public keys and the detail needed to verify ForensicsGuard signatures — releases, integrity manifests and licences — offline, with standard cryptographic tooling. These are published because verification that depends on us is not verification.
On request
Technical material is obtained through a conversation, not a download button. That way it reaches a named organisation for a known purpose, and arrives with the context needed to read it correctly.
If you are assessing the platform for procurement or security review, ask for what you need to establish and we will tell you what exists and what we can provide under NDA.
Boundary
The following are not offered as downloads here or anywhere else. They are delivered directly to identified customers as part of a deployment.
Two reasons, both substantive. The first is authorisation: ForensicsGuard is built for lawful, authorised investigation, and a public download is by definition issued to no one in particular. Delivering to identified customers is what keeps the platform's intended use enforceable rather than merely stated.
The second is attribution. Evidence is attributed to a specific appliance running specific software. A deployment that arrived through a known channel, bound to a Guardian ID and verifiable against a signed manifest, can be accounted for later under challenge — which is the only condition in which any of this matters.
None of it is security by obscurity. Everything needed to verify what you have been given is published: the public keys and the verification contract are at verification & updates, and they are meant to be public. What is withheld is distribution, not the means of checking.
At a glance
The same boundary in one table, so it can be read without reading the page.
| Material | Availability | How it is obtained |
|---|---|---|
| Product brochure | Public | On request — contact us |
| Public verification keys and verification contract | Public | Published at verification & updates |
| Technical documentation | Evaluating organisations | Under NDA, on request |
| Deployment guidance | Evaluating organisations | Under NDA, on request |
| Datasheets | Evaluating organisations | On request |
| Guardian appliance images | Customers only | Delivered as part of a deployment |
| Lab Station installer | Customers only | Delivered as part of a deployment |
| Mobile Sensor builds | Customers only | Delivered as part of a deployment |
| Licences | Customers only | Issued against a specific Guardian ID |
| Source, signing and release tooling | Not distributed | Held outside every deployed system |
The wider index of published and forthcoming material is on the resources page. If you already run ForensicsGuard, software reaches you through your deployment rather than from here — see support.
Tell us what you are evaluating and what you need to see. We will tell you what is public, what exists under NDA, and what is only ever delivered as part of a deployment.