> For the complete documentation index, see [llms.txt](https://docs.zama.org/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/protocol/sdk/go-and-rust-guide/operations.md).

# Daemon deployment

Run, monitor, and upgrade the Zama SDK daemon in production for Go and Rust integrations.

The daemon is a required part of a Go or Rust integration. Run it on your own infrastructure, keep it healthy, and upgrade it safely. Upgrade the daemon image and the clients together, and check [client and daemon compatibility](https://docs.zama.org/protocol/sdk/api-references/client-and-daemon-compatibility.md) before you do.

## Where to go next

🟨 Go to [**Deploy in production**](https://docs.zama.org/protocol/sdk/go-and-rust-guide/operations/run-in-production.md) to run the daemon on your infrastructure.

🟨 Go to [**Monitor and troubleshoot**](https://docs.zama.org/protocol/sdk/go-and-rust-guide/operations/monitor-and-troubleshoot.md) a running daemon.

🟨 Go to [**Upgrade the daemon**](https://docs.zama.org/protocol/sdk/go-and-rust-guide/operations/upgrade-and-recover.md) to replace the daemon and clients together, or roll back.


---

# 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.zama.org/protocol/sdk/go-and-rust-guide/operations.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.
