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

# Deploy & Operate

- [Self-hosting](https://docs.algenta.ai/deploy-and-operate/self-hosting.md): Deploy and operate the Algenta engine on your own infrastructure — configure it, run it, and verify a self-hosted instance is healthy.
- [Configuration reference](https://docs.algenta.ai/deploy-and-operate/configuration.md): Every Algenta configuration environment variable in one place, with its default and any aliases — complete and current.
- [Monitoring & observability](https://docs.algenta.ai/deploy-and-operate/monitoring.md): Monitor a self-hosted Algenta deployment — scrape the protected /metrics endpoint, read the engine health signals, tail the structlog JSON logs, all inside your own network.
- [Encryption at rest (BYOK)](https://docs.algenta.ai/deploy-and-operate/byok-kms.md): Encrypt Algenta secrets at rest with your own AES-256-GCM key supplied through ALGENTA\_CONFIG\_ENCRYPTION\_KEY.
- [Device key store](https://docs.algenta.ai/deploy-and-operate/device-key-store.md): Choose where Algenta stores the per-device private key — Apple Secure Enclave, a Linux TPM, the OS keyring, or an encrypted file — and confirm the runtime is healthy with runtime doctor.
- [Audit & tighten egress](https://docs.algenta.ai/deploy-and-operate/privacy-egress.md): Read the engine's live egress policy, tighten it with deployment-mode settings, generate a 24-hour privacy report, and audit the redacted egress decision log.
- [Teams & roles (RBAC)](https://docs.algenta.ai/deploy-and-operate/teams-rbac.md): Invite team members and set roles, understand the owner/admin/member/viewer permission matrix, and read the org audit log and its content-hashed artifacts.
- [Deployments & nodes](https://docs.algenta.ai/deploy-and-operate/deployments-and-nodes.md): Provision an isolated cloud deployment across AWS, Azure, or GCP, track its status and monthly cost, and register self-hosted worker nodes that heartbeat into the engine.
- [Licensing & editions](https://docs.algenta.ai/deploy-and-operate/licensing.md): How Algenta licensing works for self-hosted and air-gapped use — what a license grants, how to install and verify it offline, the editions, and the open-core terms.
- [Usage & limits](https://docs.algenta.ai/deploy-and-operate/billing.md): Inspect unlimited execution policy and local governance records. Algenta is licensed per device, never per decision.


---

# 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.algenta.ai/deploy-and-operate.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.