Use the public iLab Security & Compliance page to answer questions about how iLab protects laboratory and patient data, where it is hosted, and what compliance commitments apply. This content is published and maintained on the website; the summary below reflects the currently published page.
What iLab publishes about security
Hosting: iLab runs on AWS (Amazon Web Services) with auto-scaling cloud infrastructure, rather than a single fixed server.
Encryption: Data moving to and from iLab, and data stored in its databases, is encrypted using industry-standard protocols, both in transit and at rest.
Audit logs: Meaningful actions are logged so activity can be traced by what happened, when, and by whom.
Role-based access control: Employees only see and do what their assigned role and permissions allow, down to individual actions.
Auto-scaling infrastructure: Infrastructure scales automatically with demand instead of relying on a single fixed server.
Compliance commitments
The published page states that iLab is built to meet HIPAA and GDPR requirements: encryption, audit trails, and role-based access are described as core to every layer of the platform. iLab states it signs Business Associate Agreements (BAAs) and data-processing agreements (DPAs) directly with labs that need them, and describes this as the same standard offered to every lab on the platform, not only Enterprise plans.
These are the laboratory's own commercial and compliance commitments as currently published; they are not a third-party certification claim. A laboratory that needs an executed BAA or DPA, or needs to confirm compliance scope for its own regulatory review, should request it directly from iLab rather than relying on this summary alone.
Enterprise and custom hosting
Laboratories running multi-location operations, or that need infrastructure matching their own compliance program, can request a dedicated or custom hosting arrangement. The published page directs this request through Talk to Our Team, which opens the current contact/booking path rather than a self-service setting. Availability, scope, and pricing for custom hosting are not published and must be confirmed directly with iLab.
Frequently asked questions
Is iLab HIPAA and GDPR compliant?
Yes, per the currently published page: encryption, audit trails, and role-based access are described as built into every layer of iLab, and iLab states it signs BAAs and data-processing agreements directly with labs that need them, as the same standard for every lab on the platform.
What cloud platform does iLab run on?
AWS. The published page describes auto-scaling infrastructure built to handle production demand rather than a single fixed server.
Can a laboratory get a custom or dedicated hosting setup?
Yes. iLab states it works with enterprise labs directly on dedicated and custom hosting arrangements tailored to their infrastructure and compliance needs. Use Talk to Our Team on the Security & Compliance page to start that request.
Where do I find the current, exact wording of these claims?
Use the public iLab Security & Compliance page for the current wording. Published compliance and hosting claims can change; treat this article as an orientation summary, not a substitute for the live page or a signed agreement.
Related guides
Compare iLab plans, pricing, trials, and add-ons — compare published plan limits and add-ons before registering.
Create an iLab account for your laboratory — complete registration and enter the new workspace.
Need help?
Use the website contact path, the Talk to Our Team option on the Security & Compliance page, or email [email protected] to request a BAA, data-processing agreement, or custom hosting discussion. Never send a password, verification code, payment credential, or access token by email.