01Pharoah Technology · pharoahlive
Pharoah Control
The estate's operations root: one place that knows what exists, who can reach it, and what changed.
Live · control.pharoahtechnology.co.ukFree22 parts · 13 probe-verified
Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)control.pharoahtechnology.co.uk
02What it is
The facts, from the register.
| Product | Pharoah Control |
| Register key | pharoah-control |
| Owner | Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50) |
| Live at | control.pharoahtechnology.co.uk · HTTP 200 on 9 September 2026 |
| Price | Free · [object Object] |
| Built from | 22 register parts, 9 live, 13 probe-verified |
What it does
Pharoah Control provides estate operations teams with a single view of assets and access rights, showing what exists, who can reach it, and what has changed, eliminating scattered secrets and control surfaces.
Runs on
Infisical shared-secret-vault
System gap + ingestion register
Register drain generator (self-healing register)
GTM Outreach Engine
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 Propertymark and RICS client-money rules.
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
Client money protected and reconciled
Check 2
AML checks before the deal, not after
Check 3
A redress trail for every instruction
Frame chosen by BRG as a summary of Propertymark and RICS client-money rules. 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.
Secrets and control surfaces are scattered, so nobody knows who can reach what.
Who carries it
Estate operations teams requiring centralised visibility of assets and access control.
Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose
What it does instead.
The estate's operations root: one place that knows what exists, who can reach it, and what changed.
Pharoah Control provides estate operations teams with a single view of assets and access rights, showing what exists, who can reach it, and what has changed, eliminating scattered secrets and control surfaces.
The parts doing the work
Infisical shared-secret-vault verified
Every deploy's secrets — check the vault before asking for keys.
System gap + ingestion register verified
The standing self-test register. Live probe of all captured companies showed we notice identity but ingest almost no real data (3/668 with SIC, 0 with
Register drain generator (self-healing register) verified
Reads the live register, finds owned tools no product/agent uses + unmapped products, files one lane_handoff each (dedup + capped) so the register-fir
GTM Outreach Engine verified
Vertical-agnostic, global, always-on outbound GTM. A vertical = a gtm_vertical config row (pain wedge, killer feature, channels, pricing, winning temp
Source: register purpose, public_blurb, product_parts joined to builder_blocks4 of 22 parts shown
06Why it's better · 3 of 6Check 1 · controls
Proof it exists, not a roadmap.
200
HTTP status of control.pharoahtechnology.co.uk on 9 September 2026 · real-content-verified
13/22
register parts verified by probe
HTTP 200
functional surface probe
Open control.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.
Category: post-deployment operational assurance. Nearest rivals: Datadog, New Relic, Grafana Cloud, PagerDuty, Better Stack; strongest is Datadog. Our edge: observability platforms tell you a metric moved and leave the operator to decide whether the deployment is actually sound; we assert operational integrity after release — that the thing shipped is the thing running and still doing its job. How we beat them: per-host and per-metric pricing serves large SRE teams, while a UK software operations manager wants a verdict on the release, not a dashboard to interpret.
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.
Estate operations teams requiring centralised visibility of assets and access control.
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.
Free
Basis: [object Object]
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.
| Part | Category | State | Verified |
|---|
| Infisical shared-secret-vault | integration | live_wired | |
| System gap + ingestion register | backend | live_wired | |
| Register drain generator (self-healing register) | backend | live_wired | |
| GTM Outreach Engine | data | live_wired | |
| Parts Register Watch — register coverage and drift guard | backend | built | |
| Expense Management | full-stack | live | |
| Register Counter Integrity Guard (honest readiness inputs) | backend | live_wired | |
| Meeting Note Taker — universal transcript→notes engine | backend | live | |
| Supabase + RLS | integration | live_wired | |
| AI gateway budget guard (KHUFU) — ARMED | backend | built | |
Source: product_parts joined to builder_blocks · 10 of 22 shown probe-verified not yet
11Why packaging matters
Bought as a price.
Delivered as a scope.
What the buyer hears
Free
A number to compare with the last number.
the gap
disputes · churn
unpaid work
What the provider means
A scope
22 parts, some verified, some not, plus everything that is excluded.
Packaging is the instrument that makes the scope as visible as the price.Thesis
12Why packaging matters
Five things a package does that a price cannot.
1Scope becomes visible. The parts are named, so nothing is assumed.
2Boundaries are explicit. What is outside is written down before the first invoice.
3It is auditable. A package is a documented process, which is what Propertymark and RICS client-money rules looks for.
4Buyers compare like for like. A referral needs a defined thing to refer.
5Switching 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 Control, as a package.
integration
Infisical shared-secret-vault
Every deploy's secrets — check the vault before asking for keys.
verifiedSupabase + RLS
Multi-tenant Postgres rail with forced RLS, policy-derived least privilege, born-safe DDL and reviewed client
verifiedbackend
System gap + ingestion register
The standing self-test register. Live probe of all captured companies showed we notice identity but ingest alm
verifiedRegister drain generator (self-healing register)
Reads the live register, finds owned tools no product/agent uses + unmapped products, files one lane_handoff e
verifiedParts Register Watch — register coverage and drift guard
Repeatable proof/report guard that watches register coverage, v_register_drift and operator alias gaps so ever
verifiedRegister Counter Integrity Guard (honest readiness inputs)
FIXES a systemic board lie: readiness_pct is a GENERATED column whose formula was correct but whose INPUTS lie
live_wireddata
GTM Outreach Engine
Vertical-agnostic, global, always-on outbound GTM. A vertical = a gtm_vertical config row (pain wedge, killer
verifiedfull-stack
Expense Management
Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and rei
liveSource: product_parts grouped by builder_blocks.category4 groups
14Anatomy of the packageOn one page · 10 items of work left, filed
A package reads like a control document.
Inside the scope
- Infisical shared-secret-vault
- System gap + ingestion register
- Register drain generator (self-healing register)
- GTM Outreach Engine
- Parts Register Watch — register coverage and drift guard
Evidenced, and how
- Live URL probed: HTTP 200 on 9 September 2026
- 13 parts probe-verified, latest 16 July 2026
- Functional surface: HTTP 200
- Register row updated with every probe
Outside the scope today · work left
- Internal estate tooling (local scripts + protocol docs); parts 6/19; no public surface by design.
- 9 parts still to verify by probe
Who signs, and where the work sits
- Pharoah Technology Ltd owns the product and the data layer
- 1 build packet proposed · 9 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 Controlcontrol.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
16Close
Three things to take back to your desk.
One
Open the URL on slide 6. Test it before you trust it.
Two
The parts and their verification state are on slide 10.
Three
A package is a compliance instrument, not a price list.
See it live
control.pharoahtechnology.co.uk
Talk to us
via control.pharoahtechnology.co.uk
Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)Pharoah Technology