Work / Cinray
Case study · Dental imaging
A cloud CBCT platform that cuts dental report time from 40 minutes to 15
Cinray is a web-based SaaS DICOM viewer platform. Dental imaging teams view CBCT scans, take measurements and produce structured reports in the browser, with nothing to install. We shaped the architecture, built the platform, and support its go-to-market.
Client
Cinray, founded by a dental clinic chain
Product
Web-based SaaS DICOM viewer for CBCT
Built for
Imaging centres, clinic chains and hospitals with dental practice
Our scope
Strategize, Build, Operate
40→15
Minutes to prepare a CBCT report end to end.
28
Structured report templates, grouped by type of assessment.
4
User roles with separate, configurable permissions: clinic admin, technician, radiologist and doctor.
0
Software to install. Centres log in from a browser and start reading scans.
The challenge
Reporting was the slowest part of the job
A CBCT scan of the jaw holds hundreds of image slices. Turning one into a report means finding the right views, measuring roots, canals and bone, and writing structured findings tooth by tooth. The founder’s own endodontic report templates run to more than 40 pages. Preparing one report took around 40 minutes.
The tools that do this well are usually desktop software sold on a licence and installed on each workstation. That is a steep cost for imaging centres and clinic chains, and it ties the work to specific machines.
The founder wanted a different model: a SaaS DICOM viewer and reporting platform that runs in the browser, is paid for per study, and takes a report from scan to signed PDF in a fraction of the time.
01 · Strategize
Decisions made before any code was written
We worked through the architecture with the founder first. These choices shaped what the platform could cost to run and how quickly it could ship.
Browser first
Everything runs in a web browser, so a centre can start with a login. No installation, no workstation licences.
Proven imaging core
The viewer is built on OHIF and Cornerstone3D, open-source medical imaging frameworks, with licences checked before integration. This put development time into dental workflows instead of rebuilding image rendering.
Storage that matches use
Scans are read heavily in the first weeks and rarely after. Older studies move automatically to lower-cost archive storage, which keeps running costs in line with a per-study price.
Roles from day one
Access is built around how a centre actually works: who uploads, who reports, who reviews. Permissions are set per role rather than per person.
02 · BUILD
The hard parts of building it
A dental CBCT platform asks a lot of a web browser. These were the parts that took the most engineering.
3D imaging in the browser
A CBCT study holds hundreds of image slices. The viewer loads the full volume and renders it in four linked views, a 3D volume plus coronal, axial and sagittal slices, that stay in sync as the user moves through the scan. Lengths, angles and notes are measured directly on the image.
Panoramic reconstruction
Pano mode rebuilds a panoramic image along a curve the user traces on the dental arch, with cross-sectional slices along it, all computed in the browser.
A reporting engine for clinical templates
28 structured templates with per-tooth conditional sections, measurement tables that adapt to each tooth’s anatomy, and reference image grids. Images captured in the viewer go straight into the report, and patient details fill in from the scan’s metadata.
Two people, one report
A technician and a radiologist can edit the same report at the same time without overwriting each other’s work. The final PDF locks on save and reopens only when a doctor asks for re-evaluation.
Roles, notifications and sharing
Four roles with configurable permissions, email and phone call notifications as a study moves forward, and finished reports shared by email or WhatsApp.
Security
Data encrypted at rest and in transit, with access controlled by role.
03 · OPERATE
Taking it to market
Beyond the platform, we built cinray.in, the product’s public website, and support its go-to-market.
THE RESULT
From scan to signed report in 15 minutes
In early use, report preparation has dropped from around 40 minutes to 15. Centres get a full CBCT viewer and structured reporting with no installation and no licence, paying per study.
technology
What it runs on
Front end
React · OHIF · Cornerstone3D
Back end
Node.js · PostgreSQL
Cloud
AWS EC2 · Amazon S3 · AWS Lambda · Amazon SNS · Amazon SQS · Amazon CloudWatch
Security
Encryption at rest · Encryption in transit · RBAC
Have something to plan, build or run?
Tell us what you are working on. We will come back with how we would approach it.