Overview#
Deployment-Portable Media Processing is a pluggable media layer that runs the platform's evidence and video capabilities identically in managed cloud deployments and in fully air-gapped, on-premises installations. An agency operating a classified, disconnected network cannot send interview audio to an internet transcription service or hold body-worn camera footage with a public cloud provider, yet its investigators need the same storage, transcoding, transcription, search, and playback workflows as any other customer. Historically that choice has forced agencies to accept a reduced feature set in exchange for sovereignty.
This module removes that trade-off. Object storage, video transcoding, speech-to-text, semantic vector search, and video streaming each sit behind a provider interface, and the platform selects the right implementation for its deployment mode at startup. Security administrators in disconnected facilities, IT teams at cloud-hosted agencies, and procurement offices weighing data-residency obligations all get the same evidence and video platform, backed by whichever infrastructure their policy requires.
Key Features#
- Provider-Based Media Architecture: Object storage, video transcoding, speech-to-text, semantic vector search, and video streaming are each defined as a provider interface, so every capability can be fulfilled by a cloud or a local implementation without touching the features built on top.
- Automatic Deployment-Mode Resolution: At startup the platform resolves its deployment mode and selects the matching set of cloud or local providers automatically.
- Fully Air-Gapped Operation: The complete evidence and video stack, including transcription and semantic search over recordings, runs on local infrastructure inside disconnected networks with no external dependencies.
- Local Media Serving: On-premises installations serve video and other media directly from local infrastructure through dedicated media routes, so playback never depends on an outside network.
- Vendor-Neutrality Guard: An automated guard prevents any new platform code from coupling directly to a cloud vendor's software development kit, keeping the media layer portable by construction rather than by policy.
- One API Surface Everywhere: The same API surface serves every deployment mode, so applications, integrations, and automation behave identically regardless of where media is processed and stored.
- Cloud Feature Parity: Cloud tenants receive managed storage and transcoding with no feature differences from on-premises installations, and no media infrastructure of their own to operate.
Use Cases#
- Classified Facility Deployment: A security administrator at an agency with a classified, disconnected network runs the full evidence and video stack on local infrastructure, and investigators still transcribe and search recordings.
- Managed Cloud Tenancy: An IT manager at a cloud-hosted agency gets managed storage and transcoding out of the box, with the identical feature set their on-premises counterparts use.
- Data Sovereignty Compliance: A programme office subject to data-residency rules keeps all media processing and storage inside its own estate while staff follow the same workflows as cloud users.
- Hosting-Neutral Procurement: An evaluation team selects a hosting model on policy and cost alone, knowing the evidence and video capabilities are the same in either mode.
Integration#
Deployment-portable media processing underpins the platform's media-dependent capabilities rather than standing alone. Digital evidence management stores and retrieves exhibits through the object storage interface, body-worn camera ingestion and standards-based camera integration deliver footage into the same layer, audio intelligence and transcription features consume the speech-to-text provider, semantic search across recordings uses the vector search provider, and court-ready export packages draw transcoded, playable media from whichever backend the deployment uses. Because every consumer goes through the provider interfaces, these neighbouring modules behave identically in cloud and air-gapped installations.
Open Standards#
- MPEG-4, H.264 and H.265: Transcoding targets widely supported containers and codecs, so evidence video plays back on commodity software in any deployment.
- HTTP Live Streaming: Video delivery can use standards-based streaming manifests, whether media is served from managed cloud infrastructure or from local media routes.
- TLS 1.3: Media upload, retrieval, and streaming between clients and platform services are protected in transit with modern transport encryption.
- ISO 8601: Timestamps on media objects, processing jobs, and transcripts are serialised in standard date-time format for interoperability with downstream systems.
Last Reviewed: 2026-07-16 Last Updated: 2026-07-16