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

# Pro Features

Add coordination and visibility without replacing the concepts you already know.

JoobQ Pro builds on the Core runtime. The upgrade adds workflow orchestration, metrics and alerting, plus explicit coordination services. It does not make persistence configuration, graceful shutdown, or idempotency somebody else's responsibility.

| Capability                                                             | Guide                                  | Important boundary                                                |
| ---------------------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------- |
| Typed workflows, dependencies, signals, timers, children, compensation | [Workflow DSL](/pro/workflow-dsl.md)   | Available since Pro v0.2.2; authoring preview; effects can repeat |
| Durable batches, uniqueness, and distributed rate limits               | [Coordination](/pro/coordination.md)   | Durable services require an explicit Delivery runtime             |
| Metrics, percentiles, alerts, and structured logs                      | [Observability](/pro/observability.md) | Configure collection and external export deliberately             |
| Queue, workflow, and DLQ inspection                                    | [CLI management](/pro/management.md)   | CLI inspection is shared with Core; Pro adds workflow data        |

Start with [adding Pro](/readme/adding-pro.md), then run [one activity](/quick-start/first-workflow.md). Each guide identifies the API family it uses so you can keep ordinary jobs running while adopting one Pro capability at a time.

\[Screenshot: The JoobQ terminal workflow view showing a process-order run with dependent steps, current attempts, a waiting signal, and a separate queue/worker pane.]


---

# 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.joobq.io/pro.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.