All decks
Pharoah Surveillance CorePharoah Technology · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductPharoah Surveillance Core
Register keypharoah-surveillance-core
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atsurveillance.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£25 one-off
Built from7 register parts, 6 live, 1 probe-verified

What it does

Lawful, tamper-evident estate surveillance with GDPR / AEPD governance built in.

Runs on

Live-view gateway config auto-sync (camera CRUD -> go2rtc)
Default Pixel Masking
External Evidence Ledger Submission
Wearable Capture
Source: estate register (products, product_parts, builder_blocks) · deploy probe 9 September 2026Evidence live
03The frameWhat this buyer's profession checks

We will measure it against the SRA Standards and Regulations.

Three checks a buyer in this field applies, whether or not they name the standard. We use them as the frame for everything that follows.

Check 1

Competence and supervision of the work

Check 2

Client money and confidentiality handled correctly

Check 3

A record that stands up if the regulator asks

Frame chosen by BRG as a summary of the SRA Standards and Regulations. Verify the wording with the body before external use.No accreditation is claimed
04Why it's better · 1 of 6Check 2 · fit for purpose

The job as the register describes it.

Estate surveillance either breaches GDPR or gets switched off, because governance was never built into it.

Who carries it

Estate owners requiring lawful, tamper-evident surveillance with GDPR/AEPD compliance.

Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose

What it does instead.

Lawful, tamper-evident estate surveillance with GDPR and AEPD governance built in.

Lawful, tamper-evident estate surveillance with GDPR / AEPD governance built in.

The parts doing the work

Live-view gateway config auto-sync (camera CRUD -> go2rtc)

pharoah-surveillance-core commit b51c048: camera create/update/delete regenerate go2rtc.yaml (atomic 0600, go2rtc-patchable YAML dialect) and surgical

Default Pixel Masking

Frame-normalised privacy-mask rectangles burned into recordings (ffmpeg drawbox) and every export/DSAR; fail-closed refusal when a masking-required ca

External Evidence Ledger Submission

HMAC-signed submission of every export/capture content-hash to an external append-only evidence ledger; retry sweep + manual resubmit; proof_token rec

Wearable Capture

Hardware-agnostic signed glasses/body-cam evidence ingest: content-hashed, attested, retained per legal profile, DSAR-covered on the same governance s

Source: register purpose, public_blurb, product_parts joined to builder_blocks4 of 7 parts shown
06Why it's better · 3 of 6Check 1 · controls

Proof it exists, not a roadmap.

200

HTTP status of surveillance.pharoahtechnology.com on 9 September 2026 · real-content-verified

1/7

register parts verified by probe

6

parts wired live

HTTP 200

functional surface probe

Open surveillance.pharoahtechnology.com during the talk. Anything the deck claims should be visible there.

Source: register deploy_probe_code, deploy_probed_at, product_parts.verified_by_probeProbed, not promised
07Why it's better · 4 of 6Against the market, honestly

Where we lead, and where we don't.

Category: public-safety surveillance platforms. Nearest rivals: Genetec Security Center, Milestone XProtect, Motorola Solutions Avigilon, BriefCam, Verkada; strongest is Genetec in government. Our edge: rivals require replacing the estate with their own cameras and VMS before anything modernises, which is why ageing public-safety systems stay ageing; we modernise on top of the hardware already installed. How we beat them: no forklift replacement and no per-channel licensing, which is the budget reality for a government security officer.

Not independently sourced This verdict was written from an analysis whose only source was the model itself, not scraped competitors (analyst pharoah). Treat the competitor names and positions as a working hypothesis until the market research is re-run; do not quote them to a buyer.
Source: register vs_competitionNamed competitors are the register's, not the presenter's
08Why it's better · 5 of 6Check 2 · fit for purpose

Built for one kind of buyer.

Estate owners requiring lawful, tamper-evident surveillance with GDPR/AEPD compliance.

Source: register audience, serves_nichesOne buyer, not everyone
09Why it's better · 6 of 6Price is part of the scope

What it costs, in one line.

£25 one-off

Buying route

Payment on enquiry
software
Scope named on the next slides, so the price has a boundary
Source: register price_gbp, billing_interval, pricing_basis, payment_link_activeNo hidden rate card
10What's inside

The parts, with their verification state.

PartCategoryStateVerified
Live-view gateway config auto-sync (camera CRUD -> go2rtc)backendbuilt
Default Pixel Maskingbackendstaged
External Evidence Ledger Submissionbackendstaged
Wearable Capturebackendstaged
Hardened Live-View Gatewaybackendstaged
Break-Glass Owner Recoverybackendstaged
Counter-Surveillance console tabbackendbuilt
Source: product_parts joined to builder_blocks · 7 of 7 shown probe-verified   not yet
12Why packaging matters

Five things a package does that a price cannot.

1
Scope becomes visible. The parts are named, so nothing is assumed.
2
Boundaries are explicit. What is outside is written down before the first invoice.
3
It is auditable. A package is a documented process, which is what the SRA Standards and Regulations looks for.
4
Buyers compare like for like. A referral needs a defined thing to refer.
5
Switching fear drops. The move is inside the package, not a project bolted on the front.
Source: BRG packaging doctrine; frame from slide 3Packaging = a compliance instrument
13This packageCut by what each part does

Pharoah Surveillance Core, as a package.

backend

Live-view gateway config auto-sync (camera CRUD -> go2rtc)

pharoah-surveillance-core commit b51c048: camera create/update/delete regenerate go2rtc.yaml (atomic 0600, go2

built

Default Pixel Masking

Frame-normalised privacy-mask rectangles burned into recordings (ffmpeg drawbox) and every export/DSAR; fail-c

staged

External Evidence Ledger Submission

HMAC-signed submission of every export/capture content-hash to an external append-only evidence ledger; retry

staged

Wearable Capture

Hardware-agnostic signed glasses/body-cam evidence ingest: content-hashed, attested, retained per legal profil

staged
Source: product_parts grouped by builder_blocks.category1 groups
14Anatomy of the packageOn one page · 7 items of work left, filed

A package reads like a control document.

Inside the scope

  • Counter-Surveillance console tab

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 1 parts probe-verified, latest 9 September 2026
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • No build gap recorded in the register
  • 6 parts still to verify by probe
  • 1 register field to fill (vs_competition_unsourced)

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 0 build packets proposed · 7 management items pending
  • Change log kept in the register
Source: product_parts (inside), deploy and part probes (evidenced), v_deck_work_left (work left; filed to manager_work and build_packets by deck_work_left_sync)One page
15Across the family

Where it hands over.

Anaïs AIgateway.pharoahtechnology.com
Anaïs AI (LLM router / reseller)anaisai.co.uk
Anaïs AI (working app)anaisai.co.uk
Pharoah TechnologyPharoah Surveillance Coresurveillance.pharoahtechnology.com
ATS Résumé Scanner (free)ats.pharoahtechnology.com
Aurora AIauroraai.pharoahtechnology.com
Aurora Guardauroraguard.co.uk
Source: register rows sharing client_key pharoahOne house, many doors
1 / 16
Arrow keys or space · N narration · P print
Slide 1Narration Words Running total

Production guide

How to turn these sixteen slides into a presentation video. Same structure as every deck in the family, so a crew that has made one can make them all.

1 · Deliverable

ItemSpec
Format16:9, 1920×1080, 25 fps, H.264 MP4 plus WebM. Burned captions and a sidecar SRT.
RuntimeNarration below plus screen captures of the live product; typically 8 to 12 minutes.
Framethe SRA Standards and Regulations. Verify the wording of the three checks with the body before external use.
BrandPharoah Technology family palette as rendered here. Green only for verified and live states; red only for exclusions.
VoiceCalm, exact, never theatrical. Read figures and dates in full. Numbers are the register's, and the register is cited on every slide.

2 · Runtime plan

#SlideNarrationWordsStarts

3 · Screen captures

4 · Full narration

5 · What this deck must not say

  • No numbers that are not on a slide with a register source.
  • No accreditation by the SRA Standards and Regulations; the frame is a lens, not a badge.
  • No named competitor read aloud unless the audience asks; the register's names are on slide 7 for the presenter.
  • No client names, volumes or tenure unless the register carries them.

6 · Regenerate

This deck is generated from the estate register. Update the product row, re-run the deck build, redeploy. Do not hand-edit this file.