> 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/api-references/client-and-daemon-compatibility.md).

# Client and daemon compatibility

Match Go or Rust client versions with the Zama SDK daemon image.

{% hint style="warning" %}
The daemon and its Go and Rust clients are experimental. The wire protocol can change between minor versions, so upgrade the daemon image and the clients together.
{% endhint %}

Run the daemon image and your Go or Rust client at exactly the same version. Upgrade the image and clients together; matching only the major and minor versions is insufficient.

| Artifact     | Location                                                  |
| ------------ | --------------------------------------------------------- |
| Daemon image | `ghcr.io/zama-ai/sdk-daemon` on GitHub Container Registry |
| Rust crate   | `zama_sdk` on crates.io                                   |
| Go module    | `github.com/zama-ai/sdk/clients/go/v3`                    |

Each release publishes the image for `linux/amd64` and `linux/arm64`, tagged with its exact version and with a moving channel tag: `latest`, `beta`, or `alpha`.

The quickstarts and the deployment page set one `ZAMA_SDK_VERSION` variable for the image tag and the client version, and each release updates it to that release.

For deployments, record the selected client version and pin the daemon image to the digest of its matching release. Do not rely on a moving image tag when restarting an existing deployment. Each release signs the image and attaches build provenance and an SBOM; [Deploy in production](https://docs.zama.org/protocol/sdk/go-and-rust-guide/operations/run-in-production.md#verify-and-pin-the-image) shows how to verify them and obtain the digest. Retain the Go module files or your Rust application's lockfile to reproduce the selected dependencies.

The wire protocol is named `v1beta1`. This identifier does not select an SDK release channel or replace the exact-version pairing rule.

Start with the [Go quick start](https://docs.zama.org/protocol/sdk/getting-started/go-quick-start.md) or [Rust quick start](https://docs.zama.org/protocol/sdk/getting-started/rust-quick-start.md). Read [Upgrade the daemon](https://docs.zama.org/protocol/sdk/go-and-rust-guide/operations/upgrade-and-recover.md) before changing an existing deployment.


---

# 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/api-references/client-and-daemon-compatibility.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.
