> For the complete documentation index, see [llms.txt](https://developer.sahamati.org.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.sahamati.org.in/sahamatinet-agent-sna/integration-guide/deploying-sna.md).

# Deploying SNA

SNA runs as a standalone agent inside your own infrastructure. You can deploy it in either of two ways:

<table><thead><tr><th width="131.3333740234375">Option</th><th>Use when</th></tr></thead><tbody><tr><td>Helm chart</td><td>Your AA services run on Kubernetes</td></tr><tr><td>Docker</td><td>Your AA services run on containers without Kubernetes</td></tr></tbody></table>

Both options run the same SNA image and behave identically. Choose the one that matches your environment.

> 📌 Always deploy the latest version of SNA.

### GitHub Repository

The SNA downloadables repository contains the Helm chart and the snalib distribution:

<https://github.com/Sahamati/sahamatinet-agent-downloadables>

### Helm Chart Deployment Steps

1. Download the contents from the repository: <https://github.com/Sahamati/sahamatinet-agent-downloadables.git>
2. Refer to the README.md file in the repository root for an overview.
3. Follow the instructions in the SETUP.md file for deployment of the container. This includes configuring the required settings and running the Helm charts.
4. After installation, test the ping API to confirm the SNA container is up and running.

### Upgrading SNA

When Sahamati releases a new version of SNA (e.g., to update schema definitions or metric logic), the upgrade process is straightforward:

1. Download the new Helm chart version from the GitHub repository.
2. Run a Helm upgrade command:


---

# 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://developer.sahamati.org.in/sahamatinet-agent-sna/integration-guide/deploying-sna.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.