Skip to content

Interoperability

Nothing on your side is exposed to the internet.

The most common objection to cloud hospital software is that it will want to open ports into your network. Pensieve’s answer is that it never asks you to.

  • Direction: Outbound only
  • Transport: Mutually authenticated (mTLS)
  • Inbound rules: None

The concern, and the answer

A hospital network team’s job is to keep the internal network unreachable from outside. Most cloud vendors ask them to make an exception: an inbound rule, a listener, a port. That new opening is exactly the attack surface a security review worries about.

Pensieve does not ask for one. The orophin bridge reaches out to the Pensieve backend; nothing reaches in.

One arrow, and it points out

DIAGRAMHospital firewall with a single outbound arrow from orophin to the Pensieve backend; all inbound arrows blockedDIAGRAM, 16/9
The hospital firewall permits a single outbound, mutually authenticated connection from orophin. Inbound connections stay blocked.
  • Outbound-onlyorophin initiates a single connection out to the Pensieve backend. No ports are opened into the hospital network, and there is no inbound listener to expose.
  • Mutually authenticatedThe connection is mTLS: both ends present and verify a certificate, so neither the agent nor the backend talks to an impostor.
  • What your network team approvesA single outbound connection, the same shape as any other cloud client. It reviews like ordinary egress, and no firewall rule is opened inward.
  • Why it mattersThe attack surface a cloud vendor usually adds, an inbound listener sitting on your network, is absent here.
You’ll want to open ports into my network.
No. orophin opens one outbound, mutually authenticated connection to the Pensieve backend and nothing listens for inbound traffic. Your network team approves egress.

Powerful. Responsible. Pensieve.

Get started