> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aseeflow.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Quarkus Integration

The ASEE Flow Engine can be used in a Quarkus application by using the provided Quarkus Extension. Quarkus Extensions add
behavior to your Quarkus application by adding dependencies to the classpath.

The ASEE Flow Engine Quarkus Extension will pre-configure the ASEE Flow process engine, so it can be easily used in a
Quarkus application.

If you are not familiar with [Quarkus](https://quarkus.io/), have a look at the [getting started](https://quarkus.io/get-started/) guide.

To enable ASEE Flow Engine autoconfiguration, add the following dependency to your `pom.xml`:

```xml theme={null}
<dependency>
  <groupId>org.aseeflow.bpm.quarkus</groupId>
  <artifactId>aseeflow-bpm-quarkus-engine</artifactId>
  <version>1.0.0</version>
</dependency>
```

This will add the ASEE Flow engine v.7.23.0 to your dependencies.

## Supported deployment scenarios

ASEE Flow supports the following deployment scenario:

* executable JAR with one embedded process engine.

There are other possible variations that might also work, but are not tested by ASEE Flow at the moment.

## In this section

* [**Quarkus Version Compatibility**](/user-guide/quarkus-integration/version-compatibility) — Supported Quarkus versions.
* [**Engine CDI Integration**](/user-guide/quarkus-integration/cdi-integration) — Use the engine with Quarkus CDI.
* [**Quarkus Extension Configuration**](/user-guide/quarkus-integration/configuration) — Configure the Quarkus extension.
* [**Resource Deployments**](/user-guide/quarkus-integration/deployments) — Deploy process resources.