> 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/admin/on-premise-deployment.md).

# Deploying and updating a self-hosted Structural instance

For a self-hosted instance of Tonic Structural, you install Structural in your own environment.

{% hint style="info" %}
The self-hosted version of Structural is only available to customers who purchased Structural or are undergoing a formal evaluation of Structural. For details, contact <sales@tonic.ai>. For information about the Structural free trial, go to the [Tonic.ai web site](https://www.tonic.ai/).
{% endhint %}

## Deployment checklist and requirements <a href="#checklist-requirements" id="checklist-requirements"></a>

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Deployment checklist</strong><br><br>Checklist of items to verify before you deploy Structural.</td><td><a href="/app/admin/on-premise-deployment/tonic-deployment-checklist.md">Deployment checklist</a></td></tr><tr><td><strong>Structural system requirements</strong><br><br>Overall system requirements for a Structural deployment.</td><td><a href="/app/admin/on-premise-deployment/tonic-system-requirements.md">System requirements</a></td></tr><tr><td><strong>Process guide to expand to additional teams</strong><br><br>Implementation process to expand Structural use to a other teams.</td><td><a href="/app/admin/on-premise-deployment/guide-to-expand-structural-to-other-teams.md">Guide to expand Structural to other teams</a></td></tr></tbody></table>

## Deploying and updating Structural <a href="#deploy-structural" id="deploy-structural"></a>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Deploy Structural on Docker</strong></td><td>How to use Docker Compose to deploy Structural on Docker.</td><td></td><td><a href="/app/admin/on-premise-deployment/deploying-with-docker-compose.md">Deploying with Docker Compose</a></td></tr><tr><td><strong>Deploy Structural on Kubernetes</strong></td><td>How to use Helm to deploy Structural on Kubernetes.</td><td></td><td><a href="/app/admin/on-premise-deployment/deploying-with-helm.md">Deploying on Kubernetes with Helm</a></td></tr><tr><td><strong>Enter and update your license key</strong></td><td>How to enter a new key or update an existing key.</td><td></td><td><a href="/app/admin/on-premise-deployment/license-key-enter-update.md">Entering and updating your license key</a></td></tr><tr><td><strong>Update Structural</strong></td><td>Download and deploy an updated version of Structural</td><td></td><td><a href="/app/admin/on-premise-deployment/updating-tonic.md">Updating Structural</a></td></tr></tbody></table>


---

# 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/admin/on-premise-deployment.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.