> 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/share-vs-enterprise/share-deployment-explained.md).

# Share deployment explained

### What is Share?

**Share** is the Infotopics SaaS deployment model.

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.

***

### Share deployment architecture

<figure><img src="/files/4kYQN6XOIK3XUGJb0aVo" alt=""><figcaption></figcaption></figure>

### 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 dynamically by asking a question.

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

```
GET https://docs.infotopics.com/deployment-and-licensing/share-vs-enterprise/share-deployment-explained.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.