VIDIZMO integration brief · Axon · vidizmo.ai/integrations/catalog/axon

Integrations / Axon

Axon

Redaction, search and camera AI alongside Axon, with results returned to Axon. Visit website

Axon Evidence is where many public safety customers keep body-worn camera, in-car and interview footage, and Axon Fusus is where their real-time crime centers bring live cameras, alerts and field units into one view. VIDIZMO is designed to work alongside both, adding redaction of video, audio, images and documents, search across a whole case file, and analytics on cameras that already feed Fusus, while Axon stays the system of record and the finished work goes back into Axon.

Redaction and Search That Return to Axon Evidence

Open as a two-page brief

This connector is not prebuilt. It would be built to the customer's requirement on the Axon Evidence Partner API, with scope and effort agreed per engagement. Axon Evidence is where many public safety customers keep body-worn camera, in-car and interview footage, and it stays the system of record throughout. VIDIZMO adds the work that often happens around it, redacting video, audio, images and documents for public records requests and discovery and searching Axon footage together with the other material in the same case, and then returns the finished work to the original Axon Evidence record.

How it connects

An administrator on the customer's Axon Evidence tenant creates an API access client under the security settings, which issues the client ID, secret and partner ID the connector uses, and the customer's Axon Evidence subscription needs to include partner API access, which their Axon representative can confirm. Scope is set by the customer, so only the evidence categories, cases or date ranges they choose are read.

Evidence comes across with the metadata Axon exposes, including officer, device, recorded time and case number, and the case number travels as a custom attribute so the reference holds on both sides. VIDIZMO records a SHA-384 hash when each file arrives and writes a custody entry for every action it takes. When the work is done, the redacted copy, transcript or production package is written back to the same Axon Evidence record as a derived asset, and the original is never altered.

What you can do together

  • Redact faces, license plates, screens, spoken personal information and document text across a whole release with Redactor, then return the redacted copies to Axon Evidence for release through the workflows the department already uses.
  • Search Axon footage together with 911 audio, phone extractions, CCTV exports and case documents in AI Intelligence Hub, asking questions in plain language and getting back the exact clip and moment, limited to the cases the person asking may open.
  • Hand prosecutors and discovery teams redacted, indexed productions that still point back to the original Axon record.
  • Run redaction and AI processing on premises or in an air-gapped network where policy requires it, with only the finished derived assets returned to Axon.

A scenario

  1. RequestA records unit receives a request for every body-worn camera clip, the 911 call and the incident report tied to a vehicle pursuit.
  2. ScopeThe unit selects the case, and the connector reads the Axon clips with their metadata.
  3. CombineThe 911 audio and the PDF report join the same working set, and the audio is transcribed.
  4. RedactRedactor finds bystanders' faces, plates and spoken personal information across the video, audio and report, and a reviewer approves each redaction with an exemption code.
  5. ReturnThe redacted clips, redacted report and transcript are written back to the Axon Evidence record as derived assets.
  6. ReleaseThe unit releases the package from Axon Evidence, with the full action history available on both sides.

What stays where

Axon Evidence remains the system of record

Originals, retention, sharing and the Axon audit trail stay in Axon Evidence.

VIDIZMO holds a working copy only for the job

The copy is kept under the customer's retention settings, with VIDIZMO's own custody log for every action.

Derived assets go back to Axon

Redacted copies, transcripts and production packages attach to the original record, and nothing is overwritten.

Processing runs where the customer chooses

VIDIZMO cloud, a government cloud, on premises or fully air-gapped, on a CJIS Security Policy-aligned architecture.

Products and solutions

Camera Analytics Into the Axon Fusus View

This integration is proposed and would be built with Axon Fusus. Axon Fusus is where real-time crime centers bring live cameras, alerts and field units into one view, and it already brings in alerts from technology partners. AI Live Insight would add detection on the cameras and video management systems a customer already has, sending each alert into Fusus so operators see it alongside everything else they watch.

How it connects

Fusus integrations are provisioned by the Fusus team, which issues the endpoint and credentials a partner sends events to. AI Live Insight reads existing cameras over RTSP or ONVIF, including estates on Axis, Milestone XProtect, Hanwha Vision, exacqVision, Avigilon and Verkada, runs detection on a server the customer controls, and would send each alert as an event with its location, camera and a short clip reference.

What you can do together

  • Show alerts for people, vehicles, license plates, weapons and zone entry from cameras that already appear in Fusus, without new camera hardware or changes to how those cameras record.
  • Tune detection per camera, by zone, schedule and severity, so operators see the alerts that matter for each location.
  • File the clip around an alert as evidence with retention and a custody record, so it can move into Axon Evidence with the rest of the case.

A scenario

  1. ScopingThe customer and Axon agree which cameras feed AI Live Insight and which alert types go to Fusus.
  2. SetupThe Fusus team issues the endpoint and credentials, and AI Live Insight is pointed at the agreed camera streams.
  3. AlertA vehicle matching a plate of interest passes a city camera, and the alert appears in the Fusus view with its location and camera.
  4. ResponseThe operator opens the live feed in Fusus and dispatches a unit.
  5. EvidenceThe clip around the alert is filed with a custody record and can join the case in Axon Evidence.

What stays where

Axon Fusus remains the operator view

Live video, maps, alerts and dispatch context stay in Fusus.

AI Live Insight runs the detection

It sends alerts in and does not change how Fusus displays, routes or stores them.

Cameras keep recording as they do

No new hardware and no change to the recording estate.

Processing runs on site

Detection runs on a server the customer controls.

Products and solutions

Axon Records Case Numbers on Every Derived Asset

This connector is not prebuilt. It would be built to the customer's requirement on the REST API path the platform already uses, with scope and effort agreed per engagement. Axon Records is the records management system in the Axon suite, holding reports and case files. Reading case and incident numbers from it lets redaction, transcription and search work in VIDIZMO file against the right case, so everything that returns to Axon lines up with the record it belongs to.

How it connects

Case and incident numbers, involved parties and report references would be read over the API and carried as custom attributes on the material VIDIZMO works on. That keeps a public records release, a discovery production or a search result tied to the same case number the department already uses in Axon.

Axon Records stays the authoritative record for reports and case files, report writing does not change, and nothing is written back unless a step is scoped for it.

What you can do together

  • Open a records request or discovery job against an Axon Records case number and have the matching material gathered for review.
  • Check that items a report cites are present before a production goes out.
  • Keep the case number on every redacted copy and transcript that returns to Axon Evidence.

A scenario

  1. ScopingThe engagement agrees which record fields are read and how they map to attributes.
  2. SetupThe connection is configured once against the Axon Records API with the case number mapped to an attribute.
  3. RequestA records request arrives for a case, and the case number pulls the related report references into the job.
  4. ReviewMaterial is redacted and checked against what the report cites.
  5. ReturnDerived assets go back to Axon Evidence carrying the same case number.

What stays where

Axon Records remains the authoritative record

Reports and case files stay there, and report writing is unchanged.

Read-only by default

Nothing is written back to Axon Records unless the customer scopes it.

The case number travels with the work

It arrives as an attribute and stays on every derived asset.

Processing runs where the customer chooses

VIDIZMO cloud, a government cloud, on premises or air-gapped.

Products and solutions

Next step

See it on your own Axon instance. We will show the connection made, the data moving and the output, then size it for your deployment.

Request a demonstration  or write to sales@vidizmo.ai

sales@vidizmo.ai  ·  vidizmo.ai/integrations/catalog/axon

Products we integrate with

Axon Evidence.com

Content ingestion, Export

Available on request

Axon Fusus

Live alerts, RTSP, ONVIF

Available on request Outbound

Axon Records

REST API access, Content ingestion, Workflow nodes

Available on request

Not what you need?

We build it

Send us your API documentation and we build, test and maintain the connector, at no development cost to you.

Request this integration

Bring an MCP server

If the system publishes a Model Context Protocol server, AI Intelligence Hub connects to it as a client with configuration alone.

Define a REST endpoint

Describe your endpoint and it becomes a node in an agent workflow, without waiting on our roadmap.