The relationship
Sit with the entity.
Ministries, authorities, governorates, and government companies in Egypt. Engineering and counsel under a written scope. Every sensitive action attributable. This is the relationship. Not a catalogue of portals.
The four columns
Sit, write, build, prove. Each column has a deliverable. None is skipped.
Deliverable
A written file
Seat
Egyptian entities
Standard
Accountable
Limit
Not a ministry
Protocol G-01
Two benches. One file.
The entity holds the mandate. The house holds the engineering and the counsel. Between them, a written scope. Nothing is committed until it can be audited.
SHIELDRA EG
Government
G-01
The protocol
Cairo
The state
The entity
- The public duty, the committee, the law that binds the work.
- Who must sign. Who must see. Who must not.
- Tender boards, technical committees, and the path a decision actually takes.
The file
Scope, controls, delivery. Written. Holdable. Auditable.
SHIELDRA
The house
- Systems the entity can run, isolate, and hand over.
- Architecture and overlays before capital or code decides.
- Encryption, access, audit, isolation. Named in the file. Not implied.
The three that must exist
The entity
The file
The house
If the mandate, the file, or the house is missing, there is no engagement.
How we sit
Four columns. Then the record.
Government work is not a sprint slogan. It is a protocol: sit, write, build, prove. Each column has a deliverable. None is skipped.
01
Sit
The mandate, the constraints, the people who must approve. We listen to the entity, not the slide.
02
Write
Scope, security controls, and delivery. In writing. Committees can hold it. Vendors cannot hide in it.
03
Build
The system as scoped. Procurement, platforms, operations, or a module. The bar is already in the file.
04
Prove
Handover, documentation, and a record of sensitive action. What closed. What remains. Named.
Who sits
The entities we sit with.
The form of the entity changes. The protocol does not. Named awards are confirmed in writing. They are not listed here as a banner.
Seat 01
Ministries
Central duty, many directorates, a record that must survive a change of chair.
Seat 03
Governorates
Local operations at scale. The same bar. The same file. The same audit line.
Seat 04
Government companies
Commercial units of the state. They trade, procure, and operate. They still need the record.
The business
What we do with the entity.
Procurement is the dedicated government path. The relationship is wider: platforms, operations, hardening, counsel, and modules when the mandate has no SKU. Open the path that matches the mandate.
- Item 01ProcurementTender, bid, evaluation, award. Accountable from registration to the record.The government path
- Item 02PlatformsInternal systems the entity runs: operations, finance, people, command.Open
- Item 03OperationsPlant, warehouse, field. If the state runs a line, the line can be engineered.Open
- Item 04HardeningSystems that already run. Raise the bar. Do not pretend it is a new build.Open
- Item 05CounselArchitecture, legal overlays, financial structure, trade. Before the spend.Open
- Item 06ModulesWhen the mandate has no boxed product. Built on the same bar.Open
The record
Every sensitive action must answer four questions.
Government systems fail in the gap between the screen and the file. We engineer so the record can be read: who, what, when, which object. That is the standard the entity can defend.
| 01Who | 02What | 03When | 04Which |
|---|---|---|---|
| An attributable actor. Not a shared password. Not an anonymous admin. | The sensitive act: approve, award, override, export, change a role. | A time the committee can trust. Not a screenshot from a demo. | The tender, the record, the file, the person. Named. Retrievable. |
Encryption, access control, isolation, and audit are selected in discovery and written into scope. PDPL, where it applies, is engineering readiness. It is not a certificate we issue.
The edges
What this relationship will not claim.
The protocol is honest. If we do not hold a mandate or a licence, the file says so.
Cl. 01
Not a government entity, a ministry unit, or a substitute for the authority that holds the public duty.
Cl. 02
Not a list of live awards. Named contracts are confirmed in writing with the entity. Team members' prior UK project histories are professional background. They are not current Egyptian government contracts.
Cl. 03
Not the State Lawsuits Authority, in-house legal, or licensed representation. Counsel here is the house overlay. Licensed work stays licensed.
Cl. 04
Not a PDPL certificate, an audit opinion, or a security guarantee. Security reduces risk. It does not eliminate it. Readiness is engineered and scoped.
In writing
Direct answers.
01
Who is this for?
Egyptian ministries, authorities, governorates, and government companies that need systems and counsel they can defend. The protocol is the same. The mandate is theirs.
02
Do you only build procurement portals?
No. Procurement is the dedicated government path. We also sit on internal platforms, operational systems, hardening, advisory, and custom modules when the mandate requires them. Each is a separate written scope.
03
Do you still work with the private sector?
Yes. Government is this relationship. Private sector remains a seat of the house. Many corridors need both. The file still names who the entity is.
04
Are you PDPL certified?
No. PDPL here is engineering readiness under Law 151, written into scope where it applies. It is not a certificate we issue.
The first conversation
Bring the mandate. We will say whether it needs a file.
What the entity must run, award, protect, or prove. We will say what belongs in the protocol, and what must stay with the authority that holds the duty.
We reply within one business day. No public pricing. Nothing is committed until it is written. Named awards are not assumed from this page.