RAPTORv0.1 · ZA

Drone security software for patrol operators

Your drones are already flying.
Everything else is on WhatsApp.

RAPTOR is the operations spine for private security drone teams: detect, track, alert, document and bill — in one place, with court-ready chain of custody on every frame.

The demo is a sandbox with fictional data — no signup, nothing to install. The free trial is the real product for 14 days: one aircraft, two people, 300 minutes of video, 2 GB of storage and court-ready exports, with no card. One trial per company.

01
Detect
Live RTMP + telemetry
02
Track
Realtime map, trails
03
Alert
WhatsApp, GPS-pinned
04
Document
SHA-256, chain of custody
05
Bill
PayFast, ZAR

Why it holds up

Footage is not evidence until somebody can prove nobody touched it.

Sealed on arrival

Every still and clip is hashed the moment it lands — not later, not on export. Anyone can re-verify that the file is byte-for-byte the one that was captured.

Append-only custody

Every view, download and export is written to a log nobody can edit or delete. Not the operator, not an administrator, not us.

POPIA from the start

You set a retention window per site. Past it, footage is destroyed automatically — while the record of it, its digest and its access history survive, so an old export still references something real.

Anyone can ask what you hold about them, or ask to be erased — both are a single request, both are logged, and neither alters an incident record somebody else may need. See a sealed record.

Inside the product

Two registers, because two different people have to read it.

A controller at two in the morning needs colour, movement and one glance. An insurer, a body corporate or an attorney needs the opposite: plain type, exact times, and nothing that looks like it was styled to persuade them. RAPTOR does not restyle one into the other — the tactical layer is simply not present in the record.

The console, at 02:00Operations
The RAPTOR operations console: a dark map of Cape Town with four drone markers, a fleet panel showing Sentinel-04, Impi-03, Kestrel-02 and Hawk-01 with battery levels and coordinates, and an incident feed with severity badges.
Four aircraft, live. Battery and position on every one, incidents arriving as they happen, and the draw tools for a zone, a station or a patrol route within reach. Single-colour by design — the callsign letters tell the aircraft apart, so colour is free to mean severity and nothing else.
One incident, end to endOperations
A RAPTOR incident record: a map with a red cordon zone and a drone track, beside a timeline reading Detected, Incident opened, Still captured, Alert sent, Acknowledged, Clip attached, Resolved, Exported, each with a timestamp.
Detection at 02:11:47, alert to the ground team at 02:12:04, a named person acknowledging three minutes thirty-four later. Nobody typed any of it.
The same night, for a lawyerRecord
The RAPTOR evidence register: a plain white page listing four files with capture times in SAST, file types, sizes and full SHA-256 digests.
Every file, its digest, and who touched it. No colour, no glow, no severity theatre — this is the page that gets printed and attached to something.

And the part nobody photographs

The record-keeping is the job. The map is how you see it happen.

Every operator already has a map. What they do not have is a list of who signed for the current revision of the operations manual, which folio has been open for eleven days, and what expires next month — and those are the things an audit asks for.

What needs attention, firstRecord
The RAPTOR compliance screen: a status list reading "1 document already expired", "1 level 1 finding open" and "1 person has not acknowledged revision 7", each with a FIX link, above tabs for Expiry, Operations manual, Audits and findings, and Produce a pack.
Three lines answer the only question worth asking on a Monday. Each one is a button into the screen that fixes it — ordered by consequence, because an expired approval grounds the operation and an unsigned distribution list is a finding on the day.
The list a version number cannot beRecord
The RAPTOR operations manual register: revision 7, effective from 2026-08-26, approved 2026-08-20, training required, a summary of what changed, and a distribution list naming each person and whether they have acknowledged it.
CAR 101.04.5(5) asks that an amendment reach everyone engaged in the operation and that they be made aware of it. A version number evidences none of that. This names the person who has not signed, which is the only form of that answer an inspector accepts.
The folio, before anyone asks for itRecord
The RAPTOR flight paperwork queue: sorties listed oldest first with the aircraft, the pilot, the duration and whether the folio is complete and acknowledged.
Seventeen fields per flight under SA-CATS 101.05.22, filled from what the console already saw. Oldest first, because the folio nobody has closed is the one that has been open longest — and it is the one an audit finds.

These are screenshots of the running software, captured by a script that signs in and photographs it — not mock-ups. The digests in the evidence register are real SHA-256 values. Click through it yourself.

Packages

Pay monthly. Cancel any time.

Subscribe now and pay monthly through PayFast, or start with one free 14-day trial per company — no card needed. Cancel any time; a cancelled plan runs to the end of the month you paid for.

Starter

R499/ month

One drone, one site — the paperwork and evidence done properly.

  • 1 drone
  • 2 users
  • 100 alerts a month
  • 1 000 video minutes a month
  • 10 GB storage
  • PDF incident reports

Pro

Recommended

R1 999/ month

A real fleet: several drones, a control room, court-ready exports.

  • 5 drones
  • 10 users
  • 1 000 alerts a month
  • 10 000 video minutes a month
  • 100 GB storage
  • Court-ready PDF exports

Enterprise

Quoted

Many sites, many pilots, your own limits and terms.

  • Unlimited drones
  • Unlimited users
  • Unlimited alerts
  • 100 000 video minutes a month
  • Storage sized to your contract
  • Court-ready PDF exports
Talk to us

Prices in South African rand, billed monthly by card once your trial ends.

Founding customers

Fly one shift. We’ll build the record.

One aircraft, one site, fourteen days, no card. You fly your normal patrol; we turn it into a sealed, timestamped, court-ready record. If it isn’t obviously better than what you do now, we’ll say so and you’ve lost a morning.

  • 1 aircraft
  • 1 site
  • 14 days
  • No card
  • Your data stays yours
Nothing is charged, and no card is taken at any point.

What you type here goes into a message you send us yourself — this page stores nothing and sets no cookies. We use your details to arrange the pilot and for nothing else.

About

Built here, by one person, for operators here.

RAPTOR is built by Gregory Dearham. Not a team, not a reseller of somebody else’s platform — one person who writes the code, answers the email and will be on the call when something breaks at two in the morning.

It started from a narrow observation: South African drone security operators have the flying solved and the paperwork nowhere. The aircraft is licensed, the pilot is competent, the patrol happens — and then a controller retypes a Thursday night into Word from memory, and the footage sits in a folder with a WhatsApp filename on it. Everything RAPTOR does is aimed at that gap, and nothing it does is aimed anywhere else.

It is early, and saying so is the point. There is no pretence of a support desk or a decade of deployments. What there is instead: the software genuinely runs, you can click through it right now without giving anybody an address, and a founding pilot costs nothing because the first operators are doing us the favour, not the other way round.

If you would rather talk to a person than read a website — gregory.dearham@kiffleads.com.

Based
South Africa — ZAR, SAST, POPIA
Stage
Early. Founding pilots are free
Support
Direct to the person who builds it

Straight answers

  • Where the data sits. The application and the database are both hosted in the EU (Frankfurt) — one place, not two. That is a cross-border transfer under POPIA §72, permitted because the EU regime offers substantially similar protection. Alerts, video and card payments are delivered by named third parties outside South Africa, and the list is yours on request. Your data stays yours, and you can export or erase it whenever you ask.
  • What it will not do. No facial recognition. No matching against SAPS or any police database. Neither is on the roadmap, and both are refused rather than deferred.
  • Who is accountable. POPIA requires a named Information Officer for the responsible party. For RAPTOR that is Gregory Dearham, at the address above — a person, not a form.

The fastest way to judge any of this is to use the thing. The demo is a sandbox with invented data, takes no signup and stores nothing about you.

RAPTOR — Drone security software for patrol operators