Contact
Twenty minutes, and it commits you to nothing. What we ask for is the column headers of one spreadsheet you already export — not your data, just the headers — and we can tell you what the count would look like.
Trialayer runs on two planes. Patient records are read in your browser and never reach us. Aggregate counts — and only those — travel to the shared plane, where a site sends a feasibility answer and a sponsor receives it. Sign-in for that plane is at app.trialayer.com; your site issues the account.
Hospitals, clinics, dedicated sites and academic teams.
Feasibility and site selection teams.
In your browser: patient records, record linkage and pseudonymization. The spreadsheet is read from your disk and the identifiers never leave the tab — open the Network panel and watch. Sign-in gates the shared plane, not the reading: we cannot see or reset that password, and we do not hold the data behind it either.
On the shared plane: counts, their period, their methodology and a SHA-256 fingerprint. No subject codes, no rows, no individual dates. The site reads the exact payload before it is sent, and the sponsor can verify the fingerprint on arrival.
That split is not a limitation we work around. It is the reason a site can use this at all — and doing the first half in the browser is why there is no IT, security or procurement queue in front of it.