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

The facts, from the register.

ProductPharoah Wire
Register keypharoah-wire
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atwire.pharoahtechnology.co.uk · HTTP 200 on 9 September 2026
Price£29 a month · [object Object]
Built from5 register parts, 5 live, 3 probe-verified
Listed14 August 2026

What it does

An encrypted store-and-forward messaging relay that runs on your own domain. Only signed requests are accepted — unsigned traffic is refused — with push notifications and a hardened channel for passing data between devices. Voice and video relay stays off by default until you add a real-time tier.

Runs on

ghostwire relay v130
Ghostwire Core
Relay flood-cap
Wire lane depot
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 buyer's own change-control.

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

A control between the work and the submission

Check 2

A process fit for this buyer, not a generic one

Check 3

Readiness for the next rule change

Frame chosen by BRG as a summary of the buyer's own change-control. 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.

Messaging relays accept unsigned traffic, so the relay itself becomes the weak point.

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

What it does instead.

Pharoah Wire exists to solve: Messaging relays accept unsigned traffic, so the relay itself becomes the weak point.

An encrypted store-and-forward messaging relay that runs on your own domain. Only signed requests are accepted — unsigned traffic is refused — with push notifications and a hardened channel for passing data between devices. Voice and video relay stays off by default until you add a real-time tier.

The parts doing the work

ghostwire relay v130 verified

Source registration for ghostwire-relay-v130: relay/worker.js at 6530e3aaa389d3c7d3463b1ca947fd3bcd271f18 (anchor line 8). Source inspected; runtime,

Ghostwire Core verified

Registered from existing live product_parts during 2026-07-05 Codex register-integrity repair. Products: ghostwire. Existing part status=staged, gap_t

Relay flood-cap

GhostWire relay MAX_PENDING=2000 per-recipient cap. Deployed live v6ed60b04; source on pharoah-wire main.

Wire lane depot

Canonical repo (client+relay) + CLAUDE.md lane rules; both lanes build here. Pushed 67f378d, handoff posted.

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

Proof it exists, not a roadmap.

200

HTTP status of wire.pharoahtechnology.co.uk on 9 September 2026 · real-content-verified

3/5

register parts verified by probe

5

parts wired live

HTTP 200

functional surface probe

Open wire.pharoahtechnology.co.uk 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.

PHIL CORRECTION 16 Jul (builder's direct call): vault-messenger and pharoah-wire are the same GhostWire family, nearly complete. Live evidence backs this: ghostwire-relay.craig-45c.workers.dev deployed+verified end-to-end zero-knowledge store-and-forward (D1-backed, ciphertext-only storage, 14d TTL purge) - relay is production-ready. Android: RSA-4096 release signing key minted, GW-PROTO-1 relay half proven, invite-accept path built+verified. Per Phil (the builder, direct product knowledge): this beats Signal/Silent Circle/Rocket.Chat on its protocol design once assembled - overriding the prior conservative hold, which was based on register notes alone rather than the live build state. Gate PASSED on builder's authority + live relay evidence.

Evidence: ghostwire-relay.craig-45c.workers.dev · production-ready. · built+verified. · Circle/Rocket.Chat · state.

Not independently sourced This verdict was written from an analysis whose only source was the model itself, not scraped competitors (analyst gtm-loop-worker). 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_competition (18 August 2026)Named 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.

Not in the register yet an audience. This slide stays blank until the register carries it; nothing here is invented.
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.

£29 a month

Basis: [object Object]

Buying route

Payment on enquiry
ready-to-use
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
ghostwire relay v130backendbuilt
Ghostwire Corefull-stacklive_wired
Relay flood-capbackendlive_wired
Wire lane depotbackendlive_wired
Ghostwire Relayfull-stacklive_wired
Source: product_parts joined to builder_blocks · 5 of 5 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 buyer's own change-control 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 Wire, as a package.

backend

ghostwire relay v130

Source registration for ghostwire-relay-v130: relay/worker.js at 6530e3aaa389d3c7d3463b1ca947fd3bcd271f18 (anc

verified

Relay flood-cap

GhostWire relay MAX_PENDING=2000 per-recipient cap. Deployed live v6ed60b04; source on pharoah-wire main.

live_wired

Wire lane depot

Canonical repo (client+relay) + CLAUDE.md lane rules; both lanes build here. Pushed 67f378d, handoff posted.

live_wired
full-stack

Ghostwire Core

Registered from existing live product_parts during 2026-07-05 Codex register-integrity repair. Products: ghost

verified

Ghostwire Relay

DEPRECATED/SUPERSEDED 27 Aug 2026. This block refers only to https://ghostwire-field-relay.craig-45c.workers.d

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

A package reads like a control document.

Inside the scope

  • ghostwire relay v130
  • Ghostwire Core
  • Ghostwire Relay

Evidenced, and how

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

Outside the scope today · work left

  • Signup, authenticated messaging, encrypted relay, and subscription entitlement have not been freshly proved as
  • 2 parts still to verify by probe
  • 2 register fields to fill (vs_competition_unsourced, audience)

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 1 build packet proposed · 4 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 Wirewire.pharoahtechnology.co.uk
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 buyer's own change-control. 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 buyer's own change-control; 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.
  • Fields missing from the register for this product: audience. Fill the register, regenerate; do not improvise on stage.

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.