Sovereign by design, enterprise by default
Clinician-led clinical AI that runs on-premises, inside the hospital. Governed compute from the bedside to the province, so patient information stays under the custody of the institution responsible for it.
What Criticalinsights™ builds
Criticalinsights™, founded by clinicians and AI engineers, builds clinical AI that lives entirely inside the institution: the compute, the bedside intelligence, the governed clinical knowledge, and the connection to patients and families. Nothing leaves the boundary, and no third party holds the keys.
Criticalinsights builds the foundation. Clinical AI runs on top of it: ours, the hospital's own, or any vendor's, all governed the same way.
Engineered for the standards North American healthcare runs on
The safety property built into the platform, not a setting on top of it. A qualified human holds the judgement and the accountability: every model, agent, and workflow is designed to inform that person and stop at them.
The system surfaces evidence, risk, and reasoning. It does not order, prescribe, or act on a patient. Every clinically consequential step waits on a named person with the authority to take it.
Anything sensitive routes to explicit human approval before it takes effect. The approval gate is enforced in the platform itself, not left to policy documents or user discipline.
Every output carries what it drew on, what it was missing, and how it was formed, so the reviewing clinician can accept, question, or reject it on the evidence rather than on trust.
The operator, the custodian, the key-holder, and the approver are the institution's own people. Clinical accountability is never transferred to a model or to us.
Sovereign by design, enterprise by default
System architecture
CRATON, the Criticalinsights™ sovereign stack
Data residency follows stewardship at every tier. Patient information stays with the organization legally responsible for it; only structure and learning move between tiers.
Products
Sovereign platform
The hospital's control layer for AI: one governed runtime for every assistant, agent, and workflow, deployed single-tenant inside the institution's boundary. The institution sets the boundaries, the safety rules, and the approvals; SALVEA enforces them everywhere with role-based access, human-in-the-loop sign-off, and a complete audit trail. Zero data egress, the clinician's final say.
Explore SALVEACritical care
The bedside critical-care platform: TRINITY, the intelligent bedside integration hub, and IMPACT, the clinical dashboard on top of it. Continuous capture from monitors, devices, and record systems, with risk computed on premises.
Explore the bedside platformClinical reference
The institution's own approved monographs, protocols, and guidelines: version-controlled, pharmacy-governed, and reachable by every clinician at the point of care. No patient information is entered, processed, or stored.
Explore CELSUSGrounded answering
The answering agent for the approved library. Clinicians ask in plain language and get an answer cited to the institution's own document and version, or an explicit no source found when the library is silent.
Explore CECIDocumentation
Ambient clinical documentation. The encounter that was going to happen anyway becomes a structured draft note on the unit's own compute, and reaches the record only when a clinician signs it.
Explore MINIMContact-free sensing
Posture, movement, and presence in the bedspace, read as geometry rather than imagery. Joints and limbs only: no face, no likeness, and no video stored or transmitted anywhere.
Explore FIGURAFamilies
The family app. Families stay connected to their baby's journey through the admission, with updates and family-readiness materials that build up over time, governed by the care team.
Explore CHICKADEETRIMPACT, CELSUS, CHICKADEE, MINIM, CECI, and FIGURA run on SALVEA and CRATON.
Governance architecture
Processing happens on hardware inside the facility. Nothing is sent to a third-party cloud service, and no outside party processes clinical content.
Institutional infrastructure rather than token-based pricing. Adoption can grow across the hospital without per-user costs growing with it.
Existing technology teams, and hospital-held keys and policies. The institution remains the information steward throughout.
Every action and every AI response is logged, versioned, and reviewable, so clinical decision support stays accountable.
How adoption works
Step 01
A scoped use case and a small clinical team, chosen by the site.
Step 02
Policies, access, and audit are active before the first question is asked.
Step 03
Results are reviewed against the site's own criteria, in shadow mode first.
Step 04
The site decides whether to widen the deployment, and on what timeline.
Governance & trust
Encryption, SSO/SAML identity, role-based access, and a complete audit trail, with documentation available under NDA.
We work with clinical, privacy, and information-management leadership to scope a deployment your teams can absorb and operate. Briefings are held under NDA.
