> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/deployment-and-licensing/saas-vs-enterprise/saas-deployment-explained.md).
# SaaS deployment explained
### What is SaaS?
The extension services are hosted and maintained by Infotopics, allowing customers to use Apps for Tableau without managing servers, upgrades, or infrastructure.
Data access follows Tableau’s security model. Extensions only receive data that Tableau allows, and no direct database connections are made by the extension itself.
***
### SaaS deployment architecture
### Key characteristics
* Fully managed by Infotopics
* No server installation required
* Automatic updates and maintenance
* Secure cloud environment
* Suitable for Tableau Cloud and Tableau Server
***
### Responsibilities
| Area | Responsibility |
| ---------------------- | -------------- |
| Hosting & uptime | Infotopics |
| Updates & patches | Infotopics |
| Platform security | Infotopics |
| Tableau permissions | Customer |
| Workbook configuration | Customer |
***
### Typical use cases
* Tableau Cloud deployments
* Proof-of-concept and production use
* Organisations without on-prem requirements
* Teams that want fast time-to-value
***
### Limitations to consider
* Less control over infrastructure
* Custom network or security configurations may be limited
If full control over hosting and configuration is required, **Enterprise deployment** may be a better fit.
***
---
# 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.infotopics.com/deployment-and-licensing/saas-vs-enterprise/saas-deployment-explained.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.
