For research.

Most retrospective studies spend their first months hand-building the cohort. The research license puts the full platform on a local install so that work happens once, stays current, and never requires the data to leave your institution.

Registry building without the labor

Import the archive and let curation do the heavy lift: structures standardized to TG-263 by a dictionary that learns your institution, cohorts proposed by treatment site with evidence attached, and every decision confirmed by a person and carried as provenance. The result is a defensible registry, not a folder of scripts and a spreadsheet only one lab member understands.

Analysis that answers reviewers

Query graphically across the whole cohort, read population DVH with server-computed bands, and evaluate against protocol scorecards and limit sheets, with plan-quality distributions read across the whole population. When methods are questioned, the answer is the platform's public lineage (the DVH engine descends from dicompyler-core) plus provenance on every number.

Built for how research computing actually works

A local install on ordinary hardware, no GPU requirement, no cloud dependency, and full function on a disconnected network after the one-time install. It is the shape that fits IRB expectations and equipment budgets. Collaborating sites run their own installs; the data never has to pool anywhere.

The path in

Research licensing starts with a conversation about the archive, the study, and the install. If Radial isn't the right fit for the question, we'll say so. The platform is built by people who have spent their careers on the academic side of this exchange.