Home and estate
Detect: Perimeter entry, loitering, line crossing, gate left open and camera tamper
Value: Verified alerts before a responder or owner is asked to act

Phepha connects cameras, sensors, location and response policy so homes, businesses, industrial sites and fleets receive evidence they can act on, even when connectivity is weak.
Lower upfront cost, faster installation, less electronic waste and recurring event-pack revenue.
Each deployment starts with a site risk, an event definition, a response owner and a retention rule.
Detect: Perimeter entry, loitering, line crossing, gate left open and camera tamper
Value: Verified alerts before a responder or owner is asked to act
Detect: After-hours presence, queue pressure, restricted access and incident bookmarks
Value: Faster loss review with searchable clips and acknowledgement records
Detect: PPE exceptions, restricted zones, person-vehicle proximity and smoke cues
Value: A reviewable safety event joined to place, policy and operating context
Detect: Route exceptions, driver context, harsh impact, cargo-zone entry and tamper
Value: One timeline across camera, GNSS, vehicle and geofence evidence
Detect: Illegal dumping, blocked roads, crowd density, flood cues and traffic incidents
Value: Standards-based incident exchange without pretending AI is emergency dispatch
Prices are planning estimates excluding final cabling, civil work, data and taxes. A site survey produces the binding quotation.
One focused entrance, gate, room or remote asset
A compact event camera that captures pre-event and post-event evidence, health and tamper signals. Heavier recognition runs only when an event justifies it.
Not positioned as a continuous multi-model AI server.Upgrade 1-4 compatible cameras already installed
An edge gateway that adds local event rules, selective clip upload, evidence custody and multi-channel alerts without replacing the customer's camera estate.
Site survey confirms RTSP/ONVIF access, power, placement and network quality.Higher-volume sites needing several event models
A Raspberry Pi 5 gateway with an optional Hailo accelerator or AI camera for efficient people, vehicle, PPE and zone analytics at the edge.
Camera count depends on resolution, frame rate and enabled models.Rugged sites, control rooms and multi-building deployments
Protected power, PoE, local storage, health monitoring and optional LTE, mesh, thermal or additional sensors in a managed deployment with an agreed SLA.
Final scope follows risk assessment, coverage design and compliance review.Phepha joins the event to location, policy, people, sensor quality and response history.
Planning values include the platform and event configuration. Civil works, specialist sensors, data, tax and partner response are confirmed after survey.
Face images are processed in the browser and are not sent to Phepha. Live location uses the phone browser's permission and HTTPS geolocation.
The structure protects working capital while giving customers clear acceptance milestones.
Funds hardware procurement, site mobilisation and initial configuration
Due after installation, acceptance tests and operator training
Released against the signed punch list and handover pack
Event packs, evidence, device health, updates and support
Human triage and PSiRA-accredited response where contracted
More cameras, sensors, storage, analytics, integrations and SLA coverage
The defensible advantage is a maintained human network around the technology, not an unsupported jobs multiplier.
A planning unit for workload testing, not a guaranteed jobs-to-camera ratio.
Actual staffing is driven by alert rate, travel distance, uptime target, response scope and whether the customer self-monitors. Pilot telemetry must validate the ratio before it appears in a funding or tender commitment.
A Phepha Champion coordinates people and process. The role has no police powers, does not hold an unrestricted watchlist and receives only the minimum information needed for an assigned task.
Pilot targets are agreed per deployment. They become published performance claims only after representative field evidence.
Offline queue recovery, missed-event rate and mean time to repair
Escalation delivery, acceptance and unresolved-event ageing
Clip completeness, clock quality, manifest/hash validation and custody exceptions
False alarm review by event class, site, camera and operating schedule
Data-subject requests, deletion completion and complaint resolution
Hotspot maintenance, road hazard, dumping and safety workflow outcomes
Local supplier spend, first-time fix and regional coverage
Deposit coverage, data/storage cost, renewal and site expansion
Signed webhooks, REST or message-bus events enter an existing authorised incident system after its owner approves the interface and security assessment.
Named SAPS, metro, customer or security users receive least-privilege access, MFA, audit logging and tenant-scoped evidence.
Where a station or control room lacks suitable equipment, a procured and authorised console can run on its premises with a designated, trained operator.
An authorised request produces the minimum necessary clip, manifest, timestamps, hashes and access history for an investigator or court process.
| Body or stakeholder | Legitimate role | Phepha integration gate |
|---|---|---|
| SAPS station, district and province | Crime reporting, investigation and lawful evidence receipt | Station Commander/designated official, case or occurrence reference, approved access and no assumed direct CAD connection |
| Community Police Forums and boards | Partnership, communication, hotspot identification and community feedback | SAPS Act sections 18-23; no policing powers and no raw sensitive feed by default |
| KZN Community Safety and Liaison | CPF capacity, civilian oversight and integrated provincial safety programmes | Programme agreement, monitoring indicators and provincial governance |
| Municipal and metro police services | Traffic policing, by-law enforcement, crime prevention and municipal control rooms | Municipal mandate, SCM process, information officer and approved operating procedure |
| Private security and control rooms | Verified alarm triage and contracted response | PSiRA-registered business/personnel, client consent, confidentiality and response SLA |
| SITA, GITO/CIO and government ICT | Hosting, network, security and interoperability review for public bodies | MIOS, agency architecture, procurement route and formal accreditation where required |
| Fire, disaster management and EMS | Human-confirmed hazard handoff and situational evidence | Authorised emergency channel; visual cues supplement, never replace, certified life-safety systems |
| Information Regulator and information officers | POPIA governance, PAIA access and high-risk processing oversight | Processing inventory, notices, DPIA, operator contracts, retention and prior-authorisation assessment |
| Insurers, investigators, NPA and courts | Claims or case evidence with provenance | Purpose-specific request, minimum disclosure, export manifest and chain-of-custody record |
| DMPR/Mine Health and Safety Inspectorate and labour structures | Mine or workplace safety controls and worker participation | Site code of practice, risk assessment, consultation and human-reviewed safety workflow |
| ICASA and communications suppliers | Radio equipment, spectrum and managed connectivity | Type-approved equipment, lawful spectrum use and supplier contracts |
| National Treasury, CSD, SITA and municipal SCM | Public procurement and supplier verification | Current CSD/tax/company records, tender-specific mandatory criteria and transparent milestone pricing |
| SASSETA, MICT SETA, QCTO, SAQA and TVET partners | Accredited security, control-room, IoT, AI and cybersecurity pathways | Registered programmes/providers; Phepha product training does not impersonate a national qualification |
Phepha owns the event policy, evidence model, customer workflow and integration layer. Commodity infrastructure stays replaceable.

| Layer | Candidate | Decision | Licence | Commercial role |
|---|---|---|---|---|
| Media routing | MediaMTX | Adopt now | MIT | RTSP/WebRTC/HLS routing, recording and playback from one compact service |
| Edge detection | OpenCV + ONNX Runtime | Adopt now | Apache/MIT | ARM-compatible event models with measured CPU and memory budgets |
| NVR option | Frigate | Pilot selectively | MIT | Strong detection and review workflow; face recognition is not Pi-native because it requires AVX/AVX2 |
| Notification fan-out | Apprise + ntfy | Adopt now | BSD/Apache-GPL | One policy can reach push, email, WhatsApp API, SMS or webhooks |
| Escalation | GoAlert | Evaluate for control rooms | Apache 2.0 | Acknowledgement, schedules and escalation instead of fire-and-forget alerts |
| Broadband mesh | OpenWrt 802.11s + batman-adv | Pilot on controlled sites | GPL | Site-owned backhaul for cameras and gateways after RF design |
| Low-bandwidth site IoT | ChirpStack LoRaWAN | Pilot for sensors | MIT | Health, alarm and command packets only; never marketed as a video network |
| Smart-city exchange | FIWARE NGSI-LD | Contract-led | Open standards | A standards-based context API for municipal integration without hardwiring one city stack |
| Intermittent edge fabric | Eclipse Zenoh | Lab benchmark | Apache/EPL | A future low-overhead path for distributed devices; MQTT remains the production baseline |
Responsible limits reduce false claims, failed deployments and regulatory exposure.
Face identity is consent-based and purpose-limited. Public-space identification is not enabled by default and may require prior-authorisation assessment and a DPIA.
CCTV installation, monitoring, tracking and security response are delivered through appropriately registered parties where the activity falls within regulated security services.
AI prioritises evidence. It does not autonomously accuse, punish, dispatch police or trigger high-consequence action.
Visual smoke, fall or impact cues supplement certified fire, medical and vehicle safety systems; they do not replace them.
Wireless equipment follows ICASA type-approval and spectrum requirements even when it operates in licence-exempt bands.
Every contract defines notice, access, encryption, retention, deletion, export and incident-response responsibilities.
SAICTS will survey the site, confirm compatible cameras, define acceptance tests and issue a milestone-based quotation.
Request a paid pilot