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

> Component versions and deployment-level changes for FlowX.AI 5.13.0.

> [!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.13 is a **SaaS-managed release**. Deployment-level changes, including infrastructure, Kafka topics, and service configuration, are handled automatically by FlowX. The information below is provided for transparency. Self-hosted deployments receive these capabilities with the next LTS release family.

## Component versions

The versions below are the component versions that make up FlowX.AI 5.13.0. On SaaS these are managed by FlowX; the list is provided for transparency.

### Core components

| Component | 5.13.0 |
| - | - |
| **admin** | 11.97.0 |
| **advancing-controller** | 11.67.0 |
| **application-manager** | 11.101.0 |
| **audit-core** | 11.69.0 |
| **authorization-system** | 11.78.0 |
| **cms-core** | 11.88.0 |
| **data-search** | 11.67.0 |
| **data-sync** | 11.68.0 |
| **designer** | 11.168.1 |
| **designer-user** | 11.8.0 |
| **document-plugin** | 11.95.0 |
| **email-gateway** | 11.83.0 |
| **events-gateway** | 11.72.0 |
| **file-gateway** | 11.79.0 |
| **integration-designer** | 11.119.1 |
| **license** | 11.72.0 |
| **nosql-db-runner** | 11.73.0 |
| **notification-plugin** | 11.88.0 |
| **organization-manager** | 11.77.0 |
| **process-engine** | 11.104.0 |
| **runtime-manager** | 11.101.0 |
| **scheduler-core** | 11.69.0 |
| **task-management-plugin** | 11.84.0 |
| **webhook-gateway** | 11.78.0 |

**designer-user** is new in 5.13. It backs the Designer notification center.

### AI base components

| Component | 5.13.0 |
| - | - |
| **embedder** | 11.6.0 |
| **knowledgebase-indexer-v2** | 11.6.0 |
| **knowledgebase-rag** | 11.6.0 |
| **doc-parser** | 11.6.0 |

### AI dev-time components

| Component | 5.13.0 |
| - | - |
| **ai-gateway** | 11.85.0 |
| **ai-analyst** | 11.6.0 |
| **ai-architect** | 11.6.0 |
| **ai-assistant** | 11.6.0 |
| **ai-designer** | 11.6.0 |
| **ai-developer** | 11.6.0 |
| **harness** | 11.6.0 |
| **ai-render-host** | 11.168.1 |
| **kb-enrichment** | 11.6.0 |
| **planner** | 11.6.0 |

**harness** and **ai-render-host** are new in 5.13. Together they run the [Developer Agentic Harness](https://docs.flowx.ai/5.9/ai-platform/developer-agentic-harness.md): harness is the agent service, and ai-render-host renders UI flows headlessly for the agent. ai-render-host ships at the designer version.

### AI runtime components

| Component | 5.13.0 |
| - | - |
| **agent-builder** | 11.6.0 |
| **cee-pii** | 11.6.0 |
| **data-privacy** | 11.6.0 |
| **doc-converter** | 11.6.0 |
| **dynamic-classifier** | 11.6.0 |
| **evals-judge** | 11.6.0 |
| **speech-to-text** | 11.6.0 |
| **web-crawler** | 11.6.0 |

### AI extensions

| Component | 5.13.0 |
| - | - |
| **modpod** | 11.0.1 |
| **observatory-api** | 11.10.2 |
| **observatory-platform** | 11.10.2 |
| **observatory-web** | 11.10.2 |

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

The web SDKs ship at the **designer** version (`11.168.1` for FlowX.AI 5.13.0). The native iOS and Android renderers version independently.

| Component | 5.13.0 |
| - | - |
| **@flowx/angular-sdk** | 11.168.1 |
| **@flowx/angular-theme** | 11.168.1 |
| **@flowx/angular-ui-toolkit** | 11.168.1 |
| **@flowx/react-sdk** | 11.168.1 |
| **@flowx/react-theme** | 11.168.1 |
| **@flowx/react-ui-toolkit** | 11.168.1 |
| **@flowx/react-native-sdk** | 11.168.1 |
| **@flowx/react-native-theme** | 11.168.1 |
| **@flowx/react-native-ui-toolkit** | 11.168.1 |
| **@flowx/core-sdk** | 11.168.1 |
| **@flowx/core-theme** | 11.168.1 |
| **react-saas** | 11.168.1 |
| **iOS renderer** | TBD |
| **Android renderer** | TBD |

The **react-saas** container app tracks the designer version.

***

## Configuration changes

> [!NOTE]
>
> On SaaS, required configuration changes are applied automatically by FlowX. The changes below are listed for transparency. Self-hosted deployments will receive them, re-verified, with the next LTS release family.

### New Kafka topics

These topics back new 5.13 capabilities. On SaaS they are created and managed automatically.

**Notification center:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.designer-user.notifications.v1` | application-manager, process-engine → designer-user |

Notifications now pass through designer-user, which stores them and forwards them to events-gateway on the existing `ai.flowx.eventsgateway.user.notifications.v1` topic for delivery to the Designer.

**Move token:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.core.trigger.token-move.batch.v1` | process-engine → process-engine |

**Run auditing:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.core.run.segment.v1` | process-engine, integration-designer → audit-core |
| `ai.flowx.core.runtime.failure.v1` | process-engine, integration-designer → audit-core |

### New services

The Developer Agentic Harness adds the **harness** and **ai-render-host** services to the AI dev-time group, with a dedicated PostgreSQL database for harness sessions. The notification center adds the **designer-user** core service, which uses MongoDB, Redis, and Kafka. On SaaS these services and their databases are provisioned and managed by FlowX.

### New service dependency: process-engine and object storage

Oversized workflow responses and UI flow updates are now offloaded to object storage instead of travelling inline on Kafka. The process engine reads these offloaded payloads, so it now depends on object storage in addition to its existing databases. On SaaS this connection is provisioned and managed by FlowX.

### Changed default: Elasticsearch replica auto-expansion

New process instance indices and new audit log indices now use the Elasticsearch `auto_expand_replicas` setting, with a default of `0-1`. Elasticsearch keeps 0 replicas when the cluster has one data node and 1 replica when it has two or more, and adjusts the count as nodes join or leave. On SaaS, Elasticsearch is managed by FlowX.

| Environment Variable | Description | Default Value | Component |
| - | - | - | - |
| `FLOWX_ELASTICSEARCH_INDEXSETTINGS_AUTOEXPANDREPLICAS` | Replica range that Elasticsearch applies to new indices. Set to `false` to use the fixed `FLOWX_ELASTICSEARCH_INDEXSETTINGS_REPLICAS` value instead | `0-1` | process-engine, audit-core |

* **Overrides the fixed replica count:** while auto-expansion is on, `FLOWX_ELASTICSEARCH_INDEXSETTINGS_REPLICAS` has no effect on new indices.
* **New indices only:** the setting applies to the `process_instance` index and index template and to the audit logs data stream template. Existing indices keep their current settings.
* **Disk usage:** on clusters with two or more data nodes, the replica roughly doubles the disk space these indices use.

> [!WARNING]
>
> **Breaking change for self-hosted upgrades.** Self-hosted deployments receive this change with the next LTS release family. A deployment that pins a fixed replica count, for example `FLOWX_ELASTICSEARCH_INDEXSETTINGS_REPLICAS=3`, loses it on new indices unless it also sets `FLOWX_ELASTICSEARCH_INDEXSETTINGS_AUTOEXPANDREPLICAS=false`. On multi-node clusters, check free disk space before upgrading.

To apply auto-expansion to indices created before the upgrade, update their settings once:

```http theme={"dark"}
PUT process_instance*,.ds-audit-logs*/_settings
{"index": {"auto_expand_replicas": "0-1"}}
```

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


## Related topics

- [FlowX.AI 5.13.0 Release Notes](https://docs.flowx.ai/release-notes/v5.x/v5.13.0-september-2026/v5.13.0-september-2026.md)
- [Deployment guidelines v5.1.13](https://docs.flowx.ai/release-notes/v5.x/v5.1.x-lts/deployment-guidelines-v5.1.13.md)
- [Deployment guidelines v5.9.5](https://docs.flowx.ai/release-notes/v5.x/v5.9.5-september-2026/deployment-guidelines-v5.9.5.md)
- [Deployment guidelines v5.9.6](https://docs.flowx.ai/release-notes/v5.x/v5.9.6-october-2026/deployment-guidelines-v5.9.6.md)
- [Deployment guidelines v5.9.4](https://docs.flowx.ai/release-notes/v5.x/v5.9.4-august-2026/deployment-guidelines-v5.9.4.md)


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