ZON-01
Restricted-area entry
Entry into a polygon you draw — server room, cash office, tank farm, substation, bonded store.
Access control tells you a door opened. It does not tell you who walked through it.
LIVE01VerifyIs every camera actually working?
Security intelligence for cameras you already own
See it. Prove it. Close it.
Blepo connects to the cameras already on your wall, proves they are actually working, turns what they see into incidents a person can act on, and keeps the record of what happened next.
No rip and replace. No proprietary cameras. One piece of software that speaks ONVIF and RTSP, reads without ever writing to your recorder, and tells you plainly when it cannot prove something rather than colouring it green.
- ONVIF & RTSPStandards your estate already speaks
- Read-onlyNo writes, no PTZ, no deletions
- Five statesVerified, failed, unknown, unsupported, stale
- SignedAn evidence record, not a status page
Standards we build on, and recorders we are validating.
Blepo connects over RTSP and ONVIF, which most of your estate already speaks. Recorder-level checks need a vendor adapter, and what any given adapter can actually prove depends on the model, the firmware and the access you grant it. Those four brands are candidates under test, not blanket guarantees — we publish a tested compatibility matrix per model rather than a wall of logos, and a camera we cannot prove something about is reported as UNSUPPORTED.
BUILT ONRTSPH.264 · H.265 streams
BUILT ONONVIFDiscovery and device metadata
IN VALIDATIONHikvisionISAPI recorder metadata
IN VALIDATIONDahuaCGI recorder metadata
IN VALIDATIONAxisVAPIX recorder metadata
IN VALIDATIONUniviewLAPI recorder metadata
NO RIP-AND-REPLACE · NO NEW CAMERAS · NO RECORDER SWAP
Equipment nobody is checking is not security.
It is a record of your loss.
It is a record of your loss.
01
Reactive
Everything is reviewed after an incident, never during one. The equipment was a witness, not a guard.
02
Unverified
Disks fill, lenses drift, generators idle, recorders stop writing. Nobody checks until it is needed.
03
Unsearchable
Hours of manual scrubbing on the one morning it actually matters — if the footage is even there.
Blepo checks every device on the site, every hour and signs the proof that it did.
THE PREMISE
This camera is already on the wall. The question is whether it is doing anything.
Nigerian estates, warehouses and branches have spent a decade buying cameras. Very few of them can tell you, this morning, which of those cameras produced usable footage last night. That is the gap Blepo closes first.
LAYER 00 · VERIFY
Intelligence is worthless on a camera that isn’t recording.
Every AI security platform sells you detection and quietly assumes the footage is there. Nobody checks. So before a single detection runs, Blepo checks each camera independently — stream, image quality, recorder state where the recorder exposes it, and clock drift — and reports each check as verified, failed, unknown, unsupported or stale. Never as a single green dot.
CAM 01
North Gate
Recording verified
RETAINED31d
CAM 02
Reception
Recording verified
RETAINED31d
CAM 03
Server Room
Recorder not writing · 6d
RETAINED0d
CAM 04
East Corridor
No recorder API on this model
RETAINED—
CAM 05
Loading Bay
Image degraded · view shifted 14°
RETAINED29d
CAM 06
Car Park
Recording verified
RETAINED31d
CAM 07
Perimeter W
Stream unavailable · 21d
RETAINED—
CAM 08
Rear Exit
Clock drift 4m 12s
RETAINED31d
CAM 09
Stairwell
Check incomplete · timed out
RETAINED?
CAM 10
Warehouse
Recorder stopped · 2d
RETAINED2d
CAM 11
Gate 03
Recording verified
RETAINED31d
CAM 12
Yard South
Site agent offline · stale 2h
RETAINED?
3 of 12 cameras would have produced nothing if you had needed footage this morning — and on 3 more, we cannot prove either way, so we say so rather than colour them green.
STREAM
Stream health
Every camera polled on a schedule you configure. A stream that is unreachable, unusable or still serving the same frame is reported as failed, not quietly skipped.
RECORD
Recording integrity
Where a recorder exposes it, we confirm it is genuinely writing this channel — not merely powered on and answering pings. Where it does not, we say so.
RETAIN
Retention, where readable
On recorders whose adapter supports a retention test: how many days of footage are actually retrievable right now, per camera, against the policy you believe you have.
FRAME
View integrity
Detects a shifted view, a defocused lens, an obstructed frame or an IR failure against a reference frame.
TAMPER
Tamper evidence
Signed heartbeats from every site. Silence is treated as an alarm, not as an absence of news.
CLOCK
Clock accuracy
Drifted timestamps make footage useless as evidence. We measure the drift against a trustworthy reference and report it — correcting it is a change on your NTP, not something Blepo reaches in and does.
Verify runs on the cameras you already own, on hardware already at the site. No new recorders, no rip-and-replace, no capital approval and it is the reason every layer above it can be trusted.
HONEST VERIFICATION
A camera is not green or red. It is one of five things.
Two states force every uncertainty into a lie. A camera whose recorder cannot be queried is not healthy — it is unverifiable, and you deserve to be told which.
StateWhat Blepo means by itWhat a two-state dashboard shows
VERIFIEDThe check ran against the device, the device answered, and the answer was affirmative within the time window the check defines.Green
FAILEDThe check ran and the device failed it. Stream unreachable, no frames, image quality below the rule, or the recorder reported it is not writing this channel.Green, until someone asks for footage
UNKNOWNThe check could not establish an answer either way. We say so. We never infer a pass from the absence of a failure.Green
UNSUPPORTEDThis device or recorder does not expose what the check needs. The capability is missing, not failing — and the difference belongs on your screen, not in our logs.Green
STALEThe last answer is real but old. The site may be offline, the agent may be buffering. An hour-old pass is reported as an hour-old pass.Green, showing yesterday
THE INVARIANT
A live stream never implies a recording.
A camera can be online, in focus, perfectly framed, and writing nothing to disk. Blepo reports stream health and recording state as two independent checks, and reports recording as verified only where a supported recorder returns affirmative evidence. Everywhere else it reads RECORDING UNKNOWN — because that is what we actually know.
Recording verified means a recorder-specific playback or retention test returned evidence inside a defined window. It is not a guarantee about future footage, and we do not present it as one.
DETECT
Three tiers, and we tell you which one you are buying.
A rule you draw on a camera view behaves the same way on day one and on day four hundred. A behavioural model does not, until it has seen your site. Those two things are sold as one thing everywhere else in this category.
Geometry, schedule and object class. You draw them on your own camera view and they do exactly what you drew, which is why they can ship first.
ZON-02
Virtual tripwire
A line crossed, optionally in one direction only. In but not out, or out but not in.
Direction is the difference between a delivery and a theft.
ZON-03
After-hours presence
A person or a vehicle on site outside the schedule you set, per camera, per day of week.
Most losses happen when the site is empty and nobody is watching the screen.
ZON-04
Dwell and loitering
Presence inside a marked zone for longer than a threshold you choose.
Reconnaissance looks exactly like loitering, and precedes most planned incidents.
ZON-05
Obstruction and scene change
Camera covered, frozen frames, or a major change to what the camera is pointed at.
Reported as an observation with evidence, never as an accusation of sabotage.
Every rule is drawn on your own camera view, on your own schedule, with a preview mode and a version history. Rules disable themselves automatically when the input quality is too poor to trust — a detection from a defocused camera is worse than no detection at all.
INVESTIGATE
One incident, not nine alerts.
Related detections are correlated into a single incident with a severity, an explanation and whatever evidence the integration permits. Every underlying signal is kept — correlation groups the noise, it never discards it.
- 02:14:31YARD-04ZON-03 · after-hours presencePerson class · schedule: closed
- 02:14:48YARD-04ZON-02 · tripwire, inboundDirection matched
- 02:15:12BAY-07ZON-01 · restricted-area entryBonded store polygon
FRAMETrigger frameStored by Blepo · retention 30d
CLIP8s around triggerStored by Blepo · retention 30d
REFNVR 02:14:00–02:18:00Reference only · footage stays on your recorder
LIFECYCLE
NEWACKNOWLEDGEDASSIGNEDINVESTIGATINGESCALATEDRESOLVED
OR MARKED BENIGNEvery transition records who did it and when. Machine-generated candidate signals are shown distinctly from human-confirmed incidents, and marking one a false alert is captured as feedback rather than swallowed.
Your recordings are never touched
Blepo reads. It does not delete, overwrite or alter an original recording on your NVR, and the connector has no API for doing so.
Ours and yours are labelled apart
Every item says whether Blepo is holding a copy or merely holding a pointer into footage your recorder owns. You always know which one you are relying on.
Provenance travels with it
Event time, source camera, retrieval time, rule and model version, and an integrity hash where the integration supports one.
Access is scoped, expiring and logged
Tenant-scoped storage, short-lived links, configurable retention — and an audit trail of who opened what, which exists for your protection as much as ours.
RESPOND
It reaches a person, and the record says whether it arrived.
Recipient groups, escalation chains, quiet hours and cooldowns — and delivery failures shown as failures. If WhatsApp drops the message, the incident is still open, still assigned, and still waiting for somebody.
IN-APPFirst release
In-app
- A live incident feed with unread state, severity, site, camera and timestamp
- Recipient groups, event categories, escalation chains, quiet hours and cooldowns
- Acknowledgement and view state, but only where it is technically measurable
WHATSAPPGated on provider approval
WhatsApp Business
- An approved provider and compliant templates — no grey-route messaging
- A short summary and an authenticated expiring link, never raw footage by default
- Opted-in, verified recipients as provider rules and applicable law require
WEBHOOKAfter pilot
Signed webhooks
- incident.created, incident.updated, camera.offline, camera.degraded
- Stable IDs and idempotency keys, so your ticket system never doubles up
- Delivery history, retries and rate-limit visibility
PERFORMANCE POLICY
We are not quoting an alert latency.
Not because it is slow — because nobody has measured it on your cameras, your uplink and your recorder yet. We instrument event-to-incident, incident-to-queue and queue-to-provider timings from day one, and we will publish medians and 95th percentiles once pilot deployments have produced them. Any vendor quoting you a sub-second figure before seeing your site is quoting you a lab.
THE RECORD
A dashboard tells you what it thinks. A record proves it.
Every check Blepo runs is signed on your site, before it touches our servers and each batch is cryptographically linked to the one before it. Change a reading after the fact and every link after it breaks. That is the difference between a status page and evidence you can hand to an insurer, an auditor or a court.
03:11:40GATE-01recordingwriting · 31d retained
03:11:40GATE-01frame integrityfrozen · 0.998 match
03:11:40YARD-04field of viewdrifted 11°
03:11:40BAY-07recordingwriting · 30d retained
03:11:40DOCK-02clock+2s of NTP
03:11:40DOCK-02recordingunsupported · recorder exposes no status
PREVIOUS9f2c…a41b
THIS BATCH4d81…07ce
NEXTc705…18fa
Signed where it happens
The signing key never leaves your site. Even we cannot forge a reading that was never taken which is the whole point of asking us.
Two clocks, both kept
When the reading was taken and when it reached us are recorded separately. The gap between them tells you about your uplink, not just your camera.
A report you can check
The monthly report cites the exact stretch of the record it was built from, so the person receiving it can verify it rather than take your word.
HOW IT WORKS
Four steps, and none of them involve buying a camera.
Most security upgrades start with a quotation for hardware. This one starts with the estate you already paid for.
01
Connect what is already installed
A lightweight agent runs on hardware already at the site and finds your cameras over ONVIF, or takes their stream addresses directly. No new cameras, no re-cabling, no recorder swap.
02
Verify before you analyse
Every camera is checked continuously — stream, image quality, recorder state where the recorder supports it, clock. Nothing is analysed on a camera Blepo cannot first prove is working, and a check we cannot complete is reported as unknown rather than passed.
03
Draw the zones that matter
Mark perimeters, doorways, restricted areas and tripwires directly on the camera view, and set the hours each rule applies. Everything is normalised, so a resolution change does not invalidate your work.
04
Act on verified alerts
Related signals correlate into one incident, the permitted evidence is attached, and it routes to the person on duty — in-app, on an approved WhatsApp template, or into your own systems by signed webhook. One tap marks it a false alert, and that feedback is measured rather than swallowed.
WHERE IT RUNS
Same platform. Different first rule.
Nothing here is a separate product or a separate price. What changes is which rule gets drawn on day one — and that is a conversation, not a dropdown.
01
Warehousing & logistics
Yards are large, staffed thin at night, and full of things worth taking.
FIRST RULETripwire across the loading gate, inbound only, outside shift hours
02Banking & financial services
When an auditor asks for last Tuesday, the answer cannot be a shrug.
FIRST RULERecording verification on every branch camera, every day, with a monthly report
03Retail
Shrinkage is a measurement problem long before it is a camera problem.
FIRST RULEAfter-hours presence, plus merchandise-removal patterns in controlled pilot
04Estates & facilities
One guard, forty cameras, and a screen nobody has looked at since Tuesday.
FIRST RULERestricted-area polygons on plant rooms, dwell thresholds on perimeter roads
05Critical infrastructure
A camera aimed at a wall passes every uptime check ever written.
FIRST RULEIntegrity checks first — tamper, obstruction, clock drift, agent silence
06Hospitality
The risk is in the corridors guests never see.
FIRST RULEBack-of-house zones and service entrances, scheduled around trading hours
See it on your own cameras.
Bring your existing footage. We'll show you what Blepo finds in it.