> ## 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.5

> Component versions, configuration, and deployment notes for FlowX.AI 5.9.5 (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.5 is a maintenance release for the 5.9.x LTS line. The upgrade from 5.9.4 is non-breaking and requires no data migration. The headline addition, native PostgreSQL partitioning, is opt-in: deployments that never enabled data partitioning are not affected. Review [Configuration changes](#configuration-changes) before you deploy.

> [card] Upgrade Path
>
> **5.9.4 → 5.9.5**: Direct upgrade. No data migration is required.
>
> 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.3 or earlier directly?** Review the [5.9.4 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.4-august-2026/deployment-guidelines-v5.9.4.md) first: the Helm image registry split applies when you skip 5.9.4. Upgrading from 5.9.0, 5.9.1, or 5.9.2, also review the [5.9.2 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.2-july-2026/deployment-guidelines-v5.9.2.md) for the organization-ID migration fix and manually marked Liquibase changesets.

## Component versions

### Core components

| Component | 5.9.5 | 5.9.4 | 5.9.0 | 5.8.0 | 5.1.13 (LTS) |
| - | - | - | - | - | - |
| **process-engine** | 10.174.10 | 10.171.3 | 10.135.0 | 10.106.0 | 9.76.10 |
| **admin** | 10.152.7 | 10.149.3 | 10.116.0 | 10.93.0 | 9.76.8 |
| **designer** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **cms-core** | 10.113.7 | 10.110.4 | 10.86.0 | 10.67.0 | 9.47.6 |
| **scheduler-core** | 10.94.6 | 10.91.2 | 10.70.0 | 10.53.0 | 9.36.5 |
| **events-gateway** | 10.100.7 | 10.97.2 | 10.72.0 | 10.55.0 | 9.37.5 |
| **notification-plugin** | 10.110.7 | 10.107.4 | 10.83.0 | 10.64.0 | 9.40.5 |
| **document-plugin** | 10.124.7 | 10.121.3 | 10.94.0 | 10.75.0 | 9.45.5 |
| **task-management-plugin** | 10.112.6 | 10.109.3 | 10.84.0 | 10.66.0 | 9.44.7 |
| **reporting-plugin**\* | 10.1.6 | 10.1.6 | 0.2.6 | 0.2.6 | 0.2.8 |
| **data-search** | 10.92.6 | 10.89.2 | 10.69.0 | 10.52.0 | 9.33.5 |
| **audit-core** | 10.102.6 | 10.99.2 | 10.79.0 | 10.63.0 | 9.41.5 |
| **advancing-controller** | 10.98.7 | 10.95.2 | 10.73.0 | 10.55.0 | 9.36.6 |
| **integration-designer** | 10.200.9 | 10.197.5 | 10.162.0 | 10.128.0 | 9.60.7 |
| **application-manager** | 10.158.7 | 10.155.5 | 10.123.0 | 10.97.0 | 9.83.8 |
| **runtime-manager** | 10.158.7 | 10.155.5 | 10.123.0 | 10.97.0 | 9.83.8 |
| **data-sync** | 10.107.7 | 10.104.3 | 10.81.0 | 10.58.0 | 9.34.4 |
| **authorization-system** | 10.122.7 | 10.119.3 | 10.96.1 | 10.77.0 | 9.44.6 |
| **nosql-db-runner** | 10.101.6 | 10.98.2 | 10.75.0 | 10.56.0 | 9.32.5 |
| **email-gateway** | 10.101.6 | 10.98.2 | 10.74.0 | 10.56.0 | - |
| **organization-manager** | 10.98.6 | 10.95.2 | 10.71.0 | 10.53.0 | - |
| **webhook-gateway** | 10.69.6 | 10.66.2 | 10.44.0 | 10.25.0 | - |
| **file-gateway** | 10.33.7 | 10.30.2 | 10.8.0 | - | - |
| **license** | 10.87.6 | 10.84.2 | 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**: 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) for details.
* **Qdrant** (vector database): bundled in the AI Platform 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.5 | 5.9.4 | 5.9.0 | 5.8.0 | 5.1.13 (LTS) |
| - | - | - | - | - | - |
| **@flowx/angular-sdk** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/angular-theme** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/angular-ui-toolkit** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/react-sdk** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/react-theme** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/react-ui-toolkit** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/react-native-sdk** | 10.277.0 | 10.277.0 | 10.230.2 | - | - |
| **@flowx/react-native-theme** | 10.277.0 | 10.277.0 | 10.230.2 | - | - |
| **@flowx/react-native-ui-toolkit** | 10.277.0 | 10.277.0 | 10.230.2 | - | - |
| **@flowx/core-sdk** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **@flowx/core-theme** | 10.282.5 | 10.275.0 | 10.230.2 | 10.181.0 | 9.165.3 |
| **react-saas** | 10.282.5 | 10.275.0 | 10.230.2 | - | - |
| **iOS renderer** | 10.6.2 | 10.6.0 | 10.4.1 | 10.3.0 | 9.0.32 |
| **Android renderer** | 10.9.3 | 10.8.0 | 10.5.0 | 10.3.0 | 9.0.44 |

### 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.5 | 5.9.4 | 5.9.0 | 5.8.0 | 5.1.13 (LTS) |
| - | - | - | - | - | - |
| **knowledgebase-indexer-v2** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | - |
| **knowledgebase-rag** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | - |
| **embedder** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | - |
| **doc-parser** | 10.11.0 | 10.10.2 | 10.9.0 | 10.7.0 | - |

#### AI Runtime components

| Component | 5.9.5 | 5.9.4 | 5.9.0 | 5.8.0 | 5.1.13 (LTS) |
| - | - | - | - | - | - |
| **agent-builder** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **data-privacy** | 10.11.0 | 10.10.2 | 10.1.0 | 10.1.0 | - |
| **doc-converter** | 10.11.0 | 10.10.2 | 10.2.3 | 10.2.3 | - |
| **evals-judge** | 10.11.0 | 10.10.2 | 10.1.1 | - | - |
| **speech-to-text** | 10.11.0 | 10.10.2 | 10.3.4 | 10.3.3 | - |
| **web-crawler** | 10.11.0 | 10.10.2 | 10.3.5 | 10.3.5 | - |

#### AI Dev Time components

| Component | 5.9.5 | 5.9.4 | 5.9.0 | 5.8.0 | 5.1.13 (LTS) |
| - | - | - | - | - | - |
| **ai-gateway** | 10.35.6 | 10.32.2 | 10.7.0 | - | - |
| **ai-analyst** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **ai-architect** | 10.11.0 | 10.10.2 | - | - | - |
| **ai-assistant** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | - |
| **ai-designer** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **ai-developer** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **planner** | 10.11.0 | 10.10.2 | 10.7.0 | 10.7.0 | 9.4.8 |
| **kb-enrichment** | 10.11.0 | 10.10.2 | - | - | - |
| **flowx-docs** | 5.9.5 | 5.9.4 | 5.9.0 | - | - |

#### AI Extensions

| Component | 5.9.5 | 5.9.4 | 5.9.0 | 5.8.0 | 5.1.13 (LTS) |
| - | - | - | - | - | - |
| **modpod** | 10.0.7 | 10.0.7 | 10.0.7 | 10.0.7 | - |
| **ai-observatory** | 10.7.2 | 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

> [!NOTE]
>
> 5.9.5 introduces no new Kafka topics over 5.9.4. 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): everything new in this release is opt-in or ships with a safe default, so no values change is required for a standard upgrade.
2. Update container images to the 5.9.5 versions listed in the table above.
3. Deploy services using your standard deployment process.
4. Verify deployment via **FlowX.AI Designer → Platform Status**.

### Configuration changes

#### Native PostgreSQL partitioning (opt-in)

Process-instance archiving on PostgreSQL can now use native declarative partitions instead of the legacy copy-based mechanism. Data partitioning itself remains **off by default** (`FLOWX_DATA_PARTITIONING_ENABLED` is `false`), so deployments that never enabled it are not affected.

New process-engine variables:

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_DATA_PARTITIONING_ARCHIVING_POSTGRESNATIVE` | Use native PostgreSQL partitions for archiving when partitioning is enabled. PostgreSQL only; other databases keep the existing mechanism. | `true` |
| `FLOWX_DATA_PARTITIONING_PREMAKECRONEXPRESSION` | Schedule for the job that creates upcoming partitions in advance. | `0 0 23 * * ?` |
| `FLOWX_DATA_PARTITIONING_PREMAKEPARTITIONSAHEAD` | How many future partitions the job keeps created ahead of the current one. | `2` |

> [!WARNING]
>
> Enabling native partitioning converts the process-instance tables to partitioned tables, and the conversion is one way: there is no supported path back to unpartitioned tables. Review the [partitioning and archiving setup guide](https://docs.flowx.ai/5.9/setup-guides/flowx-engine-setup-guide/process-instance-data-archiving.md#native-postgresql-partitioning) before turning it on.

#### Document plugin: processing size limits

The document plugin now enforces size limits on archive, encryption, and extraction operations. Input over the limit is rejected instead of processed. The defaults are generous; override them only if your documents legitimately exceed them.

| Environment Variable | Description | Default Value |
| - | - | - |
| `DOCUMENT_ARCHIVE_MAX_FILE_SIZE` | Maximum size, in bytes, of a file accepted for archive operations. | `209715200` (200 MB) |
| `DOCUMENT_ENCRYPTION_MAX_FILE_SIZE` | Maximum size, in bytes, of a file accepted for encryption. | `104857600` (100 MB) |
| `DOCUMENT_EXTRACT_MAX_UNCOMPRESSED_SIZE` | Maximum total uncompressed size, in bytes, an archive may expand to during extraction. | `209715200` (200 MB) |

#### Integration Designer: workflow output size guard

Workflow output published to Kafka is now size-checked before sending. A root workflow output that exceeds the limit fails the workflow run with the failure type `outputTooLargeForKafka` instead of being silently dropped by the broker's message-size limit. The check applies to root workflow outputs on automatic and default-path completion; subworkflow outputs are not checked.

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_KAFKA_PAYLOAD_SIZE_LIMIT` | Maximum serialized size, in bytes, of a root workflow output published to Kafka. | `786432` |

> [!TIP]
>
> Keep this limit below your broker's `max.message.bytes`. The default, 768 KB, sits safely under the common 1 MB broker default.

#### Advancing datasource metrics

The process engine and Integration Designer now register their advancing datasource under a named connection pool (`advancing`), so its metrics are distinguishable from the main datasource pool in Prometheus. No configuration action is required.

> [!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.