Prova
Safety rules on the camera itself, and an audit pack that proves what happened.
Prova installs as an application on Axis cameras you already run. Rules are applied on the device against the camera's own scene metadata, each incident is signed where it happens, and the video never leaves the camera at all. Prova Cloud keeps the evidence registry and produces the audit pack an HSE manager hands to a labour inspector, an ISO 45001 auditor or an insurer. It runs today on a camera in a laboratory; the first installation on a working site is still ahead, and the page says which parts that leaves unproven.
Prova
Features
An application on the camera, not another box
Native code on the camera itself, reading the scene metadata the camera already produces through its Device Data Hub interface. Nothing to rack, nothing to power, no second appliance in the cabinet — and no detection model of ours that would need retraining and shipping to you.
The video never leaves the camera
An application on a camera has no video pipeline, no GPU and no storage of its own, so there is nothing to stream. What travels is a signed incident and a small anonymised crop measured in kilobytes, against the megabytes a clip would cost. That changes retention, backup and hosting by three orders of magnitude, which is why it is a design decision rather than a setting.
No identity, and no field to put one in
An incident carries a class, a short-lived track id, geometry and a time. There is no field for a face, biometrics, clothing colour or a per-person score, and the attribute data the camera offers is dropped at the boundary rather than stored and ignored. People are pixelated on the camera before an image is written, by a policy set per site.
Signed where it happens
A key created on the camera signs each incident and each image, and the registry pins that key the first time it sees the device. If the key changes the node is disabled until a person re-enables it. Changing a value after the fact makes the record fail verification — proven by replaying a real signed incident with one number altered and watching it be refused and recorded as refused.
The audit pack is the deliverable
A PDF mapped to the ISO 45001 clauses an auditor works from and to the EU Machinery Regulation: what happened, where, how often, the evidence hash of every record, and the anonymisation policy that was applied. Generated from the registry rather than written by hand, so it says what the records say.
Ask a question, get a number you can check
A question becomes a query the registry runs. The model never sees the evidence and never produces a figure itself, so a wrong number is not a shape the system can express. Every answer carries its row count and up to five incident ids, and an answer of zero is an answer about the records rather than proof that nothing happened.
Who it's for
For the person who has to prove it, not only see it.
Sites where a safety claim has to survive an inspection, an insurance review or a surveillance audit — and where the cameras on the wall are already Axis cameras.
HSE and safety managers
The person who owns the corrective action and has to show, months later, what was done about it and on what evidence.
Auditors and inspectors
ISO 45001 surveillance, a labour inspection or an insurer's review, where a claim with no verifiable record behind it is a finding rather than a reassurance.
Sites already running Axis cameras
Prova adds software to cameras that are already installed and already detecting. There is no additional hardware in the purchase.
Where it stands
In a laboratory, not yet on a site — and specific about the difference.
This is the newest thing we have published. The honest description of a product this young is a list of what has been proven and where, so here is that list rather than a launch announcement.
What runs today
Both halves run. Rules are applied on the camera, incidents are signed and queued, the queue survives a restart and a lost connection, and the registry produces a real audit pack whose hashes verify.
Where it runs
On one AXIS Q3548-LVE in a laboratory, and on a server of ours. There is no customer installation, no pilot on anyone's site, and nobody has bought it.
What a laboratory cannot show
The test scene is a wall and a screen. Objects in it fall below the camera's own minimum size for classification, so the rules that need a person or a vehicle are proven on a workstation rather than on the device. A scene with real traffic is the next step, and it is the one that matters.
On Axis
Prova is built on the camera application platform and the metadata interface Axis publishes for that purpose. It is not a partnership, an approval or a certification, and it is not part of any Axis partner programme; an application to one is pending and nothing follows from it yet.
Measured, not claimed
Three things that were tested by breaking them.
Deliberately none of them is a detection figure. The detector is the camera's own and the test scene has nothing in it worth detecting, so any accuracy number here would be measuring a wall.
A tampered record is refused, and the refusal is kept
A real signed incident was replayed with a single value altered. It was rejected and the rejection was written to the audit trail. A signature nobody tries to break is a claim; this one was tried.
The queue outlives the connection
With the network gone the camera keeps recording incidents to a queue that survives a restart of the application, retrying on a widening interval rather than hammering. The buffer has a stated ceiling of roughly two and a half days at the rate the laboratory produces, and reaching it is reported rather than hidden.
Restore drill: six seconds
An encrypted backup restored into an isolated instance in a drill that runs weekly, rather than a backup job whose output nobody has ever read back. Six seconds to restore, with one row of loss at worst.
Join the Prova waiting list.
Tell us about your site and the problem you want solved. We reply within one business day and say plainly where the product stands today.
Prova
Tech stack
- Axis ACAP (native C)
- Device Data Hub
- Ed25519
- FastAPI
- PostgreSQL
- PDF audit packs
FAQ
Frequently asked questions
Do we need new cameras or another box?
No new box, and in most cases no new cameras. Prova is software installed on Axis cameras you already own, and it uses the scene metadata those cameras already produce. The condition worth knowing before anything else is the firmware: the metadata interface it reads is only stable from AXIS OS 12.8 onwards, so a camera older than that is not a candidate until it is updated.
Does any video leave the site?
None, and not as a policy that could be changed. An application running on a camera has no video pipeline, no GPU and no storage of its own, so there is no stream for it to send even if someone asked it to. What leaves is a signed incident record and a small anonymised crop.
Is this facial recognition, or scoring our staff?
Neither, and the data contract is where that is enforced rather than a setting. An incident has a class, a short-lived track id, geometry and a time, and no field for a face, biometrics, clothing colour or a per-person score. The attribute data the camera itself offers is discarded at the boundary. People are pixelated on the camera before an image is stored, and a site can only relax that after its own assessment.
Is Prova an Axis partner product?
No. It is built on the camera application platform and the metadata interface Axis publishes for third-party software, which is what those interfaces are for. It is not a partnership, an approval or a certification, it carries no Axis endorsement, and an application to the partner programme is pending. We will say so here when that changes and not before.
How ready is it, honestly?
Young, and running. The camera application and the cloud registry both work: rules on the device, incidents signed and queued, a queue that survives restarts and outages, and audit packs whose hashes verify. What does not exist is a customer. There is no installation on a working site, no pilot, and no buyer, and the rules that need to see a person or a vehicle have been proven on a workstation rather than on the camera, because the laboratory scene has neither in it.
Have a project in mind?
Tell us what you want to build. We respond within one business day.
Built by an EU-incorporated senior team — 20+ years in enterprise delivery.