For vendors.
Your product needs population-scale answers; building the data layer that produces them is years of work that isn't your product. Radial is that layer, offered in whatever shape your product needs.
Three ways to ship it
The platform inside your product
Radial runs as a component of your deployment, including on-prem alongside your own install.
Your UI, our engine
Curated cases, metrics, and DICOM operations through the versioned REST contract.
Or white-label: the analytics under your brand, scoped as part of the OEM engagement. All three shapes share the property that matters: your customers' data stays in your product and their institution, not in a third party's cloud.
Independence, structurally
Oncurate has no treatment-delivery, planning, or OIS business. Building on Radial doesn't put your roadmap on a competitor's platform, and it doesn't route your customers' data through a rival's infrastructure: a structural fact worth more than any partnership clause.
What you're not rebuilding
Under the contract is the part that takes years: a hardened DICOM-RT ingestion and normalization engine, the TG-263 mapping dictionary that learns per deployment, and a validated DVH engine with public lineage, checked against known-answer reference cases so the numbers underneath your integration are ones you can stand behind.
The design-partner offer
The API contract is young and deliberately still shapeable. An early vendor doesn't adapt to our decisions; they sit at the table where the decisions get made, while breaking changes are cheap and the surface can bend toward their product.