On your servers
The whole platform runs inside your environment — your data centre or your private cloud.
BioStudioAI runs on your servers. The AI gets a description of your data, never your measurements. Every security, privacy and compliance claim points to a test that ran.
BioStudioAI uses the intelligence of Claude, ChatGPT and Gemini — without your measurements leaving your lab. Four steps, left to right.
Files and measurements stay on your servers, locked.
Claude, ChatGPT or Gemini get a description and your question — not your numbers.
Which test, which plot. A plan — never a result.
Every number is calculated from your data. Numbers typed by the AI are rejected.
Sending more than a description is a setting your admins control.
Switch the setting and watch what crosses the boundary. In every mode the engines compute every number on your servers, and notebook content never goes to an AI model.
Your data never leaves. We can't see it.
For your IT, security and quality teams: where BioStudioAI runs, what the AI can and cannot see, and what gets recorded.
The whole platform runs inside your environment — your data centre or your private cloud.
Data is encrypted. BioStudioAI, the company, has no access to your files or results.
Models get a description of your data, not your measurements. Admins choose which models each team may use — or switch AI off.
Every AI call is kept in an encrypted log. Every analysis has version history; every exclusion has its rule and value.
Per-project sharing and roles. People see what their project allows — nothing more.
Export to Excel, CSV, PDF, PowerPoint and SVG at any time. If you stop, your data never left your servers.
The whole platform moves into your environment, encrypted. BioStudioAI, the company, has no access to your files or results.
On-premises, when policy requires it. Your network, your backups, your rules.
In your own cloud account, under your own access policies.
Your data stays yours. We don't train on it, and we can't see it. Export everything, any time, in standard formats.
Our Trust Center publishes the test suites behind each security, privacy, accuracy and compliance claim — with dates, environments, commands to reproduce them and checksums on every document.
Each audit entry stores the SHA-256 of its content and of the entry before it. Edit any past entry and every link after it stops matching. Example entries; the hashes are computed in your browser right now — the same mechanism the notebook's audit trail uses.
In BioStudioAI the database also refuses UPDATE and DELETE on the trail, and the chain is re-verified every night. If the trail is unavailable, the action is refused.
Part 11 · Annex 11 evidence →Short answers to what security reviews ask first. The details, tests and dates are in the Trust Center.
AES-256-GCM encryption; codebooks for coded identifiers are stored encrypted, scoped and owner-controlled.
Administrators use two-factor codes (tested against RFC 6238 vectors, with replay protection and lock-out). Signatures need a password or passkey confirmation.
Row-level security everywhere and per-project roles: people see what their project allows — nothing more. Every notebook route checks access.
No. It is append-only and SHA-256 hash-chained; the database refuses UPDATE and DELETE, and it is re-verified every night. If it is unavailable, the action is refused.
By default a description of your data and your question — not your measurements. Identifiers are coded before anything leaves; notebook content never goes to an AI model.
Yes. Admins choose which models each team may use, or switch AI off; the engines keep working.
Not SOC 2 or ISO 27001 yet; HIPAA not assessed. The Trust Center lists the controls and the tests behind each claim.
Yes: architecture overview, data-flow diagram, our answers to the usual questionnaire, and the 41-page Trust Pack.
Architecture overview, data-flow diagram, our answers to the usual questionnaire and the Trust Pack.
We'll reply to your work email, usually within minutes.