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

The facts, from the register.

ProductPharoah Mobile Shield
Register keypharoah-mobile-shield
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atshield.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£6 one-off
Built from1 register parts, 0 live, 1 probe-verified

What it does

A defensive Android app for the GhostWire secure phone: nine baseband anomaly signals read from public, unprivileged APIs, so the handset can tell you when the network around it is behaving wrongly.

Runs on

Pharoah Mobile Shield
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 NCSC Cyber Assessment Framework.

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

Assets and access under control

Check 2

Detection with an evidence trail

Check 3

Response rehearsed, not improvised

Frame chosen by BRG as a summary of the NCSC Cyber Assessment Framework. 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.

Phones are the least protected device in an estate and the one carrying the most.

Who carries it

Organisations using GhostWire secure phones seeking enhanced app security.

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

What it does instead.

When your secure phone system needs enhanced app security features, Pharoah Mobile Shield keeps your data protected and compliant.

A defensive Android app for the GhostWire secure phone: nine baseband anomaly signals read from public, unprivileged APIs, so the handset can tell you when the network around it is behaving wrongly.

The parts doing the work

Pharoah Mobile Shield verified

PRD-4 Phase 4. Defensive Android app (Kotlin/Compose, minSdk29/targetSdk34/arm64) for the GhostWire secure phone. Repo: github.com/ATTOH-DIGITAL/pharo

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

Proof it exists, not a roadmap.

200

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

1/1

register parts verified by probe

0

parts wired live

HTTP 200

functional surface probe

Open shield.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: mobile application security and hardening. Nearest rivals: Lookout, Zimperium, Samsung Knox, Guardsquare, Appdome; strongest is Zimperium in mobile threat defence. Our edge: rivals secure a standard handset fleet under an MDM; we add application-layer hardening to an already-secure phone platform, which is the layer a hardened deployment still lacks once the device itself is locked down. How we beat them: we assume the device is already secure and address what remains, rather than reselling device management.

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.

Organisations using GhostWire secure phones seeking enhanced app security.

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.

£6 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
Pharoah Mobile Shieldbackendspec
Source: product_parts joined to builder_blocks · 1 of 1 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 NCSC Cyber Assessment Framework 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 Mobile Shield, as a package.

backend

Pharoah Mobile Shield

PRD-4 Phase 4. Defensive Android app (Kotlin/Compose, minSdk29/targetSdk34/arm64) for the GhostWire secure pho

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

A package reads like a control document.

Inside the scope

  • Pharoah Mobile Shield

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

  • DEVICE-CLASS: no public URL by design. Distribution = GhostWire fleet provisioning (update-phones.sh step 8, a
  • 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
  • 1 build packet proposed · 1 management item 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 Mobile Shieldshield.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 NCSC Cyber Assessment Framework. 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 NCSC Cyber Assessment Framework; 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.