Skip to main content
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.
Platform Status screen showing component versions

Component versions

Embedded components

  • SpiceDB
  • DGraph

Renderers

Plugins

AI Platform

Note: The ai-platform-models service has been removed in 5.7.0. LLM provider and model configuration has moved to the AI Providers UI within the Organization Manager.

Third-party supported component versions

The following versions of third-party dependencies are no longer supported:
  • Keycloak versions older than 26
  • Kafka versions older than 3.8
  • Redis versions older than 7.4

Self-hosted deployment changes

First on-premises release since 5.4.0. This section covers critical configuration changes for self-hosted (on-premises) deployments.

Supported upgrade paths

Organization ID (mandatory for upgrades)

The Organization ID is how FlowX identifies your installation. How it is obtained depends on your deployment path:
  • Fresh install: The Organization ID is created automatically during the guided setup flow (Designer first-launch screen). No manual configuration needed.
  • Upgrade from 5.1.x: FlowX registers your organization in the SaaS licensing infrastructure and provides an Organization ID (UUID). Set ORGANIZATION_ID on all 19 services before deploying 5.7.0 images — Liquibase migrations use it to replace the default organization.
Affected services (all 19): process-engine, admin, audit-core, authorization-system, advancing-controller, events-gateway, cms-core, scheduler-core, data-search, document-plugin, nosql-db-runner, notification-plugin, task-management-plugin, integration-designer, organization-manager, email-gateway, application-manager, runtime-manager, license.
Do not deploy 5.7.0 images without setting ORGANIZATION_ID on upgrade scenarios. Services will fail to start if Liquibase migrations cannot find the organization ID.
Active vs inactive instances. Liquibase migrations automatically update the Organization ID on active process instances only. Inactive or archived instances require separate migration handled by the FlowX team during guided deployment. Contact your FlowX representative for details.

License service (new)

Self-hosted deployments must configure the License service to connect to FlowX SaaS for license validation and usage reporting. See the License service setup guide for complete configuration.

IAM / Keycloak changes

FlowX.AI now uses a two-realm architecture in Keycloak and JWT public key validation (replacing opaque-token introspection). These changes were introduced in 5.5.0 (SaaS) and are now relevant for self-hosted deployments.
  • Token validation: security.type switches from oauth2 to jwt-public-key on all services
  • Service accounts realm: A dedicated realm (00000002-0002-4002-8002-000000000002) holds all service account clients, separate from the user realm
  • Organization manager: Now a required dependency for all services (provides realm resolution)
  • flowx-platform-authorize client: No longer needed — remove from Keycloak
  • Master realm credentials: The authorization-system service needs Keycloak admin access for realm migrations. If you cannot provide admin credentials, see Manual Keycloak configuration.
  • SMTP: Must be configured in Keycloak for password reset and user invitations
For complete IAM setup instructions, see the Configuring an IAM solution guide.

Environment info deprecation

The Configure Environment Info feature (PATCH /api/platform/environment) is deprecated and removed. Environment name is now set during organization registration. The following are no longer used:
  • FLOWX_CLIENT_NAME environment variable
  • FLOWX_ENVIRONMENT_NAME environment variable
  • environmentDetails section in the /api/init response

Kafka integration changes

Fx-Organization-Id header (mandatory)

All FlowX Kafka consumers now validate the Fx-Organization-Id header on every incoming message. Messages without this header are rejected with a non-retryable MissingKafkaHeaderException.
Action required for custom Kafka integrations. If you have custom Kafka producers that publish directly to FlowX topics (starting processes, sending task events, responding to engine requests), you must add the Fx-Organization-Id header to every message. Set it to the Organization UUID (ORGANIZATION_ID value).
See the Creating a Kafka producer guide for details.

New Kafka topics


Environment variables

Environment variable names follow Spring relaxed binding conventions. For example, the YAML property security.oauth2.sa-realm maps to the environment variable SECURITY_OAUTH2_SAREALM (dots become underscores, hyphens are removed, all uppercase).

New environment variables

Removed environment variables

For upgrades: Remove these variables only after the Liquibase migrations have completed successfully. If you remove them before starting services for the first time on 5.7.0, the migrations may fail. The recommended sequence is: (1) add new variables, (2) deploy 5.7.0 images, (3) let migrations run, (4) verify services are healthy, (5) remove old variables in a follow-up deployment.
Last modified on September 10, 2026