Deployment guidelines v5.9.4

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.4 is a maintenance release for the 5.9.x LTS line. The platform upgrade from 5.9.3 is non-breaking, but this release changes how the Helm charts express the container image location, so review Configuration changes before you deploy.

Upgrade Path

5.9.3 → 5.9.4: 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.

Helm values change. The charts now express the image location as image.registry plus image.repository instead of one combined path. Deployments that set global.imageRegistry need no action. Deployments that embedded the registry inside image.repository must move it out before upgrading — see Helm charts: image registry split.

Upgrading from 5.9.0, 5.9.1, or 5.9.2 directly? Review the 5.9.2 deployment guidelines first — they include required steps for the organization-ID migration fix and manually marked Liquibase changesets that also apply when you skip 5.9.2.

Component versions

Core components

Component	5.9.4	5.9.3	5.9.0	5.8.0	5.1.11 (LTS)
process-engine	10.171.3	10.165.0	10.135.0	10.106.0	9.76.3
admin	10.149.3	10.144.0	10.116.0	10.93.0	9.76.3
designer	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
cms-core	10.110.4	10.105.0	10.86.0	10.67.0	9.47.3
scheduler-core	10.91.2	10.87.0	10.70.0	10.53.0	9.36.3
events-gateway	10.97.2	10.93.0	10.72.0	10.55.0	9.37.3
notification-plugin	10.107.4	10.103.0	10.83.0	10.64.0	9.40.3
document-plugin	10.121.3	10.116.0	10.94.0	10.75.0	9.45.3
task-management-plugin	10.109.3	10.105.0	10.84.0	10.66.0	9.44.4
reporting-plugin*	10.1.6	10.1.6	0.2.6	0.2.6	0.2.8
data-search	10.89.2	10.85.0	10.69.0	10.52.0	9.33.3
audit-core	10.99.2	10.95.0	10.79.0	10.63.0	9.41.3
advancing-controller	10.95.2	10.91.0	10.73.0	10.55.0	9.36.3
integration-designer	10.197.5	10.192.0	10.162.0	10.128.0	9.60.3
application-manager	10.155.5	10.151.1	10.123.0	10.97.0	9.83.5
runtime-manager	10.155.5	10.151.1	10.123.0	10.97.0	9.83.5
data-sync	10.104.3	10.100.0	10.81.0	10.58.0	9.34.2
authorization-system	10.119.3	10.115.0	10.96.1	10.77.0	9.44.4
nosql-db-runner	10.98.2	10.94.0	10.75.0	10.56.0	9.32.3
email-gateway	10.98.2	10.93.0	10.74.0	10.56.0	-
organization-manager	10.95.2	10.90.0	10.71.0	10.53.0	-
webhook-gateway	10.66.2	10.62.0	10.44.0	10.25.0	-
file-gateway	10.30.2	10.25.0	10.8.0	-	-
license	10.84.2	10.80.0	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 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 for deployment and configuration.

Renderers

Component	5.9.4	5.9.3	5.9.0	5.8.0	5.1.11 (LTS)
@flowx/angular-sdk	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/angular-theme	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/angular-ui-toolkit	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/react-sdk	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/react-theme	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/react-ui-toolkit	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/react-native-sdk	10.266.0	10.266.0	10.230.2	-	-
@flowx/react-native-theme	10.266.0	10.266.0	10.230.2	-	-
@flowx/react-native-ui-toolkit	10.266.0	10.266.0	10.230.2	-	-
@flowx/core-sdk	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
@flowx/core-theme	10.275.0	10.265.6	10.230.2	10.181.0	9.164.15
react-saas	10.275.0	10.265.6	10.230.2	-	-
iOS renderer	10.6.0	10.5.11	10.4.1	10.3.0	9.0.27
Android renderer	10.8.0	10.6.6	10.5.0	10.3.0	9.0.37

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.4	5.9.3	5.9.0	5.8.0	5.1.11 (LTS)
knowledgebase-indexer-v2	10.10.2	10.9.1	10.7.0	10.7.0	-
knowledgebase-rag	10.10.2	10.9.1	10.7.0	10.7.0	-
embedder	10.10.2	10.9.1	10.7.0	10.7.0	-
doc-parser	10.10.2	10.9.1	10.9.0	10.7.0	-

AI Runtime components

Component	5.9.4	5.9.3	5.9.0	5.8.0	5.1.11 (LTS)
agent-builder	10.10.2	10.9.1	10.7.0	10.7.0	9.4.2
data-privacy	10.10.2	10.9.1	10.1.0	10.1.0	-
doc-converter	10.10.2	10.9.1	10.2.3	10.2.3	-
evals-judge	10.10.2	10.9.1	10.1.1	-	-
speech-to-text	10.10.2	10.9.1	10.3.4	-	-
web-crawler	10.10.2	10.9.1	10.3.5	10.3.5	-

AI Dev Time components

Component	5.9.4	5.9.3	5.9.0	5.8.0	5.1.11 (LTS)
ai-gateway	10.32.2	10.27.0	10.7.0	-	-
ai-analyst	10.10.2	10.9.1	10.7.0	10.7.0	9.4.2
ai-architect	10.10.2	10.9.1	-	-	-
ai-assistant	10.10.2	10.9.1	10.7.0	10.7.0	-
ai-designer	10.10.2	10.9.1	10.7.0	10.7.0	9.4.2
ai-developer	10.10.2	10.9.1	10.7.0	10.7.0	9.4.2
planner	10.10.2	10.9.1	10.7.0	10.7.0	9.4.2
kb-enrichment	10.10.2	10.9.1	-	-	-
flowx-docs	5.9.4	5.9.3	5.9.0	-	-

AI Extensions

Component	5.9.4	5.9.3	5.9.0	5.8.0	5.1.11 (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	-	-

For the plugins matrix, refer to the 5.9.0 deployment guidelines.

Kafka topics

5.9.4 introduces no new Kafka topics over 5.9.3. For the full multi-release topic matrix, see the 5.9.0 deployment guidelines.

Deployment notes

Standard deployment

This maintenance release follows standard FlowX.AI deployment procedures:

Apply the Helm values change described in Configuration changes, if it affects your setup.
Update container images to the 5.9.4 versions listed in the table above.
Deploy services using your standard deployment process.
Verify deployment via FlowX.AI Designer → Platform Status.

Configuration changes

Helm charts: image registry split

Across the FlowX chart set, the container image reference is now expressed as two fields instead of one combined path. The default image location is unchanged: each chart still resolves to the same registry/repository:tag.

# Before
image:
  repository: <registry>/<image-name>

# After
image:
  registry: <registry>
  repository: <image-name>

The registry resolves to global.imageRegistry when that is set, and otherwise to the chart’s own image.registry. This makes global.imageRegistry a single, chart-wide override that redirects the charts to your registry, while each chart ships the correct bare image.repository by default. Upgrade notes

If you set global.imageRegistry to point the charts at your own registry (the standard, documented approach): no action is required. Your override continues to work, and it now applies cleanly to the default bare repository names.
If you embedded the registry inside image.repository (for example image.repository: harbor.mycorp.internal/flowx/<image-name>): move the registry portion out. Set it through global.imageRegistry, or the chart’s image.registry, and let image.repository fall back to its default bare image name. Leaving the registry in image.repository alongside the now-populated image.registry prepends the registry twice. This applies to deployments configured from the FlowX setup guides before 5.9.4, which showed the combined form. If your values files were built from those examples, check them before upgrading.

Events Gateway service account

Events Gateway now authenticates to the Runtime Manager with its own service account, flowx-events-gateway-sa, in the service-accounts realm. It needs this identity to resolve and authorize a subscription before admitting the stream. Two new configuration values are involved, and both take the same secret:

Service	Environment Variable	Purpose
authorization-system	`SPRING_LIQUIBASE_PARAMETERS_SECRETS_SERVICEACCOUNTS_FLOWXEVENTSGATEWAYSA`	Secret the migration assigns to the client it creates
events-gateway	`SPRING_SECURITY_OAUTH2_CLIENT_REGISTRATION_MAINIDENTITY_CLIENTSECRET`	Secret Events Gateway authenticates with

Upgrade notes

If you deploy with the FlowX Helm charts and authorization-system runs its migrations with Keycloak admin access: no action is required. The chart already maps both values to the KEYCLOAK_EVENTS_GATEWAY_CLIENT_SECRET key of the keycloak-flowx-realm-clients secret, and the authorization-system migration creates the client and grants it the SA_FLOWX role.
If you manage Keycloak clients outside the chart (external IdP, or authorization-system cannot provision clients): create flowx-events-gateway-sa in the service-accounts realm as a confidential client with service accounts enabled and only the client-credentials grant, then supply its secret to both values above.

If flowx-events-gateway-sa already exists, the migration leaves its secret untouched by design. A pre-existing client whose secret does not match the one given to Events Gateway will not be corrected on upgrade, and Events Gateway will fail to authorize subscriptions. Make the two match manually in that case.

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.

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.

For previous FlowX.AI releases, please refer to the Release Notes overview.

​Upgrade overview

Upgrade Path

​Component versions

​Core components

​Embedded components

​Renderers

​AI components

​AI Base components

​AI Runtime components

​AI Dev Time components

​AI Extensions

​Kafka topics

​Deployment notes

​Standard deployment

​Configuration changes

​Helm charts: image registry split

​Events Gateway service account

​Third-party supported component versions

Upgrade overview

Component versions

Core components

Embedded components

Renderers

AI components

AI Base components

AI Runtime components

AI Dev Time components

AI Extensions

Kafka topics

Deployment notes

Standard deployment

Configuration changes

Helm charts: image registry split

Events Gateway service account

Third-party supported component versions