> 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/running-in-production.md).

# Running in production

- [Workers in production](https://docs.zenml.io/kitaru/running-in-production/workers.md): Deploying workers as long-running pools, scoped fleets, and one-shot CI workers, all configured through environment variables.
- [Authentication & API keys](https://docs.zenml.io/kitaru/running-in-production/authentication.md): Accounts, logins, and KITKEY\_ API keys, and how people and processes authenticate to your Kitaru server.
- [Secrets](https://docs.zenml.io/kitaru/running-in-production/secrets.md): Store credentials once, encrypted at rest, and inject them into replayed agents through agent version run specs.


---

# 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.zenml.io/kitaru/running-in-production.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.