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

# Kangal documentation

Kangal is a control plane for securing, routing, observing, and operating API, AI, and integration traffic from one product surface. These guides cover the complete path from a first gateway to production operations.

## Choose a path

| Goal                                    | Start here                                                                 |
| --------------------------------------- | -------------------------------------------------------------------------- |
| Publish a real API                      | [Gateway quickstart](/gateway/quickstart.md)                               |
| Understand control plane and data plane | [Architecture](/concepts/architecture.md)                                  |
| Protect an API with policies            | [Plugins](/plugins/plugins.md)                                             |
| Identify clients and issue credentials  | [Consumers](/consumers/consumers.md)                                       |
| Route LLM traffic                       | [AI Gateway](/ai-gateway/ai-gateway.md)                                    |
| Publish an API product                  | [Developer Portal](/developer-portal/developer-portal.md)                  |
| Manage teams and access                 | [Organizations and access](/organizations-and-access/organizations.md)     |
| Automate configuration                  | [Configuration and GitOps](/configuration-and-automation/configuration.md) |
| Connect engineering systems             | [Integrations](/integrations/integrations.md)                              |
| Operate Kangal in production            | [Production operations](/production-operations/operations.md)              |

## Security baseline

* Store credentials only in secret fields or an approved secret manager.
* Use tenant-scoped, least-privilege identities for users and integrations.
* Verify TLS, egress policy, audit history, and configuration snapshots before a production rollout.
* Never place an Admin API token inside a consumer application or generated SDK.

Continue with [Getting started](/getting-started.md) for the product model and the shortest end-to-end workflow.


---

# 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.kangal.dev/readme.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.