HENQThe application platform
Open-source application platform
HENQ is an open-source software platform for building and operating applications. It manages their data, permissions, AI execution and shared services on infrastructure your organization controls.
Establish a common reference foundation and require projects to build on it or demonstrate conformity. Institutions retain control of adoption, conformance requirements and procurement, while suppliers compete on the systems they build.
HENQ provides the software, published architecture and repeatable tests to put that foundation into practice.
Your products
Public services · Healthcare · Finance
The software platform you operate
Your environment
Computing · Storage · Service providers
Your teams build the applications.
HENQ provides the services they run on.
01 / What HENQ is
A hospital builds a referral service. A bank builds a review system. An agency builds a permit service. Each defines its own work and uses HENQ to manage the data, permissions and shared services behind it.
The platform
Install and operate HENQ on infrastructure you control. Application teams define their data models, relationships, workflows and user experience. They call HENQ services to store information, check permissions, run approved work and exchange data.
Teams do not need to assemble those shared services again for every application.
The published design explains how the software works, how its controls fit together and what an application can rely on.
Institutions can make those requirements part of procurement and acceptance. Projects can use HENQ or demonstrate that another foundation meets the adopted requirements.
Open architecture means inspectable code, documented interfaces and requirements institutions can reuse. HENQ uses the Apache 2.0 license.
02 / Control, built in
HENQ manages the data and controls how applications access it. Applications cannot bypass those controls with direct database access. Your institution chooses where the system runs and which providers it uses.
Sensitivity, compartments and handling rules govern access, derived results and release. An AI-generated summary is not permission to disclose its sources.
Models and agents work inside approved scopes, with human review where required. Generating a proposal and authorizing an action remain different powers.
Each operation records who acted, what permitted the action and which version of the information was used. Investigators and auditors can follow that record.
03 / Across sectors
Protect a patient record, approve a financial decision or share an intelligence assessment. The applications differ; each needs control over access and clear responsibility for decisions.
Healthcare
Give care teams the records they need and use AI to support clinical work. Access to a patient’s information follows the care relationship and the purpose of the task.
A specialist referral
Finance
Support investigations, risk analysis and approvals with a record of the evidence and decisions. An automated recommendation still needs the required authorization before money moves or an account changes.
A high-impact review
Public administration
Let agencies verify the facts needed for permits, benefits and public services. Each exchange has an approved purpose and recipient; agencies do not need permanent access to one another’s databases.
The application manages a permit request. HENQ manages access to its records, approval permissions, supporting documents and exchanges with other agencies.
An interagency verification
Education
Help educators prepare learning plans and use AI in their teaching. Student records stay restricted to authorized users, and educators retain responsibility for decisions that affect learners.
A learning-plan proposal
Defense & intelligence
Give analysts access to authorized sources and preserve the origin and restrictions of their findings. Combining or summarizing information does not remove its classification or release requirements.
An assessment for a partner
04 / Information exchange
Manage records, files and information exchange under the same permissions, protection and audit rules.
Known versions.
Integrity and protection rules.
Recipient · purpose · permitted data
Expiry · access limits · delivery record
A trusted HENQ installation
or a conventional external client.
Connect through familiar interfaces. A documented exchange contract tells partners how to authenticate, request approved information and meet its handling requirements.
Know the limits after delivery. Expiry and access limits govern requests to HENQ. Downloaded copies cannot be recalled, and offline reading cannot be counted. Recipient trust and agreed handling conditions still matter.
Institutional control
With HENQ, institutions set the rules for their digital services. Application teams and suppliers build within them.