Clinical capture that never leaves your device
Doctors and clinics handle PHI every day. screenpipe captures your screen and audio locally - so patient data stays on your machine, not on someone else's cloud.
Quick answer
Local-first screen and audio capture for doctors and clinics. In local-only mode, PHI stays on your device - no cloud, no third-party processing. Open source and auditable.
See it in action
Why healthcare can't use cloud-first capture tools
Most screen recorders and AI note-takers send everything to their servers. In a clinical setting, that's a non-starter.
Cloud-first tools route PHI through third-party servers you don't control
Every cloud vendor means another BAA, data-residency review, and security audit
Closed-source apps can't be inspected before they touch a clinical machine
Consumer memory apps can change their privacy terms after you've trusted them with data
Visit context is scattered across the EHR, dictation, and chat - nothing ties it together
Local-first capture built for sensitive data
screenpipe records your screen and audio on your own device. In local-only mode, capture, OCR, and search run on your machine and nothing is sent anywhere. Optional cloud AI, sync, and connectors are separate and can be left off entirely for PHI workflows.
PHI stays on-device
Local-only mode keeps recordings, transcripts, and extracted text on your machine. No cloud, no third-party processing, no BAA to negotiate.
Faster documentation
Pull up what you saw and said during a visit. Draft reports and notes from real context instead of memory.
Open source and auditable
MIT-licensed core. Your IT and security teams can inspect exactly what it does before it's installed on clinical machines.
Deploy across the practice
Roll out to a team or hospital system with admin controls, MDM deployment, and per-device access policies.
How it works
Install on your clinical machine
screenpipe runs locally on macOS, Windows, or Linux. In local-only mode, your data never leaves the device.
Work your normal day
See patients, write reports, dictate notes. screenpipe captures screen and audio in the background.
Recall and document
Search what happened during a visit, generate summaries, and draft documentation grounded in what you actually saw and said.
Key benefits
Frequently asked questions
screenpipe is local-first: in local-only mode, recordings, transcripts, and extracted text stay on your device and are never sent to a third party, which removes the cloud-processing surface HIPAA is most concerned with. Compliance always depends on your full deployment - retention policy, access controls, device security, and a BAA wherever third-party processing is enabled. screenpipe provides the local-first foundation; your organization owns the overall compliance scope.
Not in local-only mode. Capture, OCR, and search all run on your machine. Cloud AI, sync, and connectors are optional features separate from core capture - leave them off and nothing is transmitted.
Yes. screenpipe supports team and enterprise deployment with admin controls, MDM/managed rollout, and per-device policies, so IT can standardize configuration across a practice or hospital system.
Yes, the core is MIT-licensed. Your security and IT teams can inspect the source before installing it on clinical machines - something closed-source consumer apps don't allow.
Cloud-first tools route data through servers you don't control, which means a BAA, a data-residency review, and a security audit for every vendor. With local-first capture, PHI stays on the device, so you avoid most of that overhead for day-to-day workflows.