Your processes run unchanged
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.
From the team that led jBPM and KIE Server at Red Hat and IBM
Your processes, preserved. Modernize without a rewrite.
A drop-in upgrade for RHPAM, BAMOE v8, jBPM and KIE Server, on Java 21 and Spring Boot 4. No rewrite required.
If it runs on KIE Server, it runs on Aletyx. Same APIs. Same behavior. Modern stack. Native AI.
No rewrite required
Drop-in upgrade
From $25,000 a year
The vast majority of production workflows run on KIE Server. The community moved on.
KIE Server never moved to Apache. The last community release is more than three years old. IBM BAMOE v8 is end of life and v9 drops KIE Server. Red Hat PAM is end of life. You can’t stay, and you can’t rewrite. Aletyx helps you modernize while preserving your existing workloads.
Moving to Kogito isn’t a migration. It’s a rewrite.
KIE Server and Kogito are different systems: different execution model, persistence, deployment and APIs. Every BPMN asset, integration and human task has to be revisited.
For hundreds of process definitions across critical systems, that is a multi-quarter program with high delivery risk and no new business value. You don’t rewrite core systems because a new version exists. Continuity is the requirement.
Your KIE Server, on a modern stack.
We brought KIE Server back on a modern JVM, modern frameworks and a modern application server, with complete behavioral compatibility for your existing workloads.
Built and maintained by the team that led jBPM and KIE Server at Red Hat and IBM.
Your processes, integrations and behavior stay the same. Your stack is modern, patched and ready for AI agents.
What changes, and what doesn’t.
Java 21, Jakarta EE 10, Spring Boot 4, EAP 8
No more legacy application servers, no more outdated dependencies. A production runtime built for today’s enterprise infrastructure.
AI agents trigger your processes over MCP
The same AI capabilities as the Enterprise Build of Kogito, on KIE Server: MCP process triggering, an AI agent node, direct LLM invocation. Without rewriting a single workflow.
CVE patches and remediation guidance
CVE monitoring and patching on a predictable cadence. The last community release carries years of unpatched vulnerabilities. Aletyx eliminates that exposure.
No forced upgrades, no breaking changes
Signed builds. Controlled dependency baselines. Predictable release cycles you can plan around.
Bring AI agents to your KIE Server. No rewrite required.
You don’t need a new platform to put AI agents to work. The same AI capabilities as the Enterprise Build of Kogito run on KIE Server today.
MCP process triggering
AI agents discover and trigger your existing processes over MCP.
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.
When the Enterprise Build is the right call
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 modernizes without changing the architecture.
You need AI agents in your existing workflows
AI agents on KIE Server, over MCP, same as Kogito.
You face unpatched CVEs on aging runtimes
Active security patching. Modern dependencies. Enterprise SLAs.
Your vendor’s support exists only on paper
Direct access to the team that led KIE Server.
ScenarioYou run RHPAM, BAMOE v8, jBPM, or KIE Server in production
Why AletyxDrop-in replacement. Modern stack. No rewrite.
ScenarioYou’ve been told to “migrate to Kogito”
Why AletyxThat’s a rewrite. Aletyx modernizes without changing the architecture.
ScenarioYou need AI agents in your existing workflows
Why AletyxAI agents on KIE Server, over MCP, same as Kogito.
ScenarioYou face unpatched CVEs on aging runtimes
Why AletyxActive security patching. Modern dependencies. Enterprise SLAs.
ScenarioYour vendor’s support exists only on paper
Why AletyxDirect access to the team that led KIE Server.
No one else keeps KIE Server running.
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 4, 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
Community support, no contractual patch SLA
Support
Direct access to core engineers
Tiered L1→L3
Unavailable
Volunteer-based, no SLA
Pricing
From $25,000 a year
Per-core, yearly increases
N/A
Free (high internal cost)
Consideration
KIE Server support
AletyxFully restored and modernized
IBM (BAMOE)EOL in v8, removed in v9
Red Hat (PAM)End of life
Apache CommunityNot transferred to Apache
Consideration
Migration approach
AletyxDrop-in replacement
IBM (BAMOE)Rewrite to v9
Red Hat (PAM)N/A
Apache CommunityRewrite to Kogito
Consideration
Runtime stack
AletyxJava 21, Jakarta EE 10, Spring Boot 4, EAP 8.x
IBM (BAMOE)Frozen at outdated stack
Red Hat (PAM)Frozen
Apache CommunityNo releases
Consideration
AI capabilities
AletyxNative: MCP, AI agent node, LLM invocation
IBM (BAMOE)None on KIE Server
Red Hat (PAM)None
Apache CommunityNone
Consideration
Security
AletyxActive CVE patching
IBM (BAMOE)v8 EOL priority
Red Hat (PAM)End of life
Apache CommunityCommunity support, no contractual patch SLA
Consideration
Support
AletyxDirect access to core engineers
IBM (BAMOE)Tiered L1→L3
Red Hat (PAM)Unavailable
Apache CommunityVolunteer-based, no SLA
Consideration
Pricing
AletyxFrom $25,000 a year
IBM (BAMOE)Per-core, yearly increases
Red Hat (PAM)N/A
Apache CommunityFree (high internal cost)
If it works, modernize it. Don’t rewrite it.
If your KIE Server workloads run well today, you don’t need Kogito. The Enterprise Build of KIE Server is a modern, patched, AI-ready runtime and a long-term answer. Build new workflows on the Enterprise Build of Kogito. Keep what already works. Never be forced into a rewrite you don’t need.
Before you migrate
What architects ask before they migrate.
01Is this a drop-in replacement for my existing RHPAM, BAMOE v8, jBPM v7, or KIE Server deployment?
Yes. Your existing KJARs deploy directly onto the Enterprise Build with the same APIs, execution semantics and process behavior. Your integrations stay intact.
02What stack does it run on?
Java 21. Jakarta EE 10. Spring Boot 4. EAP 8.x and WildFly 35+. Kubernetes-ready. No more legacy application servers or outdated dependencies.
03Why 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.
04What happened to KIE Server in the open-source ecosystem?
KIE Server was never transferred to Apache. The last community release is more than three years old. The community focused on Kogito instead, which is a different architecture. Aletyx restored KIE Server as a fully supported, modernized product.
05What 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. The process around them stays in control.
06Can 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. Aletyx Platform is not a Business Central replacement. It is a different approach that delivers some of the same benefits with a different model.
07What 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 edition. See the pricing page for details.
08How 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 trial.
Free 60-day trial
Modernize KIE Server. Keep your processes. Add AI agents.
Be the team that kept its processes running, dropped the risk, and put AI agents to work, without a rewrite.
No credit card. Full access. Direct support.