The sovereign bridge between regulated healthcare data and frontier AI. A curated catalogue of frontier open-weight models, fused with the clinical context that lives inside the perimeter. Operated as a sovereign platform by 3verest. Built upon by healthcare providers and the software vendors that equip them.
01 / the platform
Three layers. One bridge.
PL / 01.1
The model layer
A curated catalogue of frontier open-weight models, selected and validated for healthcare workloads. Llama, DeepSeek, Qwen, MedGemma, pathology and radiology specialists, clinical embedders. Version-pinned, pen-tested, lifecycle-governed.
Adding a model is harder than removing one.
PL / 01.2
The context layer
Per-tenant retrieval over clinical content, fused with the model inside the perimeter. RAG over notes, imaging reports, labs, medications. Knowledge graphs linked to SNOMED, RxNorm, LOINC, ICD-10. Embeddings encrypted at rest under tenant keys.
AI without context is limited.
PL / 01.3
The operating environment
Sovereign compute across AU, UK, EU, CA, US. Dedicated inference environments tuned per workload. 3verest operates the platform substrate: deployment, model catalogue, compliance evidence, observability, lifecycle. The customer builds and operates the application. The line is drawn deliberately.
The bridge holds wherever it is built.
02 / who builds on bifrost
Two audiences. One platform.
AUD / 01
Healthcare providers
Health systems · hospital groups · integrated networks
Build clinical AI for your own staff and clinicians. Discharge summaries for the discharge team. Radiology triage for the radiology department. Sepsis early warning for the wards. The provider owns the application, the workflow, and the patient relationship. Bifrost owns the substrate.
Build the application. The platform is already managed.
AUD / 02
Software vendors and developers
EHR · PACS · VNA · RIS · LIS · ISVs · integrators
Ship sovereign AI inside the products you sell. Embedded, co-branded, or white-labelled. Customers buy your product and inherit Bifrost's sovereignty, jurisdiction discipline, and evidence chain. You compete on workflow; the AI substrate is solved.
Ship the feature. The compliance came with it.
03 / sovereign architecture
One perimeter. Zero egress.
bifrost / sovereign architecture / home / v1
DRG
BFR-04
REV
1.0
DTE
2026-05-22
SCL
NTS
JUR
AU · UK · EU · CA · US
CLS
PUB
04 / the case
AI without context is limited. Bifrost gives the model the whole patient.
CSE / 01 · PUBLIC AI
A model with fragments
A consumer-facing model trained on the open web answers from training data and whatever the user pastes into a prompt. No view of the imaging. No view of the labs. No view of the medication history. No view of the prior notes. Useful for general questions. Insufficient for clinical work, and inadmissible under regulation.
The model is fluent. The patient is unseen.
CSE / 02 · BIFROST
A frontier model with the record
A frontier open-weight model inside the sovereign perimeter, grounded in hybrid retrieval over the tenant’s clinical corpus. Imaging, pathology, lab trends, medication history, prior notes, care plans — the model reasons over the full record and cites the source on every claim. Useful for clinicians. Defensible to regulators.
The model is fluent. The patient is in full view.
05 / the moment
Sovereign AI is no longer niche. It is the next shape of critical infrastructure.
Historically, sovereign AI was a concern for the most regulated markets. The landscape has moved. Six forces are pushing healthcare providers, software vendors, and governments toward the same architectural conclusion: frontier AI belongs inside the jurisdiction it serves, under the keys of the institution that holds the record.
M / 01 · Geopolitical fragmentation
Allied jurisdictions are no longer comfortable routing critical inference through a small number of foreign-controlled providers. Healthcare data is now treated as a strategic asset.
M / 02 · Data sovereignty
AU, UK, EU, CA, US, and the Gulf states all run different regimes. The unifying instinct is the same: clinical records and the inferences drawn from them must stay inside the jurisdiction that produced them.
M / 03 · Regulatory scrutiny
HIPAA, GDPR, HDS, IRAP, HITRUST, ISO 27001. Auditors now treat AI as a system of record. The model, the prompts, and the outputs are in scope. Evidence chains are no longer optional.
M / 04 · Patient privacy
Clinical records are the most sensitive personal data a society produces. Trust in healthcare AI requires trust that the record never leaves the perimeter the patient consented to.
M / 05 · National security
Defence, intelligence, and critical-infrastructure communities increasingly view dependency on foreign-controlled AI as a strategic risk. Healthcare is on the list.
M / 06 · Distrust of foreign-controlled AI
Boards and ministers are no longer willing to defend a procurement decision that routes patient data through providers they cannot govern. The default has shifted.
06 / portfolio
3verest is the mountain. Forge builds. Bifrost crosses.