# Your KIE Server. Modernized. AI-Ready. No Rewrite. Source: https://aletyx.ai/enterprise-kie-server/ Built by original team members of jBPM and KIE Server. Enterprise workflow continuity for the AI era. Aletyx Enterprise Build of KIE Server is a drop-in replacement for your existing RHPAM, BAMOE v8, jBPM, and KIE Server workloads running on Java 21, Jakarta EE 10, Spring Boot 3, and a modern application server. With native AI capabilities. Without touching your code. [Assess My Migration Path](https://aletyx.ai/free-trial/) [Talk to an Aletyx Architect](https://aletyx.ai/contact/) If it runs on KIE Server, it runs on Aletyx. Same APIs. Same behavior. Modern stack. Native AI. Zero rewrites Drop-in modernization Flat-fee pricing ## The Vast Majority of Production Workflows Run on KIE Server. The Community Moved On. KIE Server was never transferred to Apache. There are no more open-source releases. The last community version is nearly three years old — riddled with unpatched vulnerabilities. IBM BAMOE v8 is end of life. v9 removes KIE Server entirely. Red Hat PAM is end of life. The community's answer — Kogito — is a fundamentally different architecture that requires a complete rewrite of every workflow asset. For the vast majority of production KIE workflow workloads running on KIE Server today, there is no upgrade path. Only a rewrite — or Aletyx. [See the difference in action](https://aletyx.ai/contact/) ## Moving to Kogito Is Not a Migration. It's a Rewrite. KIE Server and Kogito are architecturally different systems. Different execution models. Different persistence. Different deployment. Different APIs. Every BPMN asset, every integration, every human task configuration must be revisited. This is not a version upgrade — it's a multi-quarter, multi-team program with high delivery risk. For enterprises running hundreds of process definitions across critical systems, the cost and risk are prohibitive. Aletyx understands that you cannot rewrite your core business systems because a new version exists. Continuity is not optional — it's the requirement. [Explore the drop-in alternative](https://aletyx.ai/contact/) ## KIE Server — Restored, Modernized, AI-Ready Aletyx brought KIE Server back. We modernized the runtime from the ground up — modern JVM, modern frameworks, modern application server — while preserving complete behavioral compatibility with your existing workloads. Built and maintained by original team members that led jBPM and KIE Server at Red Hat. Your processes, your integrations, your behavior — unchanged. Your stack — modern, secure, and AI-ready. [Start a guided evaluation](https://aletyx.ai/free-trial/) ## What the Enterprise Build Delivers [Assess My Migration Path](https://aletyx.ai/free-trial/) ### Drop-In Replacement Same APIs. Same execution semantics. Same process behavior. Deploy your existing KJARs on a modern, secure runtime. Your regression tests pass. Your integrations stay intact. ### Modern Stack Java 21. Jakarta EE 10. Spring Boot 3. EAP 8.x. No more legacy application servers, no more outdated dependencies. A production runtime built for today's enterprise infrastructure. ### Native AI Capabilities The same AI capabilities available in Aletyx Enterprise Build of Kogito — now in KIE Server. MCP-based process triggering. AI Agent node. Direct LLM invocation. Modernize with AI without rewriting a single workflow. ### Active Security CVE monitoring and patching on a predictable cadence. The last community release carries years of unpatched vulnerabilities. Aletyx eliminates that exposure. ### Enterprise Hardening Active CVE monitoring and patching. Signed builds. Controlled dependency baselines. Predictable release cycles, no forced upgrades, no breaking changes. ## Bring AI to Your KIE Server. No Rewrite Required. The industry assumption is that AI requires a platform rewrite. Aletyx rejects that premise. We are bringing the full AI capability stack — the same capabilities shipping in Aletyx Enterprise Build of Kogito directly to KIE Server ### MCP Process Triggering AI agents discover and trigger your existing processes via Model Context Protocol. ### AI Agent Node Embed intelligent, ad-hoc AI tasks inside your existing BPMN workflows. ### Direct LLM Invocation Call language models as native workflow steps — no external integration layer. Your existing workflows gain AI capabilities. Your architecture stays the same. Your behavior stays deterministic. [See AI on KIE Server in action](https://aletyx.ai/contact/) ## When the Enterprise Build Is the Right Choice Scenario Why Aletyx You run RHPAM, BAMOE v8, jBPM, or KIE Server in production Drop-in replacement. Modern stack. No rewrite. You've been told to "migrate to Kogito" That's a rewrite. Aletyx gives you modernization without architectural change. You need AI in your existing workflows Native AI capabilities — same as Kogito — delivered on KIE Server. You face unpatched CVEs on aging runtimes Active security patching. Modern dependencies. Enterprise SLAs. Your vendor's support has become an empty policy Direct access to the engineers who built KIE Server. Scenario You run RHPAM, BAMOE v8, jBPM, or KIE Server in production Why Aletyx Drop-in replacement. Modern stack. No rewrite. Scenario You've been told to "migrate to Kogito" Why Aletyx That's a rewrite. Aletyx gives you modernization without architectural change. Scenario You need AI in your existing workflows Why Aletyx Native AI capabilities — same as Kogito — delivered on KIE Server. Scenario You face unpatched CVEs on aging runtimes Why Aletyx Active security patching. Modern dependencies. Enterprise SLAs. Scenario Your vendor's support has become an empty policy Why Aletyx Direct access to the engineers who built KIE Server. ## No One Else Offers KIE Server Continuity Consideration Aletyx IBM (BAMOE) Red Hat (PAM) Apache Community KIE Server support Fully restored and modernized EOL in v8, removed in v9 End of life Not transferred to Apache Migration approach Drop-in replacement Rewrite to v9 N/A Rewrite to Kogito Runtime stack Java 21, Jakarta EE 10, Spring Boot 3, EAP 8.x Frozen at outdated stack Frozen No releases AI capabilities Native: MCP, AI Agent node, LLM invocation None on KIE Server None None Security Active CVE patching v8 EOL priority End of life No SLA, no patches Support Direct access to core engineers Tiered L1→L3 Unavailable Volunteer-based, no SLA Pricing Flat fee, predictable Per-core, yearly increases N/A Free (high internal cost) Consideration ### KIE Server support Aletyx Fully restored and modernized IBM (BAMOE) EOL in v8, removed in v9 Red Hat (PAM) End of life Apache Community Not transferred to Apache Consideration ### Migration approach Aletyx Drop-in replacement IBM (BAMOE) Rewrite to v9 Red Hat (PAM) N/A Apache Community Rewrite to Kogito Consideration ### Runtime stack Aletyx Java 21, Jakarta EE 10, Spring Boot 3, EAP 8.x IBM (BAMOE) Frozen at outdated stack Red Hat (PAM) Frozen Apache Community No releases Consideration ### AI capabilities Aletyx Native: MCP, AI Agent node, LLM invocation IBM (BAMOE) None on KIE Server Red Hat (PAM) None Apache Community None Consideration ### Security Aletyx Active CVE patching IBM (BAMOE) v8 EOL priority Red Hat (PAM) End of life Apache Community No SLA, no patches Consideration ### Support Aletyx Direct access to core engineers IBM (BAMOE) Tiered L1→L3 Red Hat (PAM) Unavailable Apache Community Volunteer-based, no SLA Consideration ### Pricing Aletyx Flat fee, predictable IBM (BAMOE) Per-core, yearly increases Red Hat (PAM) N/A Apache Community Free (high internal cost) [Get a detailed migration assessment](https://aletyx.ai/contact/) ## If It Works, Modernize It. Don't Rewrite It. If your KIE Server workloads run well today, you do not need to move to Kogito. Aletyx Enterprise Build of KIE Server gives you a modern, secure, AI-ready runtime — and that is a complete, long-term answer. Aletyx Enterprise Build of Kogito is the right choice for greenfield projects — new workflows built cloud-native from the start. Unless you have a specific business demand that requires rearchitecting your current systems, there is no reason to rewrite what already works. Modernize what you have. Build new on Kogito. Never be forced into a rewrite you don't need [See how Aletyx preserves your existing workloads](https://aletyx.ai/contact/) Frequently Asked Questions ## Clear answers to your questions. [Talk to our team](https://aletyx.ai/contact/) 01 Is this a drop-in replacement for my existing RHPAM, BAMOE v8, jBPM v7, or KIE Server deployment? Yes. Same APIs. Same execution semantics. Same process behavior. Your existing KJARs deploy directly onto the Enterprise Build. Your regression tests pass. Your integrations stay intact. 02 What stack does it run on? Java 21. Jakarta EE 10. Spring Boot 3. EAP 8.x and WildFly 35+. Kubernetes-ready. No more legacy application servers or outdated dependencies. 03 Why not just migrate to Kogito? Moving to Kogito is a rewrite, not a migration. Kogito and KIE Server are architecturally different, different execution model, different persistence, different deployment, different APIs. Every BPMN asset and every integration has to be revisited. For workloads that already run well, that is a multi-quarter program with no new business value. Aletyx gives you a modern, AI-ready runtime without the rewrite. 04 What happened to KIE Server in the open-source ecosystem? KIE Server was never transferred to Apache. The last community release is nearly three years old. The community focused on Kogito instead, which is a different architecture. Aletyx restored KIE Server as a fully supported, modernized product. 05 What AI capabilities are available? The same AI capabilities shipping in Aletyx Enterprise Build of Kogito. MCP-based process triggering so AI agents can discover and invoke your workflows. AI Agent nodes for intelligent steps inside BPMN. Direct LLM invocation as a native workflow task. All governed by the deterministic engine around them. 06 Can I use Business Central with this? Yes. We work with existing Business Central deployments for customers who rely on it today, and we collaborate with the customer on moving to an updated authoring and monitoring toolset over time. Decision Control is not a Business Central replacement — it is a different approach that delivers some of the same benefits with a different model. 07 What support do I get? Engineer-led support with direct access to the team behind the product. No tiered L1 to L3 bouncing. SLA and coverage scale with your subscription tier — see the pricing page for details. 08 How long does migration typically take? It varies with application size, but an average application can be migrated in about a week. Since the runtime is a drop-in replacement, most of the effort is validation rather than code changes. We can scope yours during a free 60-day evaluation. Your last chance ## Modernize KIE Server.Add AI. No Rewrite. The exact processes running today will run on Aletyx tomorrow on a modern stack, with native AI, and full enterprise support. [Start My Free 60-Day Evaluation](https://aletyx.ai/free-trial/) [Talk to an Aletyx Architect](https://aletyx.ai/contact/) No credit card. Full access. Direct support.