Sovereign by design, enterprise by default
SALVEA. One sovereign platform. Every level of care.
SALVEA gives hospitals the ability to deploy AI on their own terms, with the boundaries, safety rules, and governance the institution sets, enforced everywhere the platform runs. Clinical teams get one place for assistants, agents, and analytics; the hospital keeps control of every model, every policy, and every key.
SALVEA runs on the CRATON (the on-premises compute architecture), and is the governed platform every assistant, agent, and workflow on it answers to.
One sovereign foundation. Everything governed.
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.
Model & product agnostic
Deploy any AI. Build your own. All inside your guardrails.
CRATON and SALVEA are model- and vendor-agnostic. Run any AI solution from any provider, or develop and deploy your own models and products, every one of them governed, audited, and held to the policies the institution sets. Your guardrails, not ours.
Governance console
Site 01 / single tenant
Policies
- No data egressOn
- Clinician sign-off requiredOn
- Retention 90 daysOn
Approval queue
Bed 04 discharge summary draft
Awaiting clinician sign-off
Unit 4 protocol summary
Pending review
Audit trail
- 14:02:11Policy set v12 applied to Unit 4 node
- 13:47:52Agent response released after sign-off
- 13:31:08Model swap requested, pending review
Agents
- Discharge summary drafterClinical
- Formulary lookupPharmacy
- Coding assistantRecords
SALVEA / governance view
One
Governed runtime for every assistant, agent, and workflow.
Zero
Data egress - nothing leaves the hospital's boundary.
Yours
The controls, the keys, and the final say - always the clinician's.
Sovereign by design, enterprise by default
Deployment paths
Three ways to bring SALVEA in: phased, top-down, or all at once
Every hospital moves at a different pace. SALVEA supports three deployment paths so the institution can choose the entry point that fits its readiness, risk posture, and governance model, and change direction as it grows.
Phased rollout
Start at one unit, prove value, then expand on the institution's own timeline. Lowest risk and a fast first win, with a clear runway to enterprise-wide governance.
Sequence
- Pilot
- Adopt
- Expand
- Scale
Best for
Hospitals that want to prove value in one unit before committing broadly.
Enterprise-first
Stand up the institution-wide policy spine and governance first, then extend downward into departments and units. Central rules and identity from day one; rollout follows.
Sequence
- Scale
- Expand
- Adopt
- Pilot
Best for
Health systems that want one governance model set centrally before any unit goes live.
All at once
Deploy across every unit and department at the same time, under one policy spine. For institutions ready to commit fully and move together from day one.
All phases live
- Pilot
- Adopt
- Expand
- Scale
Best for
Hospitals with the readiness and mandate to deploy everywhere at once.
Not sure which path fits? Book a scoping call and we'll map it to your system's readiness.
The control layer for AI
The hospital's control layer for AI: boundaries, safety, and rules, built in
SALVEA is the layer between a hospital's people and its AI. Every assistant, agent, and workflow runs under the institution's own policies (risk-tiered guardrails, role-based access, human-in-the-loop approval, and a complete audit trail), inside the hospital's own environment. Nothing leaves the boundary; no outside party holds the keys.
Clinical knowledge assistant
A grounded answering agent at ward and department level: answers with citations from the hospital's approved sources, under clinician judgement. It does not diagnose and it does not act alone.
Documentation & handover
Drafting support for notes, summaries, and shift handover, clinician-reviewed, never auto-filed.
Patient-flow forecasting
Dashboards and forecasts for beds, admissions, and discharge planning at unit and department level, with transparent model reasoning.
Low-code builder
Clinical informatics teams compose assistants and workflows without engineers, from proven blueprints.
Standards-native integration
FHIR-native interfaces and 130+ connectors reach the systems hospitals already run.
Documents, vision & analysis
Multi-model intelligence, vision and OCR, document generation, and file analysis across 20+ formats.
Governance, built in
One policy spine, everywhere
Every interaction is traced end-to-end. Risk is tiered, access is role-bound, and approval is human. The same governance applies whether a clinician is asking a question or an agent is drafting a note.
- Risk-tiered guardrails on every step
- Role-based access per user, team, and agent
- Human-in-the-loop approval on anything sensitive
- Full audit trail - who asked, what was retrieved, how the answer was formed
- Reasoning traces preserved and reviewable
- Evaluation framework against the institution's own criteria
- Cost and usage visibility for every team
Sovereignty & security
Your hospital. Your rules.
Sovereignty at SALVEA is a control-plane guarantee: the operator, the custodian, the key-holder, and the governing hand are the institution's own. No third party controls the models, the keys, or the data.
- TenancySingle-tenant, in your boundary
- Data egressZero - ever
- Key-holderThe institution
- EncryptionAt rest and in transit
- IdentitySSO / SAML, granular permissions
- AuditEnd-to-end, every interaction
How adoption works
Bottom-up, governed from the start
Step 01
One unit opts in
Start with a single unit (a subset of beds, one or two physicians, a few nurses), and a scoped use case.
Step 02
Governed from day one
Policies, guardrails, and audit run from the first conversation. The unit's leadership holds the controls.
Step 03
Expand by invitation
Department-level workflows follow when the site is ready, on the site's own decision and timeline.
Fits the Criticalinsights™ family
From the bed to the whole institution
01 / Bedside
Built to work natively with TRIMPACT (the TRINITY integration hub and IMPACT dashboard at the bedside), extending the same governed intelligence from the bed upward.
02 / Reference
Pairs with CELSUS, the governed clinical reference, so approved knowledge reaches every clinician at the point of care.
03 / Families
Extends to CHICKADEE, the family app, so the same governance that protects clinical AI protects the family experience.
04 / Stack
Runs on CRATON: on-premises compute from bedside to institution, with residency that follows stewardship.
Deployment & governance by jurisdiction
SALVEA in a Canadian health authority
SALVEA installs single-tenant inside the authority's own network. Compute and clinical data stay in-country, the authority's privacy office holds the residency requirement, and the deployment ladder starts with one consenting unit before any regional rollout.
- Data residency held in-country, on infrastructure the authority operates
- Privacy program designed to align with PIPEDA and provincial health-information law
- Provincial or authority-level policy spine applied across every site
- Clinical governance and audit review inside the authority's own committees
Frequently asked
Keys, policies, audit, and deployment
Bring sovereign AI to your hospital.
Deployed in your environment, governed by your teams, expanding only where your clinicians invite it. Technical briefings are held under NDA.