Commonly asked questions

No. Camnitive works on the CCTV cameras you already own (typical RTSP environments) and runs alongside your current VMS/NVR — no rip-and-replace.

Pilots of 10–50 cameras deploy in days, not weeks. You write rules in plain English — no training data, no annotation projects, and no per-site model tuning.

Yes. Rules can be configured per camera and per zone (ROI), including thresholds, cooldowns, and shift schedules — so PPE, restricted-zone, and packaging policies can differ by area.

A deterministic rules engine — not a black box — decides what fires. Zoning (ROIs), schedules, minimum-duration thresholds, and cooldowns keep alerts focused on meaningful exceptions.

Every event carries time-stamped visual evidence and an AI-written explanation in your own policy language. CamCore assembles these into conformity packs and compliance scorecards you can hand to regulators, insurers, and brand auditors.

Yes. CamEdge runs inference on-prem and video stays in-country — the AI explanation layer included. This supports EU AI Act and GDPR obligations, GCC data-protection laws such as the Saudi and UAE PDPL, and ASEAN privacy laws. Synchronization to CamCore is configured to your network and security policies.

PPE and restricted-zone monitoring, line stoppage detection, and packaging verification in targeted areas — then add process analytics, QA workflows, and compliance scorecards on the same cameras.

EHS/safety, operations, plant managers, and quality drive the use cases; IT/OT and security support deployment and governance.

Plants typically target fewer recordable incidents through continuous PPE and restricted-zone enforcement — and every event leaves defensible evidence. Safety leaders bring the trend reports and conformity packs into insurer reviews, ISO 45001 audits, and customer or brand audits, replacing self-reported checklists with a verifiable record.

Most customers start with the fixed cameras they already own at depots, yards, and gates — no rip-and-replace. In-vehicle driver behavior and fleet analytics arrive with DriveSense, launching August 2026.

Pilots of 10–50 cameras deploy in days, not weeks. You write driver behavior and safety rules in plain English — no training data, no annotation projects, and no per-site model tuning.

Yes. Policies can be configured per site, per zone, and per schedule window — so gate, yard, and dock rules can differ by location and by peak vs after-hours periods.

A deterministic rules engine — not a black box — decides what fires. Zoning, time-based thresholds, and cooldowns keep the signal clean, with safety-critical alerts separated from operational insights.

More than a notification: each event carries time, camera, rule context, visual evidence, and an on-prem AI-written narrative in your own safety-policy language — so when an insurer or regulator says 'prove it,' the answer is already on file.

Yes. CamEdge runs inference on-prem for low-latency detection at crossings and conflict points. Specific alert behaviors depend on camera placement and the configured policy.

In-country, end to end. CamEdge processes video on-prem, and CamCore can run in the cloud or in-country — supporting EU AI Act and GDPR obligations, GCC data-protection laws such as the Saudi and UAE PDPL, and ASEAN privacy laws.

Yes. Teams route alerts into existing workflows via webhooks, ticketing, and messaging integrations, with CamCore as the system of record for reporting and audits.

Yes. The cameras that enforce safety rules at docks, gates, and yards also feed dwell-time and turnaround analytics — so the deployment that protects your people pays back in throughput as well.

Alerts tell you something happened; Camnitive proves what happened. Every forklift-proximity event, blocked exit, or dock exception becomes a timestamped, evidence-grade record with an AI-written explanation in your own policy language—ready for regulators, insurers, and brand auditors.

No rip-and-replace. CamEdge runs on-prem GPU inference against the cameras you already own—the only requirement is accessible video streams. Mixed camera fleets across sites are the norm, not a problem.

Pilots of 10–50 cameras deploy in days, not weeks. There is no per-site model tuning and no training data collection: you write your safety and operations policies as plain-English rules, and the deterministic rules engine enforces them from day one.

Inside your sovereign envelope. CamEdge processes video on-prem, and CamCore—the system of record dashboard—can run in the cloud or fully in-country. That architecture is built for the EU AI Act and GDPR, GCC data-protection laws such as the Saudi and UAE PDPL, and ASEAN privacy laws like Indonesia's PDP and Singapore's PDPA.

Most start with forklift/pedestrian proximity, dock utilization, aisle safety, and blocked-exit detection. From there they add labor efficiency, congestion analytics, and yard visibility using the AI Copilot and analytics packs.

Yes. CamCore lets you define rule templates once and roll them out network-wide, with site-level zone adjustments for layout differences—so operations, safety, and compliance teams report against one consistent standard.

3PL operators use compliance scorecards as client-facing proof of duty of care — evidence per site, shift, and zone rather than self-reported numbers. Insurers see documented, continuous risk reduction on forklift-pedestrian proximity and egress compliance instead of finding out after a claim.

Alerts tell you something happened; Camnitive proves what happened. Every PPE violation, fall event, or proximity conflict becomes a timestamped, evidence-grade record with an AI-written explanation in your own HSE policy language—ready for regulators, insurers, general contractors, and brand auditors.

Neither. CamEdge runs on-prem GPU inference on the site cameras you already own, and deployment is zero-training: you write your safety policies as plain-English rules and the deterministic rules engine enforces them from day one. Pilots of 10–50 cameras go live in days, not weeks.

Because rules are written in plain English rather than trained into a model, you update zones and policies in minutes as work areas, perimeters, and crews shift—no retuning, no data collection cycles.

Inside your sovereign envelope. CamEdge processes video on-prem—which also suits remote sites with limited connectivity—and CamCore, the system of record dashboard, can run in the cloud or fully in-country. The architecture is built for the EU AI Act and GDPR, GCC data-protection laws such as the Saudi and UAE PDPL, and ASEAN privacy laws.

Most start with PPE compliance, fall/man-down detection, equipment proximity, and material staging discipline. From there they add progress tracking, subcontractor compliance scorecards, and site risk scoring with the AI Copilot.

Conformity packs assemble compliance trends by zone, shift, and subcontractor, repeat-hotspot analysis, and per-event narratives written in your policy language—so safety meetings, client reporting, and ESG audits run on the same system of record.

No. CamEdge is offline-tolerant and runs on-site over 4G/5G or temporary links. Detection continues through outages, and events sync to CamCore when the connection returns — so a greenfield site is protected from the first week of mobilization.

No. Camnitive runs on the cameras your stores already own. CamEdge handles detection on-site, so there is no rip-and-replace and no new camera estate to procure.

Days, not weeks. Rules for queues, footfall, compliance checks, and after-hours intrusion are written in plain English and applied across stores — no model training and no per-site tuning.

Alerts tell you something happened; Camnitive proves what happened. Every event is narrated by an on-prem AI in your own policy language and preserved as evidence you can hand to brand auditors, insurers, and regulators.

No. Biometric and emotion recognition are deliberately excluded from the platform. Footfall, queue, and compliance analytics are anonymous and policy-based, which keeps deployments within EU AI Act and privacy-regulation boundaries.

Inside your sovereign envelope. CamEdge keeps inference on-site and CamCore can run in the cloud or fully in-country — meeting the EU AI Act and GDPR, GCC data-protection laws such as the Saudi and UAE PDPL, and ASEAN privacy laws like Indonesia's PDP and Singapore's PDPA.

Most retailers start with 10–50 cameras across a handful of stores, then build on the same infrastructure: store operations analytics, loss prevention, the AI Copilot, and compliance packs across the full estate.

Yes — loss prevention is one of the highest-value retail use cases. After-hours intrusion, stockroom and POS-area zone rules, and delivery-door monitoring all run on your existing cameras, with every event preserved as timestamped evidence for case files. Detections stay anonymous and policy-based — no facial recognition.

Yes — this is a core design goal. CamEdge runs GPU inference on-site and is offline-tolerant: detection of restricted-zone breaches, PPE violations, smoke, fire, and leaks continues through outages, and events sync to CamCore when the link returns.

No. Inference happens on-site and only events and evidence are transmitted. Video and data stay in-country under your residency requirements — including GCC data-protection laws such as the Saudi and UAE PDPL, ASEAN privacy laws, and the EU AI Act and GDPR — and CamCore can run cloud-hosted or fully in-country.

Restricted-zone enforcement, PPE compliance, smoke and fire, leaks, perimeter intrusion, and abnormal equipment state — all configured as plain-English rules on your existing fixed cameras, with no per-site model tuning.

Every event is narrated by an on-prem AI in your own HSE policy language and preserved in a system of record. Conformity packs assemble that evidence for regulators, insurers, and ESG auditors — the answer when they say "prove it", not just an alert log.

Pilots of 10–50 cameras typically deploy in days. Because rules are deterministic and written in plain English, the same policies roll out across sites without model retraining, with escalation tiers tuned to each site's criticality.

Remote asset inspection and environmental compliance run on the same cameras and edge infrastructure, alongside the AI Copilot for cross-site operational questions and workflow integrations into ticketing and incident management.

Yes. Webhooks and integrations route events into ticketing, CMMS, and incident-management tools — a restricted-zone breach can open a permit review, a leak detection can raise a maintenance work order — with CamCore as the auditable system of record behind all of it.