> 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/getting-started.md).

# Getting started

Kangal separates management from runtime traffic:

* The **control plane** stores gateway configuration, policies, identities, integration settings, audit history, and desired data-plane state.
* The **data plane** matches incoming requests, applies plugins, selects an upstream target, proxies traffic, and reports telemetry.

The primary gateway entities follow a familiar model:

| Entity   | Purpose                                                                       |
| -------- | ----------------------------------------------------------------------------- |
| Gateway  | Isolates a control-plane configuration and runtime boundary.                  |
| Service  | Describes the upstream application behavior.                                  |
| Route    | Matches requests by host, path, method, header, query, or SNI.                |
| Upstream | Groups backend targets and load-balancing behavior.                           |
| Target   | Identifies a concrete backend endpoint and health state.                      |
| Consumer | Represents an API client and its credentials.                                 |
| Plugin   | Applies authentication, traffic, transformation, observability, or AI policy. |

## First operational flow

1. Create or select a gateway.
2. Add a service and route.
3. Add an upstream and at least one target when load balancing is required.
4. Attach a policy such as API key authentication or rate limiting.
5. Send a request through the proxy and inspect traffic telemetry.
6. Create a configuration snapshot before larger changes.

## Recommended learning path

1. Complete the [Gateway quickstart](/gateway/quickstart.md).
2. Learn how [services and routes](/gateway/services-routes.md) match traffic.
3. Add [upstreams and targets](/gateway/upstreams-targets.md) for resilience.
4. Apply an authentication or traffic [plugin](/plugins/plugins.md).
5. Register a [consumer and credential](/consumers/consumers.md).
6. Inspect [metrics, logs, SLOs, and audits](/observability/observability.md).

After the gateway path works, connect engineering systems through the [integration catalog](/integrations/integrations.md) or publish an API product through the [Developer Portal](/developer-portal/developer-portal.md).


---

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