Edge and cloud labels leave important details open; follow images, records and recovery steps to understand the proposed processing design.
The main difference is where images become plate text and which connections the workflow depends on. Recognition, record storage and any access request can involve different components, so each needs its own place on the system drawing.
Local processing and local storage are separate features. Finding one in a proposal does not establish that the other is included or explain what happens during an outage.
As recognition moved into networked cameras, the recogniser could sit on a camera or server while another application held records for review. Local appliances and managed edge systems developed different ways to connect those layers.
That history explains why calling a system edge or cloud is incomplete. The useful description follows each image, event and record through the actual deployment.
A restricted network or intermittent connection may favour local processing. Remote processing may fit another maintenance arrangement. Neither is universally necessary; permitted data transfers, software licensing, access controls and maintenance ownership all shape the choice.
A local processor does not automatically keep every record in-country or continue every operation without connectivity. Those are specific deployment questions that need a demonstration and a documented recovery process.
An illustrative continuous 4 Mb/s stream carries about 1.8 GB per hour. By comparison, 1,000 events with one 200 kB image each total about 200 MB before metadata and overhead. These describe different data paths, not Aero Ranger bandwidth figures; image selection and recording policy determine the actual transfer.
Test interruptions between capture, recognition, storage and review. The demonstration should show what is buffered, which configured rules remain available and how duplicate records are reconciled. This reveals dependencies that an architecture label alone leaves hidden.
RackLink performs recognition on supported local RTSP streams. SolarLink runs configured edge checks and later synchronisation. These are distinct deployment paths with different arrangements around the cameras.
The selected arrangement should be documented for the intended workflow. Treating CORE as a single processing location would miss those differences and the responsibilities attached to them.
Aero Ranger: supported local stream processing with RackLink; Aero Ranger: compatible camera events with COREconnect; Aero Ranger: SolarLink deployment, device health and operating scope
Sources were reviewed on the publication date. Check the linked material for current details.
