# On Premises

**Overview**

On-prem infrastructure plays a critical role in enhancing safety for healthcare applications by ensuring that sensitive patient data remains within the provider’s secure environment. By eliminating reliance on external cloud services, on-prem deployments reduce potential exposure to third-party breaches and enable tighter access control. This localized, encrypted setup supports compliance with healthcare regulations and gives organizations full authority over data handling, retention, and audit-ability.

* **Data Residency & Compliance**
  * On-prem deployments ensure PHI and sensitive health data never leave the provider’s infrastructure, supporting strict compliance with HIPAA, PIPEDA, and region-specific regulations (e.g., KSA, UAE, Eastern Europe).
* **Isolated, Encrypted Model Hosting**
  * Self-hosted LLMs and inference systems run within provider-controlled environments, eliminating third-party cloud exposure and reducing attack surfaces.
  * Supports encrypted training and inference—including homomorphic encryption—for secure data processing even during computation.
* **Operational Control & Auditability**
  * Providers retain full control over data access, retention, and key management, with the ability to define deletion schedules or revoke access instantly.
  * All infrastructure is auditable and designed to meet healthcare-grade standards for system integrity, access logging, and redundancy.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sully.gitbook.io/sully.ai-docs/FEM1tMOJsSSszbLOgKLA/on-premises.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
