> For the complete documentation index, see [llms.txt](https://docs.appsurify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appsurify.com/security-and-compliance/saas-or-on-prem.md).
# SaaS or On-Prem
Learn whether Appsurify should be working as a SaaS or an On-Prem solution for your company
## SaaS and On-Premise Available
Appsurify offers two installations options:
### **SaaS - Recommended Option**
* Securely Hosted in Microsoft Azure and follows all Security & Compliance Best Practices.
* No Direct Connection to Git-Required.
* Push-only **read** data of Commit Metadata. (No write access required).
* No access to files or folders, only code snippets.
* Data is encrypted in transit & at rest.
* Please visit our [Trust Cloud](https://appsurify-trust-cloud.trustshare.com/home) for documentation, etc.
### **On-Premise**
* Fully secure, no outside connection. Completely behind client Firewall.
* No data shared externally.
* Installed via Docker Image on internal VM.
* Available via Microsoft Commercial Marketplace.
* Microsoft Offering [Here](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/appsurifyinc1606933045773.appsurify3001).
* AWS Offering: Coming Soon!
For On-Premise deployments help, please reach out to [Appsurify Customer Success](https://appsurify.com/qa-automation-tool-pricing/).
###
###
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.appsurify.com/security-and-compliance/saas-or-on-prem.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.