Cameras, networking, recording and management sized as a verifiable system.
AXIS Camera Station Pro and Edge retained as distinct operating models, with appropriate qualifications on versions and cloud use.
Useful business video starts with an operational question: which event needs to be observed, in which area and at what level of detail? The answer guides the camera, lens, position, lighting, recording and response routine. In the Axis ecosystem, network cameras, analytics and management software can form part of projects for protecting facilities and monitoring authorized processes. Each combination must be sized and validated for the actual environment. Since 2011, in São José do Rio Preto, ADD Solution has focused on technology engineering, deployment and operations. For Video Intelligence, the approach is to connect business needs with the infrastructure that sustains video: networking, power, processing, storage and procedures. A project’s expected outcome must be defined by acceptance criteria, without assuming uniform performance across models or applications. Technical basis: official Axis portfolio.
The portfolio includes dome, bullet, box, PTZ, panoramic, thermal and modular cameras. Physical format helps organize selection but does not alone determine the quality required. Object distance, backlighting, motion, reflections, rain and vibration change the demands on lens, sensor, shutter and installation. Among bullet cameras, for example, Axis presents M20 with fixed focal length, P14 with varifocal options and Q18 for more demanding applications. The F series separates the main unit from the sensors, enabling modular combinations. These examples do not make every product in a family equivalent: resolution, environmental protection, power, analytics capabilities and support lifecycle must be checked in the exact model’s data sheet. A panoramic camera can broaden the overview; observing detail at a distant point may require different framing. PTZ requires defined positions and operational priorities, because moving the camera changes the observed area. During the survey, a reference image for each scene and the criterion for its approval should be recorded. Sources: product selection, bullet cameras and F modular series.
AXIS Camera Station Pro is a server-based VMS, operating on a private network with optional cloud service connectivity. The architecture must account for the server, operator clients, compatible devices and licenses. Management, search and integration functions do not remove the need to size storage and decoding capacity. AXIS Camera Station Edge uses Axis devices and cloud services without requiring a dedicated VMS server. Primary storage can use media and recorders supported by the system, such as Axis cards and recorder series listed in current documentation. A camera-to-cloud connection does not mean that every recording is automatically stored in the cloud. AXIS Camera Station Cloud Storage is an additional redundancy service with its own conditions. When consulted on 2 October 2026, the Axis support page advised against upgrading to ACS Pro 6.19 for environments using Cloud Storage, multi-server viewing or multi-server Smart Search. Official documents differed about the effect on Cloud Storage; therefore, neither preservation nor inevitable loss of video should be promised. Before any change, confirm the current advisory and recovery plan with Axis. The advisory states that ACS Edge is unaffected. Sources: ACS Pro, ACS Edge, Cloud Storage, 6.19 upgrade advisory and ACS Pro support.
AXIS Object Analytics can detect, classify and count moving objects, particularly people and vehicles, on compatible cameras. Scenarios such as line crossing, presence in an area and dwell time can help organize operational events. Availability depends on the camera, onboard processing, AXIS OS version and selected function. The project must start with observable rules: entry into a restricted area, a direction of travel or an aggregate count. Small objects, occlusion, shadows and lighting changes must be included in testing. The team must measure correct events, false alerts and missed occurrences in a representative sample. These results guide adjustments to the scene and rules. An alert requires verification by an authorized person before consequential decisions; it is not automatic evidence of intent or wrongdoing. The proposal does not depend on inferring emotions, sensitive attributes or people’s identities. Indicators must address a legitimate and clearly defined operational need. Sources: Object Analytics manual and compatibility and installation.
The network must support simultaneous recording, viewing, queries and exports. Adding only recording bitrates can underestimate traffic: additional clients and different video profiles also consume capacity. The design must check uplinks, distribution across switches, latency and the path to storage, preventing video operations from impairing other applications. PoE requires checking per-port power, the switch’s total budget and maximum device consumption, including heaters, illumination and accessories where applicable. Available port count does not guarantee sufficient power. Cabling, electrical protection, grounding and UPS runtime must be handled by qualified professionals according to local conditions. Segmentation and communication rules must be planned with the IT team. At acceptance, recording should be tested while operators open multiview layouts and export images, alongside observing behavior after power loss and restoration. Testing must be authorized, controlled and compatible with the environment’s continuity requirements. Sources: Site Designer planning and network video latency.
Storage must be estimated by scene, codec, resolution, frames per second, bitrate and recording hours. As an arithmetic example, 16 cameras recording continuously at an average 4 Mbps generate approximately 20.7 decimal TB in 30 days. This figure represents video alone under those assumptions, before audio, metadata, operational reserves, redundancy and capacity unavailable within the disk arrangement. Zipstream can reduce demand depending on the scene, device and configuration. A manufacturer-published average should not be turned into guaranteed savings for every installation. Nighttime noise and frequent motion can change consumption; overly restricting bitrate can compromise the required detail. The initial calculation must be compared with measurements. Raw capacity must also be distinguished from usable capacity, and planned retention from retention actually available. During operation, monitor the oldest retrievable video, disk failures and growth in consumption. For specific incidents, define authorized export before routine overwriting. Sources: bitrate control and Zipstream technology. The numerical example is an engineering calculation, not a product specification.
ONVIF must be evaluated through the profile shared by device and client, with their registered versions. Profile S covers video streaming functions; T covers advanced streaming; G addresses recording and retrieval; M relates to metadata and analytics events. Conditional functions exist: sharing a profile does not guarantee every proprietary feature or workflow. Integration must test video, authorized audio, time, events, PTZ where present, search, export and recovery after disconnection. Receiving an image over RTSP does not demonstrate that the VMS receives the metadata used by intelligent search. When the project uses third-party products, the compatible product list, drivers and licensing must be part of the validation scope. Sources: ONVIF profiles, conformance process and ACS Pro manual.
Cameras and VMS must be included in the IT inventory, with owners, versions and an update lifecycle. Individual accounts, least privilege, certificates and protected channels reduce exposure. Features must be confirmed by product and version. Avoid publishing administrative interfaces directly on the Internet; remote access needs an architecture approved by the company. Update policy must combine security fixes, compatibility assessment and recovery options. Storing system configuration and the database is a different task from preserving recordings. RAID, where available, can improve tolerance of certain disk failures but does not replace an independent copy or protect against every incident. The operating plan must account for camera failure, network loss, power failure, full storage and server unavailability. Define who receives each alert and how restoration is verified. Edge recording can help in supported scenarios, but recovery must be rehearsed with the contracted configuration. Sources: AXIS OS hardening, vulnerability management and ACS Pro installation and migration.
Images of identified or identifiable people can involve personal data. Purpose, legal basis, necessity, transparency, access and retention must be assessed by the controller, with legal support where needed. LGPD does not turn a camera configuration into automatic compliance or establish a single retention period for every project. Framing, privacy masks and export restrictions can reduce exposure. Audio and analytics that expand collection require specific justification. Legitimate interest must not be selected automatically and is not an applicable basis for sensitive personal data. The assessment must consider the context and data subjects’ rights. Sources: LGPD and ANPD guidance on legitimate interest.
Complete answers for Axis Communications architecture, deployment and operational decisions.
They are different architectures. Pro uses a server and supports optional cloud connectivity; Edge combines devices and cloud services without a dedicated VMS server. The choice depends on operations, integrations, recording and required capabilities. Axis source.
No. The manual lists supported local media and recorders. Internet access is required for configuration and management; live and recorded video may be available offline under the documented conditions. Cloud redundancy is additional. Edge manual.
No. Object Analytics is included on compatible cameras, and its capabilities vary by platform and version. The model must be checked before specifying a rule or report. Official compatibility.
ACS Pro supports third-party products, but integration requires checking the device, functions and license. The proof of concept must reproduce the workflow actually needed, beyond simply displaying live video. ACS Pro.
Not on their own. Lens, distance, lighting, motion and compression must preserve the detail required by the task. Compare equivalent scenes and validate framing on site rather than deciding solely by advertised resolution. Official selector.
List recording and viewing profiles, concurrency and retention. Use planning estimates and confirm consumption in the field, including peaks and reserves. Sizing must keep pace with changes in the environment. Site Designer.
The documentation distinguishes licenses tied to Axis hardware from one- or five-year licenses for third-party servers. Device type and expansions also matter. The proposal must identify the contracted entitlements and their validity. Licensing guide.
Approved scenes, retrievable recording, permissions, alerts, export, consumption and recovery from failures. Record limitations and owners. These criteria are a project recommendation and must be adapted to the agreed scope. Axis planning tool.
Define capture, networking, storage, management and operations without generic promises.