logo

Run your own teleradiology business

Start a reporting business
without building the software.

Writing a picture archive, a DICOM router and a radiology information system takes years. You can rent ours instead and put your own name on it. Your hospitals, your radiologists, your billing, your brand. We build it, we run it, and we stay out of your customer relationship.

Talk about a licenceSee the platform
What you are renting
The archive
A PACS written in Rust
At each hospital
A DICOM router
The worklist and reports
A full radiology information system
Billing and payouts
Per tenant, yours
Who operates it
We do
Figures on this page were measured on 12 September 2026 and rounded.
2
Vendors running a business on it today
Plus one on an instance of their own
60+
Hospitals under those vendors
Their customers, not ours
45,000
Studies they handled in three months
Measured, rounded
0
Servers you have to operate
On the tenant option

Two shapes

Share our deployment, or have one entirely of your own.

The software is identical. What differs is whether anything of yours sits on a machine shared with anyone else, and how long it takes to start.

  • As a tenant on our platform

    You get your own hospitals, your own radiologists, your own billing and your own branding, inside the deployment we already run. Nothing to host, nothing to operate, and you are live in days rather than months. This is how the vendors on it today started.

  • As your own instance

    The same platform deployed separately, with its own database, its own storage and its own domain. Nothing of yours shares a server with anyone else's. It costs more and takes longer to stand up, and for some buyers that separation is the whole point.

Where the line sits

Your customers never find out we exist.

A white label is worth nothing if the seams show. The tenant boundary here is not a theme on top of a shared system: ownership runs through the hospitals, the radiologists, the billing accounts, the invoices and the payouts, and it is enforced in the code rather than by filtering a screen.

A hospital you sign up appears in your worklist and nobody else’s. A radiologist you add reads for you. The report that comes out carries your header. The invoice carries your name.

We are the supplier of your software, not a party to your customer relationship.

What is yours
Domain and branding
Yours
Report header and footer
Yours
Invoice header
Yours
Hospitals and radiologists
Yours
Payment and messaging gateways
Yours
Configured per deployment, not per request.

What comes with it

The whole platform, not a reporting front end.

The router alone is also sold on its own, so a hospital that is not ready for a reporting contract can still start with the bridge.

Before you commit

What we would want to know, if we were buying this.

There is no clearance from any regulator for any part of this platform, and there is no conformance statement. If your market needs one, this is not the product for you yet, and we would rather you knew that in the first conversation.

There is no HL7 or FHIR interface. Hospital systems are connected through the router and a direct integration, which works, but is not a standards-based interface you can hand to a third party.

And the honest scale of this line is two vendors at volume plus a couple of small accounts. It is proven, not crowded. If you want a reference, ask and we will arrange one.

Say it plainly
Regulatory clearance
None, for any part
HL7 or FHIR
Neither exists
Diagnostic AI
No
Vendors at real scale today
Two
Who fixes a fault
We do

Straight answers

The questions vendors ask

Whose name is on it?
Yours. The domain, the logo, the favicon, the report header and footer, the invoice header, and the messaging and payment gateways are all configured per deployment. A hospital signing up with you sees your business, not ours.
Who reads the studies?
Your radiologists. You add them, you set which hospitals and modalities each one covers, and the assignment rules are yours. If you want our panel to cover gaps, that is a separate conversation and a separate contract, not part of renting the platform.
Can we bill our own hospitals through it?
Yes. Billing accounts, products, procedure costs, invoices and payments are per tenant, and radiologist payouts run through a draft, proposed, issued and void lifecycle so what you owe a reader and what you invoiced a hospital never drift apart.
What do we actually have to run?
Nothing, on the tenant option. On a separate instance you provide the server and we install and operate it. Either way the updates, the monitoring and the fault fixing are ours. At each of your hospitals the footprint is the router and a browser.
How quickly could we start?
The tenant route is days, because there is nothing to provision. A separate instance is longer, because a server has to exist and the domains have to resolve. The slow part is never the software, it is connecting the first hospital's scanners.
Is it proven, or would we be the first?
It is in use. Two vendors run a real business on it today, together handling roughly forty-five thousand studies in the last three months across about sixty hospitals, and one more vendor runs a separate instance of their own. We would rather tell you that than imply a large partner network.
Is the platform certified or cleared by a regulator?
No, and neither you nor we may say otherwise. There is no clearance from any authority for any part of it. What exists is an implementation of the DICOM standard you are welcome to test against your own equipment.
What does it cost?
It depends on which of the two shapes you want and how many hospitals and studies you expect. Ask us with a rough plan and we will quote against it.

Next step

Tell us what you want to run

How many hospitals you expect, whether you have radiologists already, and whether you want a tenant or an instance of your own. We will come back with a shape and a price.

Request a demoSee the platform first