A compression layer that nothing downstream has to know about

Conventional compression trades quality for space. Ours is built so that the video management platform, the operators, the auditors and the AI models all behave exactly as they did before — while the storage bill falls by up to 90%.

Approach

Three problems, one architecture

Every large video network we are asked to fix is failing on at least one of these three axes. They are usually described as separate projects; they are the same project.

Retention keeps getting longer

Statutory and policy retention periods are extended faster than storage budgets are approved. Every extension multiplies an estate that is already at its physical limit.

Capacity cannot always be bought

Adding arrays means adding racks, power and cooling. Remote sites frequently have no room and no viable network path at all.

AI makes the quality problem sharper

The features analytics need are precisely the high-frequency detail that aggressive compression discards first.

Foundation

The four invariants and the two lossless guarantees

These are physical properties, not marketing positions. The four invariants protect the indexing, playback and retrieval logic of the incumbent platform. The two lossless guarantees protect the people and the machines that have to use the footage.

Four invariants

Resolution unchanged

No upscaling, no downscaling. Pixels map one-to-one to the original.

Frame rate unchanged

No frame dropping. The original temporal smoothness is preserved exactly.

Codec format unchanged

H.264 and H.265 are carried through natively, so no client needs a new decoder.

Duration unchanged

Millisecond-level alignment keeps timeline scrubbing and seek positioning exact.

Two lossless guarantees

Visually lossless

No perceptible degradation for operators, investigators or reviewers — validated by no-reference quality scoring at frame level.

Machine-vision lossless

Person, vehicle and plate features are retained so downstream structured analysis is entirely unaffected.

Why both matter. An operator reviewing an incident and a model detecting a plate are two different consumers of the same pixels. Systems that only satisfy one of them create a silent failure: footage that looks acceptable and cannot be used.

Where the bytes go

What actually gets removed

We do not amplify grain or invent detail. We remove information the eye and the model both discard — then rebuild the rest faithfully.

Visual redundancy

Human sensitivity to luminance and chrominance differs. Dynamic adjustment of colour and brightness removes what the eye cannot resolve.

Spatial redundancy

Adjacent pixels in an image are highly similar. Removing that repetition reduces data volume without touching structure.

Temporal redundancy

Consecutive frames share large amounts of content. Inter-frame coding removes the duplication that carries no new information.

Key ROI preservation. On top of the three redundancy classes, AI-assisted encoding detects regions of interest — faces, vehicles, plates — and allocates bitrate preferentially so that the features downstream analytics depend on survive the process at full fidelity.

Cluster node with internal storage bays reverse
X-Stream Archive

In-place compression for footage that already exists

The hardest case is not a new build — it is an existing network with millions of files already on storage and a management platform that must not be disturbed. X-Stream Archive was designed around that constraint.

  • Runs on general-purpose CPU only. No GPU, no dedicated accelerator.
  • Supports 100% physically isolated internal networks with no external access.
  • Scales linearly from tens to thousands of compression nodes.
  • Sustains beyond 12.5 GB/s aggregate throughput on typical hardware.
Absolute boundaries

What the system will never do

A clear boundary lowers systemic risk and physically protects the evidentiary value of the footage. These exclusions are architectural, not configurable.

Never

  • Intercept or hijack the live video ingest path.
  • Affect concurrent recording writes from the original platform's cameras.
  • Modify the incumbent platform's preview, retrieval or playback workflows.
  • Apply AI picture enhancement, which would compromise evidentiary authenticity.
  • Touch a source file until verification has fully passed.

Always

  • Operate on landed recording files held in centralised open storage.
  • Scan with configurable delay, automatically identify the scene type and select a matching template.
  • Replace files in place on pure CPU compute, transparently to every user.
  • Verify every output against three independent safety gates before committing.
  • Retain the original until a configurable ageing period has elapsed.
Verification

Three gates, then and only then a replacement

Each file passes through an isolated working area. If any gate fails, the temporary file is destroyed automatically and the source file is left completely untouched.

Gate 1 — Playability

The temporary file's container and basic playback behaviour are verified before the output is trusted for anything else.

Gate 2 — Four invariants

Machine-level comparison of resolution, frame rate, codec and duration between the new and original files. All four must match exactly.

Gate 3 — Quality risk

PSNR and SSIM are evaluated against the expected envelope. Falling short triggers a preventive circuit-breaker instead of a replacement.

Preventive circuit-breaker. If picture degradation is detected — PSNR or SSIM below the expected envelope — processing halts before the source file is touched. Repeated failures permanently stop processing that file, safely retain the original, and raise a system alarm, avoiding the I/O risk of repeated attempts.

Architecture

Pure CPU, distributed, and horizontally unbounded

Hardware independence is not an optimisation — it is what makes the system deployable in a sealed government network and affordable at city scale.

Control
X-Stream PlatformGlobal scheduling, policy, alerting
Worker nodes
Scanner NodeDelayed scan and scene classification
Compress NodeCPU compression cluster
Quality NodeSampled quality inspection
Media NodeMedia read and write
Storage
Centralised open storageLanded recording files
Scene intelligence

Adaptive templates instead of manual tuning

The platform analyses day and night, lighting, motion level and scene complexity, then applies the strategy that scene actually needs. No operator parameter tuning.

Dynamic scenes

City roads, checkpoints and commercial streets. Strategy leans toward stable quality, protecting the detail of people and vehicles.

Static scenes

Corridors, warehouses and fixed entrances. Strategy leans toward a higher compression ratio to release the maximum storage.

Mixed motion

Smart campuses, car parks and public service halls. Strategy balances space against quality for footage that changes character through the day.

Deployment models

Four architectures, one codec core

Most clients start with one and expand into the others as coverage grows. There is no re-engineering step between them.

Edge scattered access

Compress at each distributed site before the stream leaves the premises. Removes the need for local NVR stacks and slashes backhaul bandwidth.

Node-level intelligent compute

A mid-size campus or industrial site served by a single appliance carrying compression, AI inference and a lightweight VMS in one box.

Central high-density aggregation

City, province and carrier scale, converging hundreds of streams per node with N+M hot standby and service-level failover.

Cloud software compression

Zero new hardware. Compress in the platform on general-purpose CPU, with linear horizontal expansion as ingest grows.

Return on investment

Five cost lines move at once

Compression is not only a storage saving. It reduces the hardware, rack, power, bandwidth and maintenance lines together — and it preserves AI capability rather than trading it away.

70%+
Comprehensive TCO reduction
Against a conventional server-and-array build
76%
Hardware investment saved
Representative comparison project
0
Additional hardware on the archive path
Software-only deployment option
6x
Retention period increase
30 days to 180 days on identical capacity
Conventional camera
4 Mbps

Per 1080P stream, 30-day retention

100%

Storage, rack, power and bandwidth footprint

With our platform
0.5 Mbps

Per 1080P stream, 180-day retention

<30%

Storage, rack, power and bandwidth footprint

Map this onto your network

Tell us your camera count, resolution mix, retention requirement and network topology. We will return a target architecture and an indicative capacity model.

Request a consultationSee the hardware