sovereign AI for healthcare
Bifrost

Where intelligence is allowed.

Bifrost runs frontier open-weight AI models inside sovereign healthcare environments. The clinical record never leaves its jurisdiction. The intelligence it produces does.

01 / the problem

Sold as a wall.
A cost. A box ticked.

For a decade the cloud told healthcare one story. Keep the data in the jurisdiction. Keep it still. Keep it safe. Sovereignty as a wall, a cost, a box ticked so the regulator looks away.

Read it the other way. Frontier AI has the scale and the compute, and it is barred, by law, from the one archive that would make it clinically useful: the patient’s own record. The public cloud can read almost everything, except the thing that matters most.

less than3%

Health data is more than 30% of the world’s data. Less than 3% of it is ever put to use beyond the visit that created it. Not because the data is poor, but because the places large enough to compute on it are the places forbidden to hold it.

Source / EHDS secondary-use framing · European Commission · Frontiers in Digital Health, 2025

02 / what it is

Sovereign AI,
the generative kind.

Sovereign AI is simple to state. Take the strongest frontier open-weight models available, and run them inside the jurisdiction, on the real clinical record, where the data already lives. The model comes to the data. Nothing leaves the boundary but the answer.

Defensive sovereignty keeps the record still and safe, and everyone now claims it. This is the next move: the same boundary, made to produce. The record stays; the intelligence travels. Call it generative sovereignty, and the public cloud cannot follow, because its entire design is to pull your data to its compute. Bifrost does the opposite.

03 / how it works

The model comes
to the data.

Inside the sovereign boundary sits The Keep, the sovereign AI stack: a curated catalogue of frontier open-weight models, retrieval over the clinical record, and sovereign inference, operated as one unit. The Keep holds the model and the record inside the wall. The bridge carries the insight across, never the record.

03.1 / sovereign architecture

One perimeter.
Zero egress.

Sovereign architecture · BFR-04Plan view. The Keep, a sovereign perimeter labelled THE KEEP · SOVEREIGN PERIMETER · 0 EGRESS, contains four labelled blocks: clinical corpus, retrieval, frontier model catalogue, and sovereign GPU substrate. Operator clinical sits at the top edge with query and response arrows crossing the perimeter. Outside the perimeter, a dashed PUBLIC AI block is marked BLOCKED AT BOUNDARY.OPERATOR · CLINICALqueryresponseTHE KEEP · SOVEREIGN PERIMETER · 0 EGRESS01 · CLINICAL CORPUSclinical records · imaging · classifieddocuments · stays here02 · RETRIEVALvector indexes · knowledge graphsSNOMED · ICD-10 · RxNorm03 · FRONTIER MODEL CATALOGUELLAMADEEPSEEKQWENMEDGEMMAPATHOLOGYfrontier open-weight · pen-tested · refreshed quarterly04 · SOVEREIGN GPURIGHT-SIZED · BY TOKENISATIONin your jurisdiction · BYOK · BMC sealedPUBLICAIBLOCKED ATBOUNDARY
bifrost / the keep / sovereign architecture
DRG
BFR-04
REV
1.0
DTE
2026-06-17
SCL
NTS
JUR
AU · UK · EU · CA · US
CLS
PUB
03.2 / the platform

Three layers.
One platform.

These three layers are The Keep: the models, the clinical context they reason over, and the sovereign ground they run on. A builder composes against them. The platform is operated; the application is theirs.

PL / 01.1

The model layer

A curated catalogue of frontier open-weight models, validated for healthcare and version-pinned. Foundation models, clinical specialists, embedders.

Adding a model is harder than removing one.

PL / 01.2

The context layer

Per-tenant retrieval over the clinical record, fused with the model inside the perimeter. Notes, imaging, labs and medications, grounded in the standard ontologies and encrypted under tenant keys.

AI without context is guesswork.

PL / 01.3

The operating environment

Sovereign GPU and inference across six jurisdictions, operated by 3verest: deployment, compliance evidence, observability, lifecycle. You build the application. The line is drawn deliberately.

The bridge holds wherever it is built.

03.3 / who builds on bifrost

Two audiences.
One platform to build on.

Bifrost does not build the application. It builds The Keep, the platform the application runs on. Providers build for their own clinicians. Vendors ship it inside what they sell. The customer relationship, and the clinical outcome, stays theirs.

AUD / 01

Healthcare providers

Health systems · hospital groups · integrated networks

Build clinical AI for your own clinicians: discharge summaries, radiology triage, sepsis early warning. You own the application, the workflow and the patient relationship. Bifrost operates the platform underneath.

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 or white-labelled. Your customers inherit the sovereignty, the jurisdiction discipline and the evidence chain. You compete on workflow; the platform is handled.

Ship the feature. The compliance came with it.

04 / the yield

What a contained
model produces.

Inside the boundary, the archive stops being a cost to defend and becomes an asset that works.

01

Reads drafted against priors the model has actually seen.

02

Research-grade evidence assembled without a single record leaving the jurisdiction.

03

Real-world evidence that pharma and regulators can trust, because its provenance never left sovereign ground.

The wall is the reason, not the obstacle.