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.

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
Self-hosted deployment changes
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_IDon all 19 services before deploying 5.7.0 images — Liquibase migrations use it to replace the default organization.
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.typeswitches fromoauth2tojwt-public-keyon 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-authorizeclient: 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
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_NAMEenvironment variableFLOWX_ENVIRONMENT_NAMEenvironment variableenvironmentDetailssection in the/api/initresponse
Kafka integration changes
Fx-Organization-Id header (mandatory)
All FlowX Kafka consumers now validate theFx-Organization-Id header on every incoming message. Messages without this header are rejected with a non-retryable MissingKafkaHeaderException.
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).
