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

# Deployment guidelines v5.9.7

> Component versions, configuration, and deployment notes for FlowX.AI 5.9.7 (5.9.x LTS maintenance release).

> [!NOTE]
>
> After upgrading to a new platform version, always ensure that your installed component versions match the versions specified in the release notes. To verify this, navigate to **FlowX.AI Designer → Platform Status**.

## Upgrade overview

FlowX.AI 5.9.7 is a maintenance release for the 5.9.x LTS line. The upgrade from 5.9.6 adds no Kafka topics and no database migrations. If you scrape the services with the Prometheus Operator, one Helm value for relabeling is renamed. Review [Configuration changes](#configuration-changes) and the [5.9.7 upgrade notes](https://docs.flowx.ai/release-notes/v5.x/v5.9.7-november-2026/v5.9.7-november-2026.md#upgrade-notes) before you deploy.

> [card] Upgrade Path
>
> **5.9.6 → 5.9.7**: Direct upgrade. No manual data migration is required. Run it as a rolling upgrade without downtime, see [Upgrade within an LTS family](https://docs.flowx.ai/5.9/setup-guides/upgrade-within-lts-family.md).
>
> **5.9.7 → 6.0.0**: See [Migrating from v5.9.x to v6.0.0](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/migrating-from-v5.9-to-v6.0/migration-overview.md).
>
> Self-hosted customers still on the 5.1.x LTS upgrade directly to the 5.9.x line. See [Migrating from 5.1 LTS](https://docs.flowx.ai/5.9/migrating-from-5.1-lts/overview.md).

> [!NOTE]
>
> **Upgrading from 5.9.5 or earlier directly?** Review the [5.9.6 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.6-october-2026/deployment-guidelines-v5.9.6.md) first, then the earlier pages they point to.

## Component versions

### Core components

| Component | 5.9.7 | 5.9.6 | 5.9.0 | 5.8.0 | 5.1.14 (LTS) |
| - | - | - | - | - | - |
| **process-engine** | 10.174.29 | 10.174.17 | 10.135.0 | 10.106.0 | 9.76.12 |
| **admin** | 10.152.25 | 10.152.14 | 10.116.0 | 10.93.0 | 9.76.10 |
| **designer** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **cms-core** | 10.113.24 | 10.113.13 | 10.86.0 | 10.67.0 | 9.47.8 |
| **scheduler-core** | 10.94.21 | 10.94.11 | 10.70.0 | 10.53.0 | 9.36.7 |
| **events-gateway** | 10.101.12 | 10.101.1 | 10.72.0 | 10.55.0 | 9.37.7 |
| **notification-plugin** | 10.111.12 | 10.111.1 | 10.83.0 | 10.64.0 | 9.40.7 |
| **document-plugin** | 10.124.24 | 10.124.13 | 10.94.0 | 10.75.0 | 9.45.7 |
| **task-management-plugin** | 10.112.23 | 10.112.12 | 10.84.0 | 10.66.0 | 9.44.9 |
| **reporting-plugin**\* | 10.1.10 | 10.1.8 | 0.2.6 | 0.2.6 | 0.2.8 |
| **data-search** | 10.92.21 | 10.92.11 | 10.69.0 | 10.52.0 | 9.33.7 |
| **audit-core** | 10.102.22 | 10.102.11 | 10.79.0 | 10.63.0 | 9.41.8 |
| **advancing-controller** | 10.98.22 | 10.98.12 | 10.73.0 | 10.55.0 | 9.36.8 |
| **integration-designer** | 10.201.16 | 10.201.2 | 10.162.0 | 10.128.0 | 9.60.9 |
| **application-manager** | 10.159.18 | 10.159.3 | 10.123.0 | 10.97.0 | 9.83.10 |
| **runtime-manager** | 10.159.18 | 10.159.3 | 10.123.0 | 10.97.0 | 9.83.10 |
| **data-sync** | 10.107.23 | 10.107.13 | 10.81.0 | 10.58.0 | 9.34.6 |
| **authorization-system** | 10.122.24 | 10.122.13 | 10.96.1 | 10.77.0 | 9.44.8 |
| **nosql-db-runner** | 10.101.23 | 10.101.13 | 10.75.0 | 10.56.0 | 9.32.7 |
| **email-gateway** | 10.102.13 | 10.102.1 | 10.74.0 | 10.56.0 | - |
| **organization-manager** | 10.98.22 | 10.98.12 | 10.71.0 | 10.53.0 | - |
| **webhook-gateway** | 10.69.24 | 10.69.12 | 10.44.0 | 10.25.0 | - |
| **file-gateway** | 10.33.25 | 10.33.14 | 10.8.0 | - | - |
| **license** | 10.87.22 | 10.87.12 | 10.63.0 | 10.46.0 | - |

\* The reporting plugin is an optional add-on and is versioned independently of the platform, so its numbering does not follow the other components. It moved from the `0.2.x` scheme to `10.x` after 5.9.0. Pin the version listed for your release.

### Embedded components

* **SpiceDB** 1.56.2, deployed and upgraded by the **SpiceDB operator** 1.27.1.
* **Qdrant** (vector database): bundled in the `flowx-ai` Helm chart; its version is managed by the chart and not pinned here. See the [Qdrant setup guide](https://docs.flowx.ai/5.9/setup-guides/qdrant.md) for deployment and configuration.

### Renderers

| Component | 5.9.7 | 5.9.6 | 5.9.0 | 5.8.0 | 5.1.14 (LTS) |
| - | - | - | - | - | - |
| **@flowx/angular-sdk** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/angular-theme** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/angular-ui-toolkit** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/react-sdk** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/react-theme** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/react-ui-toolkit** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/react-native-sdk** | 10.285.20 | 10.285.4 | 10.230.2 | - | - |
| **@flowx/react-native-theme** | 10.285.20 | 10.285.4 | 10.230.2 | - | - |
| **@flowx/react-native-ui-toolkit** | 10.285.20 | 10.285.4 | 10.230.2 | - | - |
| **@flowx/core-sdk** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **@flowx/core-theme** | 10.285.20 | 10.285.4 | 10.230.2 | 10.181.0 | 9.165.4 |
| **solution-portal** | 10.285.20 | 10.285.4 | 10.230.2 | - | - |
| **iOS renderer** | 10.9.3 | 10.9.2 | 10.4.1 | 10.3.0 | 9.0.38 |
| **Android renderer** | 10.10.2 | 10.10.2 | 10.5.0 | 10.3.0 | 9.0.48 |

### AI components

FlowX.AI groups AI services into four tiers by deployment role. **AI Base** components are the foundation; **AI Runtime** and **AI Dev Time** components both require Base to be installed first; **AI Extensions** are optional add-ons layered on top.

#### AI Base components

| Component | 5.9.7 | 5.9.6 | 5.9.0 | 5.8.0 | 5.1.14 (LTS) |
| - | - | - | - | - | - |
| **knowledgebase-indexer-v2** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | - |
| **knowledgebase-rag** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | - |
| **embedder** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | - |
| **doc-parser** | 10.11.5 | 10.11.2 | 10.9.0 | 10.7.0 | - |

#### AI Runtime components

| Component | 5.9.7 | 5.9.6 | 5.9.0 | 5.8.0 | 5.1.14 (LTS) |
| - | - | - | - | - | - |
| **agent-builder** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **data-privacy** | 10.11.5 | 10.11.2 | 10.1.0 | 10.1.0 | - |
| **doc-converter** | 10.11.5 | 10.11.2 | 10.2.3 | 10.2.3 | - |
| **evals-judge** | 10.11.5 | 10.11.2 | 10.1.1 | - | - |
| **speech-to-text** | 10.11.5 | 10.11.2 | 10.3.4 | 10.3.3 | - |
| **web-crawler** | 10.11.5 | 10.11.2 | 10.3.5 | 10.3.5 | - |

#### AI Dev Time components

| Component | 5.9.7 | 5.9.6 | 5.9.0 | 5.8.0 | 5.1.14 (LTS) |
| - | - | - | - | - | - |
| **ai-gateway** | 10.35.23 | 10.35.13 | 10.7.0 | - | - |
| **ai-analyst** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **ai-architect** | 10.11.5 | 10.11.2 | - | - | - |
| **ai-assistant** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | - |
| **ai-designer** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **ai-developer** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **planner** | 10.11.5 | 10.11.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **kb-enrichment** | 10.11.5 | 10.11.2 | - | - | - |
| **flowx-docs** | 5.9.7 | 5.9.6 | 5.9.0 | - | - |

#### AI Extensions

| Component | 5.9.7 | 5.9.6 | 5.9.0 | 5.8.0 | 5.1.14 (LTS) |
| - | - | - | - | - | - |
| **modpod** | 10.0.7 | 10.0.7 | 10.0.7 | 10.0.7 | - |
| **ai-observatory** | 10.7.3 | 10.7.2 | 10.3.2 | - | - |

> [!NOTE]
>
> For the plugins matrix, refer to the [5.9.0 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.0-june-2026/deployment-guidelines-v5.9.md).

## Kafka topics

5.9.7 adds, removes, or renames no Kafka topics. For the full multi-release topic matrix, see the [5.9.0 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.0-june-2026/deployment-guidelines-v5.9.md#kafka-topics).

## Deployment notes

### Standard deployment

This maintenance release follows standard FlowX.AI deployment procedures:

1. Review [Configuration changes](#configuration-changes). If you set `metrics.serviceMonitor.relabellings` in your Helm values, rename it before you deploy. If you deploy with Argo CD or run several FlowX releases on one cluster, read [SpiceDB CRD](#spicedb-crd) first.
2. Update container images to the 5.9.7 versions listed in the tables above.
3. Deploy services using your standard deployment process.
4. Verify deployment via **FlowX.AI Designer → Platform Status**.

### Configuration changes

#### Prometheus ServiceMonitor

The `ServiceMonitor` that the FlowX Helm charts create for each service now selects the service's management Service and scrapes `/manage/actuator/prometheus` on the `mngt` port. Before this release, the monitors of most services matched no Service, so Prometheus collected no metrics from them.

The relabeling values now use the names of the Prometheus Operator `ServiceMonitor` fields:

| Helm value | Applied | Replaces |
| - | - | - |
| `metrics.serviceMonitor.relabelings` | Before the scrape, to the target labels | - |
| `metrics.serviceMonitor.metricRelabelings` | After the scrape, to each sample before ingestion | `metrics.serviceMonitor.relabellings` |

The charts no longer read `metrics.serviceMonitor.relabellings`. If you set it, move its rules to `metrics.serviceMonitor.metricRelabelings`, where the `flowx-ai` chart applied them before, or to `metrics.serviceMonitor.relabelings` for rules that act on target labels.

#### Audit index retention

The Audit service can now delete old audit data and roll over by shard size. Both settings are off by default, so the Audit service doesn't delete data unless you set a retention period.

| Environment Variable | Description | Default Value | Component |
| - | - | - | - |
| `FLOWX_ELASTICSEARCH_INDEXRETENTIONDAYS` | Days after a backing index rolls over before it's deleted | Not set: indices are never deleted | audit-core |
| `FLOWX_ELASTICSEARCH_INDEXROLLOVERMAXPRIMARYSHARDSIZE` | Also roll over when a primary shard reaches this size, such as `50gb` | Not set: roll over by age only | audit-core |

> [!WARNING]
>
> When you first set `FLOWX_ELASTICSEARCH_INDEXRETENTIONDAYS`, the Audit service also deletes backing indices that rolled over more than that many days ago. See [Configuring Elasticsearch](https://docs.flowx.ai/5.9/setup-guides/audit-setup-guide.md#configuring-elasticsearch).

#### API description endpoints

The services no longer serve the Swagger UI or the OpenAPI description. `/swagger-ui.html`, `/swagger-ui/**`, and `/v3/api-docs/**` are no longer in the default `SECURITY_PUBLICPATHS` list. If you overrode `SECURITY_PUBLICPATHS`, you can remove these paths from your value.

#### SpiceDB CRD

The `spicedbclusters.authzed.com` CRD now ships in its own `spicedb-operator-crds` subchart of the `flowx` and `flowx-ai` Helm charts, instead of the `spicedb-operator` subchart, behind a new value:

```yaml theme={"dark"}
spicedb-operator-crds:
  enabled: true # default
```

Helm still installs the CRD only on a fresh install, never upgrades it, and never deletes it. The CRD now carries the `argocd.argoproj.io/sync-options: Prune=false,Delete=false` annotation, so Argo CD doesn't prune it or delete it with the Application.

| Your setup | What to do |
| - | - |
| Helm, one FlowX release per cluster | Nothing. The CRD already exists and Helm doesn't change it on upgrade |
| Several FlowX releases on one cluster | The CRD is cluster-scoped. Keep `spicedb-operator-crds.enabled: true` on one release and set it to `false` on the others |
| CRD managed outside the chart, for example by a cluster-wide operator install or a GitOps add-on | Set `spicedb-operator-crds.enabled: false` |

> [!WARNING]
>
> **Argo CD:** upgrade with `spicedb-operator-crds.enabled` left at `true` first, so the `Prune=false` annotation lands on the CRD. Only then set it to `false` where needed. With automated prune, removing the CRD from an Application that hasn't applied the annotation yet deletes the CRD, and with it every `SpiceDBCluster` on the cluster.

Setting the value to `false` never removes an existing CRD. Upgrading the CRD is still a manual `kubectl apply` of the new CRD when the operator is upgraded.

> [!NOTE]
>
> Confirm any required configuration changes against the setup guides before upgrading.

## Third-party supported component versions

Within each version line listed below, versions that have reached upstream end of life are not supported, even though their major/minor is listed.

| FlowX.AI Version | 3rd Party Dependency | Supported Versions |
| - | - | - |
| 5.9.x | Keycloak | 26 |
| 5.9.x | Kafka | 3.9, 4.0, 4.1, 4.2 |
| 5.9.x | PostgreSQL | 16, 17, 18 |
| 5.9.x | Oracle Database | 21c, 23ai |
| 5.9.x | MongoDB | 7, 8 |
| 5.9.x | Redis | 7, 8 |
| 5.9.x | Elasticsearch | 8, 9 |
| 5.9.x | Elasticsearch Sink Connector (\*) | 15 |
| 5.9.x | Angular (Web SDK) | 20.3, 21.2 |
| 5.9.x | React (Web SDK) | 19 |

(\*) Required only if using indexing via Kafka. Multiple sink connector implementations also work, as long as they are compatible with both the deployed Kafka and Elasticsearch version.

> [!NOTE]
>
> The table lists version lines, not individual versions. A version is supported for as long as its vendor still supports it, so check the version you plan to deploy against that vendor's lifecycle page before committing to it. When a version reaches upstream end of life it is no longer supported; upgrade that component to keep your deployment on a supported configuration. Versions can also be added during the family's lifetime as FlowX validates them.

> [!NOTE]
>
> For previous FlowX.AI releases, please refer to the [Release Notes overview](https://docs.flowx.ai/release-notes/overview.md).


## Related topics

- [Deployment guidelines v5.5.0](https://docs.flowx.ai/release-notes/v5.x/v5.5.0-february-2026/deployment-guidelines-v5.5.md)
- [Deployment guidelines v5.6.0](https://docs.flowx.ai/release-notes/v5.x/v5.6.0-march-2026/deployment-guidelines-v5.6.md)
- [Deployment guidelines v5.4.0](https://docs.flowx.ai/release-notes/v5.x/v5.4.0-january-2026/deployment-guidelines-v5.4.md)
- [Deployment guidelines v5.3.0](https://docs.flowx.ai/release-notes/v5.x/v5.3.0-december-2025/deployment-guidelines-v5.3.md)
- [Deployment guidelines v5.2.0](https://docs.flowx.ai/release-notes/v5.x/v5.2.0-november-2025/deployment-guidelines-v5.2.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.