Secure systems for government and enterprise
Determinds designs, builds, and maintains systems for ministries, government entities, and large enterprises working under long procurement cycles and strict security requirements, covering field invoicing, procurement tooling, policy retrieval, and the documentation a committee needs alongside them. We have deployed into seven or more secured government locations, and our team plans the procurement cycle as a phase of the project.
01 What shapes each system
Environment, procurement, and adoption
The environment comes first
Determinds settles where the workload runs, what leaves the boundary, and who holds the keys before designing the architecture, because in this sector those answers shape the design from the start.
Procurement is part of the project
Determinds plans a long approval cycle as a phase of the project, producing the documentation, security responses, and evidence your committee needs, in the form it needs them.
Training as a deliverable
Determinds scopes onboarding, documentation, and a named escalation route alongside the system, so your staff can adopt the software with confidence from launch.
02 Client engagements
Systems built inside secured institutions
01 / 04
03 What institutional buyers ask first
Residency, security, accountability, and transfer
Where the workload runs
The layer Determinds builds and owns is hosted in Egypt by default, and we deploy to your own infrastructure, a private tenancy, or on-premise where your obligations require it, documenting what leaves the environment and what stays inside.
Security review
Determinds has passed three external security audits and navigated one Central Bank of Egypt approval on a live payment platform, and the in-house information security teams at National Bank of Egypt and Banque Misr have each penetration-tested our systems.
Accountability after launch
The engineers who built your system support it after launch, under a service agreement with a 2-hour contracted resolution for priority-one incidents and a named escalation point.
Bringing it in-house
Under Build and transfer, Determinds builds and maintains the system while your team forms, then hands over the documentation, the code, and the operational knowledge on an agreed date.
04 Frequently asked
Questions institutional buyers ask
Security, data residency, procurement, and adoption.
How do you approach ISO 27001 and PCI DSS?
Determinds is the technology provider, not the certified entity. Certification sits with the financial institution, as it does with any technology vendor. Our systems operate inside our clients' compliant environments. On D-PAY, the processing core is PCI DSS Level 1 and SOC 2 Type II through Visa Acceptance Solutions, and the bank remains acquirer of record under its own licence. Determinds has also passed three external security audits and navigated one Central Bank of Egypt approval, and National Bank of Egypt and Banque Misr have each penetration-tested our systems.
Where will our data be hosted?
The layer Determinds builds and owns is hosted in Egypt by default, and we deploy into your own infrastructure, a private cloud tenancy, or on-premise where your obligations require it, documenting what leaves the environment and what stays inside. Where a system uses a language model, our team can deploy self-hosted models so content stays inside your boundary, and we settle the residency position of every third-party component with its provider during deployment.
Can you work inside a twelve-month procurement cycle?
Yes. Determinds plans the procurement cycle as a phase of the project, producing the security responses, architecture documentation, and evidence your committee needs, in the form it needs them, with a technical contact available throughout the evaluation. Our team maps where each decision sits early, so every submission reaches the committee responsible for it.
Can you deploy into an environment with no internet access?
Determinds has deployed into seven or more secured government locations where network access, device control, and physical entry are all restricted. Air-gapped and restricted environments shape the release process, the update path, and the support model, and our team designs all three from the start of the project.
What happens if we want to take the system in-house?
Determinds offers Build and transfer for exactly that. Our team builds and maintains the system while your own team forms, then hands over the code, the documentation, and the operational knowledge on an agreed date. Under Determinds’ standard terms, you own every commissioned deliverable in any case.
How do you drive staff adoption?
Determinds scopes onboarding as a deliverable alongside the system. Where staff did not choose the software, it needs to improve on their existing workaround from the first day, so our team starts from that workaround, usually a long-maintained spreadsheet, and builds from there.
Enterprise and public sector
Your security questionnaire, answered before the proposal
Determinds answers your security questionnaire before drafting a proposal, so our team maps every requirement against the architecture from the first pass.