> For the complete documentation index, see [llms.txt](https://docs.zenml.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenml.io/kitaru/getting-started/deploy.md).

# Deploy Kitaru

A Kitaru deployment is deliberately small:

* **The server** is one FastAPI service on Postgres. It stores agents, sessions, cohorts, evaluators, experiments, and replays, and serves the REST API the SDK, CLI, and workers speak. It executes no user code.
* **Workers** are processes you run wherever your agents' code and credentials live. All execution (replays, imports, evaluations) happens there. See [Workers in production](/kitaru/running-in-production/workers.md).
* **Postgres** is the only stateful dependency. Your database, your backups.

This shape is the data-privacy story: traces are stored on your server, parsed and replayed on your workers. Nothing needs to leave your systems.

## Setting up

1. [Docker](/kitaru/getting-started/deploy/docker.md): Compose for a single host, or the published server image against your managed Postgres. Start here. On Kubernetes, use the [Helm chart](/kitaru/getting-started/deploy/helm.md).
2. Create [accounts and API keys](/kitaru/running-in-production/authentication.md) for your team and your CI (Python client today; CLI verbs are on the way).
3. Start [workers](/kitaru/running-in-production/workers.md) in each environment agents run in.
4. Store provider credentials the server should manage as [secrets](/kitaru/running-in-production/secrets.md), and set client defaults via [configuration](/kitaru/get-help/configuration.md).

Steps 2 to 4 are covered in **Running in production**, alongside worker sizing, authentication, secrets and configuration. Come back to them once a server is up. For a first look, `kitaru login --local` in [Installation](/kitaru/getting-started/installation.md) is faster than any of this.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zenml.io/kitaru/getting-started/deploy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.