Cloud
One region. Three artifacts. One connection out.
Pensieve ships as three deployables. The managed deployment runs on Google Cloud in region asia-south1 (India), with the backend co-located with the database and one binary inside your building. This page states what runs where, who holds the infrastructure in each arrangement, and what we require of yours.
A hospital buys one product, Pensieve, and runs it. The split below is how the software is built and where each part lives. Nothing here is a menu.
What is deployed
The three deployables
- Pensieve backendThe backend: TypeScript on a Hono HTTP server, designed to run on Google Cloud Run in the asia-south1 region, co-located with the database. It is the only path to the data.
- pensieveThe React web app staff work in, the Chamber. Served over a content delivery network, behind a global HTTPS load balancer and a web application firewall.
- orophinThe bridge: one binary on a Windows PC or Linux server inside the hospital, holding a single outbound mutually authenticated connection and exposing no inbound listener.
These are engineering artifacts. None of them carries a separate name on an invoice. Each one is described at the three deployables, and the bridge in full at orophin.
Where it runs
The line between our infrastructure and yours
Who holds the keys, and who holds the record
Three arrangements. The question a CIO is actually asking is not which cloud we use. It is who can reach the record, and by what mechanism. Here is that answer for each place Pensieve can sit.
| Arrangement | Infrastructure held by | Record held in | What Pensieve can reach |
|---|---|---|---|
| Pensieve-managed cloud | Pensieve, on Google Cloud in region asia-south1 (India). | asia-south1, co-located with the database. | We operate the infrastructure. Inside the product, every read and write passes the authorization check and is audited in the same transaction as the change, ours included. |
| Your cloud tenancy | The institution. Your project, your billing, your identity and access management. | Wherever your tenancy is provisioned. It stays inside yours. | Exactly what your access management grants, and nothing that it does not. |
| Inside the hospital | The institution, on hardware in your building. | Your building. | The bridge reaches out to us. Nothing of ours reaches in. |
Where Pensieve runs
The managed arrangement runs on Google Cloud in region asia-south1 (India), co-located with the database, and the hospital-facing edge is the bridge. The infrastructure behind it is set out at data residency.
The other two arrangements are mechanically ordinary
The backend is a container image, the staff web app is static files, and the bridge is unchanged wherever the backend sits. Which arrangement a hospital runs in, and on what terms, is agreed in its contract.
Residency and sovereignty
For an Indian hospital reasoning about the Digital Personal Data Protection Act, the answer to “where does our patient data live” has to name a region. Ours is Google Cloud asia-south1, in India, co-located with the database.
Residency is the smaller half
The larger half is whether the institution can prove, afterwards, on what basis each access happened. Consent in Pensieve is a modelled data object the authorization system reads on every read and write, withdrawal is a first-class action on that same object, and every grant and withdrawal is audited inside the transaction that made it. The full mapping from obligation to mechanism is at DPDPA; the infrastructure is at data residency.
We hold no data-protection certification, because there is no such certificate to hold. What we describe is the mechanism.
What we require of your environment
Prerequisites, stated as a specification, so your infrastructure team can price it before the first call. Everything below is what the software actually needs. Nothing below is a preference.
| Requirement | Specification |
|---|---|
| On-premises host | One Windows PC or one Linux server inside the hospital network, with line of sight to the systems the bridge will read. One agent per hospital carries many connections. |
| Outbound network | One outbound, mutually authenticated connection from that host to the Pensieve backend. No inbound firewall rule, no listener on your network, nothing on your side published to the internet. Your network team reviews an egress rule and nothing else. |
| Source systems | Each system reachable from the bridge host on the protocol it already speaks: MLLP / HL7 v2, ASTM, CSV drops, database polling, or DICOM. Nothing is rewritten to accommodate us. |
| Workstations | A current browser. The staff web app is a cloud application, and a workstation without connectivity cannot open it. Only the bridge carries on through an outage, as the next row describes. |
| Interruption | Machine traffic never needs the link to be up. The bridge holds a durable on-disk outbox and drains it in order when the connection returns. |
Sizing the bridge host
The bridge runs on a Windows PC or a Linux server on the hospital network, given to the bridge alone and never a machine a clinician works at. Its processor, memory, disk and bandwidth are sized for each site at deployment, from the systems it connects and the volume they send.
Refusals
What we do not do with the record
- No secondary use of the recordWe process personal data only on the documented instructions of the Data Fiduciary, except where the law requires otherwise. The record is worked on for the purpose it was collected under, and for nothing else we find interesting.
- No training on your dataA hospital’s record is never a corpus. It is never read into a model, an evaluation set, or a benchmark, and no derived artifact of it leaves the deployment.
- No export to a third partyThe record is not sold, brokered, or passed to a partner. The providers that process data to keep the platform running are listed by name and purpose, and that list is the whole of it.
- No inbound access to your networkThe bridge opens one connection outward and exposes no inbound listener. We do not hold a route into your network, so there is none to misuse or to lose.
Where each of the four is written down
None of the four above is a promise we are asking you to take on trust. Processing on documented instructions only is a clause in the Data Processing Addendum. The third parties that touch data at all are named, with their purpose and region, at subprocessors, and that page is updated whenever the list changes. The mechanisms that enforce the rest, the authorization check on every read, the audit written in the same transaction as the change, are at security.