Osprey runs on infrastructure you control. Patient data stays inside your network, every run is logged and the doctor signs every report.

The engine, the knowledge base and the model router run inside your network.
The web app, the API, the engine, the knowledge base, the vector store and the model router all sit inside the clinic network. Nothing leaves it unless you decide so.
Your network
Web app
API
Osprey engine
Knowledge base
Vector store
Model router
Outside
Install Osprey on your own servers or private cloud. You choose where it runs.
Intake, reports and knowledge stay in your network. Nothing is sent out unless you decide so.
Each run logs what the engine read, what it wrote and who signed it.
Each organisation has its own workspace, members, roles and data.
No report is final until a qualified doctor has reviewed and signed it.

Try Osprey in a test workspace first, then install it on infrastructure your organisation controls.
Osprey runs on infrastructure you control. Patient data stays inside your network, every run is logged and the doctor signs every report.

The engine, the knowledge base and the model router run inside your network.
The web app, the API, the engine, the knowledge base, the vector store and the model router all sit inside the clinic network. Nothing leaves it unless you decide so.
Your network
Web app
API
Osprey engine
Knowledge base
Vector store
Model router
Outside
Install Osprey on your own servers or private cloud. You choose where it runs.
Intake, reports and knowledge stay in your network. Nothing is sent out unless you decide so.
Each run logs what the engine read, what it wrote and who signed it.
Each organisation has its own workspace, members, roles and data.
No report is final until a qualified doctor has reviewed and signed it.

Try Osprey in a test workspace first, then install it on infrastructure your organisation controls.