Hydrocephalus is the most common neurosurgical condition worldwide. AURORA-HYDRO models the cerebrospinal compartment as a coupled mechanical system across formation, decision-making and lifetime monitoring.
A non-functional preview of the AURORA-HYDRO surface. Composable panels, logged overrides, explainable end-to-end. Pilot sites tune this to their own workflow.
HYDRO-COMPFORM Compartment Formation84%HYDRO-COMPDECIDE Compartment Decision71%HYDRO-COMPLIFE Compartment Lifetime62%AURORA-HYDRO models the cerebrospinal compartment as one continuous problem from birth to old age. Three subsystems cover formation physics, the shunt-vs-ETV decision, and lifetime compartment surveillance.
Hydrocephalus is the most common condition treated by neurosurgeons worldwide. The compartment is governed by a small set of physical laws that most clinical systems do not model coherently. AURORA-HYDRO treats CSF dynamics as one continuous problem across the lifespan — congenital, post-haemorrhagic, post-infectious, and normal-pressure.
The shunt-versus-ETV question is well-studied — the ETVSS captures much of the easy signal — but personalised priors remain rare. AURORA-HYDRO carries a compartment model into the decision so success probability is grounded in physics, not just population statistics.
Lifetime compartment surveillance is the most under-served piece. Most patients with a shunt will need at least one revision. AURORA-HYDRO's lifetime-watch subsystem reduces the chance that a slow trajectory becomes a late emergency.
We are not building a product around Hydrocephalus. We are seeding an infrastructure — so that any hospital with the will to use it can.
AURORA-HYDRO treats the cerebrospinal compartment as one continuous problem from birth to old age. The shunt-vs-ETV branch shares a calibrated prior — ETVSS-aligned, with patient-specific flow signals layered on top.
Every AURORA-HYDRO subsystem can be adopted alone or as part of the bundle. Each ships with its own model cards, eval results and a one-command install.
CSF production, absorption and pulsatile transmantle pressure model.
CSF production / absorption / pulsatile pressure model. Patient-tuned during onboarding.
Shunt vs. ETV decision support with personalised flow priors.
Shunt vs. ETV decision support with personalised flow priors and ETVSS-aligned baselines.
Lifetime shunt surveillance, infection and revision forecasting.
Lifetime shunt surveillance — infection, malfunction and revision forecasting from telemetry-light signals.
Inputs the module reads from your existing systems, outputs it returns to them, the protocols it speaks, and the lifecycle of one case as it moves through AURORA-HYDRO.
CSF production / absorption / pulsatile pressure model. Patient-tuned during onboarding.
Shunt vs. ETV decision support with personalised flow priors and ETVSS-aligned baselines.
Lifetime shunt surveillance — infection, malfunction and revision forecasting from telemetry-light signals.
3 drafts by the module team and pilot collaborators. Each documents one slice of the substrate — methods, evaluation protocol, lessons. Slot PDFs in as they're ready; the entries point to placeholders until then.
These are the endpoints AURORA-HYDRO is built to measure across pilot deployments. The targets below are pilot goals, not retrospective results.
On networks running lifetime watch (target).
Brier-score improvement vs ETVSS baseline.
End-to-end across compartment models.
Earlier triage via lifetime watch.
Every override logged with reason.
Better selection of shunt-responsive iNPH candidates.
pip install to a hospital deploy in one afternoon.Available to pilot partners today on private registries. At public alpha (Q4 2026) the same images, weights and signatures ship under MIT on public registries. For the full per-product download grid, see the unified download page.
pip install aurora-hydro
aurora doctor hydro # → AURORA-HYDRO ✓ python ✓ compartment model # → three subsystems loaded # → ready in target ≤80ms
from aurora.hydro import decide plan = decide(case_id="bench/hydro/case-0014") print(plan.recommend) # → "ETV" print(plan.success_prob) # → 0.71 ± 0.06
AURORA-HYDRO is designed to run on hardware that already exists inside hospital networks. CPU-only inference is supported for the lighter subsystems; the heavier ones benefit from a recent GPU but do not require one. A single modern workstation handles routine cases under the latency target.
Federated deploys do not require open inbound ports. The runtime opens an outbound mTLS connection to the federation control plane; model updates are signed, audited and pulled. Patient data never traverses the federation. Consent metadata is a first-class object — subsystems with an explicit consent dependency refuse to run on records that lack the appropriate cohort policy.
Most pilot sites land on AURORA-HYDRO with an existing system in place. The recommended path is: install alongside, compare outputs on a held-out cohort for one quarter, then move read-only surfaces to AURORA, and decide on the rest. Reversibility is a design goal — nothing in the install creates lock-in.
For the full per-product, per-platform download buttons (macOS / Windows / Linux installers + pip / docker / helm / rust commands), see the unified download page. Each subsystem of AURORA-HYDRO is independently downloadable there.
AURORA is in private pilot today and opens to the world at public alpha in Q4 2026 under MIT. If you carry the weight of these diseases — as a clinician, scientist, builder, patient or advocate — there is a seat at the table.