> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/readme-1/tonic-deployment-types.md).

# Structural deployment types

## Self-hosted Tonic Structural instance

You can [deploy a self-hosted, on-premises instance of Tonic Structural](/app/admin/on-premise-deployment.md).

For a self-hosted instance, Structural provides administrator tools that allow you to [monitor Structural services](/app/admin/tonic-monitoring-logging/tonic-admin-service-list.md) and [manage Structural users](broken://pages/TJ113lVDxhMIaAzfk7WF).

You can [configure Structural environment settings](/app/admin/environment-variables-setting.md) to customize your instance.

On a self-hosted instance, based on your [license plan](/app/readme-1/tonic-license-plans.md), you have access to the full set of supported data connectors.

## Structural Cloud

Structural Cloud is our secure hosted environment. On Structural Cloud, Tonic.ai handles monitoring Structural services and updating Structural.

For [single sign-on (SSO)](/app/structural-user-access/single-sign-on.md), Structural Cloud only supports Okta.

Structural Cloud does not include:

* [Custom permission sets](/app/structural-user-access/permissions/permission-sets-about.md)
* [Environment setting configuration](/app/admin/environment-variables-setting.md), except for specific settings that can be set for a Cloud organization from the **Organization Settings** tab on **Structural Settings**. Other than that, Structural Cloud uses a single configuration.
* [Structural data encryption](/app/generation/generators-assign-config/generators-data-encryption-config.md)
* Access to the following data connectors:
  * [Amazon Redshift](/app/setting-up-your-database/amazon-redshift.md)
  * [Db2 for LUW](/app/setting-up-your-database/db2-luw.md)
  * [Spark SDK](/app/setting-up-your-database/spark-sdk.md)

Each Structural Cloud user belongs to a Structural Cloud organization, which is determined either by the user's email domain or by a workspace invitation. Structural Cloud users do not have any access to workspaces or users from other organizations.

Each free trial user is in a separate organization, along with any users that they invite to have access to a free trial workspace.

For information about Structural Cloud organizations, go to [Structural organizations](/app/structural-user-access/structural-organizations.md). 

The Account Admin permission set allows a Structural Cloud user to manage organization users and workspaces. For information about granting access to the Account Admin permission set, go to [Granting Account Admin access for a Structural Cloud organization](/app/structural-user-access/permissions/global-permissions/granting-account-admin-access-for-a-structural-cloud-organization.md).


---

# 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.tonic.ai/app/readme-1/tonic-deployment-types.md?ask=<question>&goal=<user_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.