Big studies, and every one of them sensitive
Tele-radiology and second opinions move DICOM studies between sites: CT and MRI series of hundreds of megabytes to tens of gigabytes, and whole-slide pathology images of 1 to 5 GB each. Clinical trial imaging goes from sites to a CRO on a schedule, and research cohorts run to terabytes. Ordinary uploads over TCP are slow over distance and fail on large studies, and consumer sharing tools give a compliance officer nothing to sign off.
Moved intact, and you can show it
Boita moves data with an accelerated transfer engine over UDP with its own rate control, at your line rate whatever the distance, in parallel sessions sized to your plan. The desktop app resumes by itself after a drop, sleep, restart or quit; a browser transfer starts again. The server records a checksum for every file on arrival, so a truncated series is caught before anyone reads it, and the delivery receipt lists each file with its checksum, who downloaded it and when, with a CSV verification report (PDF on Scale and above).
Boita is not a PACS and does not interpret DICOM. It does not read or modify headers, anonymise, or render a study; it moves the files exactly as they left and keeps a record of the movement. Consent, de-identification and the legal basis for sharing remain yours.
Controls on every link
Every share link has an expiry, an optional password and a download limit, and can be revoked at any time; download tokens expire in minutes, so revocation stops resumed downloads too. Recipient verification asks the clinician to confirm their email with a one-time code before anything about the files is shown, so the receipt names who downloaded. Sender-side encrypted delivery with a passphrase encrypts files on your machine before they leave it and decrypts them on the recipient’s; Boita never holds the passphrase and cannot see the contents. If you want no image of a study rendered on our servers, previews can be switched off per link.
A referring site sends a study in through an upload portal with a form for the study identifier; each upload lands in its own dated inbox folder on a token that can write there and nowhere else.
A worked example
A 20 GB MRI study reaches a reading centre from a hospital on Pro, over a 1 Gbps line, in about six minutes, plan-limited at 450 Mbps. A 200 GB batch of trial imaging to a CRO on the same plan and line takes about an hour. The calculator on the home page models your own line and distance.
- DICOM, NIfTI and whole-slide files moved as they are; checksum on every file
- Recipient verification by email code; password links; expiry and revocation
- Sender-side encryption so Boita never sees contents; previews off per link
- Audit log on every plan; SIEM export, IP allow-lists, device policies, retention rules and legal hold on Enterprise
- Data in India (Mumbai); DPDP statement published
Where the data lives, and who can reach it
Files and the transfer server run in Google Cloud, Mumbai; each workspace has its own storage root and encryption key, and the trust page lists every sub-processor. A per-workspace audit log records logins, shares, downloads, deletions and admin actions, on every plan. Enterprise adds audit export to your SIEM, IP allow-lists and device policies so staff reach the workspace only from approved networks and computers, retention rules per folder, SSO and SCIM, and a legal hold that stops anything being deleted until it is lifted.