Beta · Standalone · No Mainframe required

Legacy Java in,
Spring Boot 3 out

Molt autonomously migrates legacy Java 6/7/8 applications to Java 17 and Spring Boot 3 — and the integrations every real-world legacy app brings with it: Apache Camel, OAuth2/Spring Security, Kafka, Spring Batch, REST/Web. 47+ curated transformers rewrite dependencies, config and integration code, backed by an automated compile- and runtime-error repair loop. The goal isn't a codebase that compiles — it's an application that's immediately runnable again.

Join the Beta See how it works
4
real legacy codebases migrated end-to-end
6/7/8 → 17
Java version jump
47+
curated transformers — Camel, OAuth2, Kafka, Batch, REST/Web

One upload, a working Java 17 app back

Molt is built for ordinary legacy Java applications — Spring MVC, Spring Boot, XML-bean-configured WAR projects — not Mainframe code. It runs the whole upgrade, not just a dependency bump.

🔌
The integrations migrate too, not just the JDK
Almost every legacy app brings its own mix — simple Web MVC, REST/Web services, Spring Batch, nearly always OAuth2, sometimes Kafka or Apache Camel, often several combined. Molt targets the most common and consequential of these, not just the Java version bump.
🧭
Two migration paths, chosen automatically
Annotation-driven codebases get a Spring Boot bootstrap; XML-bean-heavy legacy WARs get a WAR/Tomcat path. Molt detects which one your project needs.
🛠️
47+ transformers, and growing
A curated, continuously expanded library of rewriters fixes the version-skew and breaking-change traps that JDK 17, Spring Boot 3, and their Camel/OAuth2/Kafka/Batch/REST integrations introduce — not generic find-and-replace, and made more granular with every release.
🤖
Autonomous AI-Fix-Loop
Compile errors and runtime failures are diagnosed and repaired automatically, with configurable limits against infinite loops.
✅
Immediately runnable, not just compiling
A green build isn't the finish line. Molt's target is an application that starts up and serves traffic right after migration — verified by actually running it, not just compiling it.
🧑‍💻
Human escalation by design
100% automation isn't the goal. When the pipeline can't safely resolve something, it stops and flags it clearly — instead of guessing.

From ZIP upload
to a deployed Java 17 app

01

Upload your Java source archive

Zip your Maven-based Java 6/7/8 project — Spring MVC, Spring Boot, or a plain WAR. No code changes up front, no agents to install.

02

Ingest & transform

Molt parses your build, detects the right migration path, and runs 47+ transformers to rewrite dependencies, plugin versions, configuration — and any Camel, OAuth2, Kafka, Spring Batch or REST/Web integrations — for Java 17 and Spring Boot 3.

03

Runtime-tested, not just compiled

The migrated app is actually built, deployed and started. The AI-Fix-Loop repairs what breaks along the way — compile errors and runtime exceptions alike.

04

Download your migrated package

A Java 17 / Spring Boot 3 application plus a packaging-aware, generated docker-compose.yaml — ready to deploy.

molt — migration run
$ curl -X POST /api/jobs -F "file=@legacy-app.zip"
 
→ INGEST... buildSystem=MAVEN, javaVersion=1.8, springVersion=Spring 4.3.7
→ TRANSFORM... rewriting dependencies, plugin versions, config
→ RUNTIME_TEST... building, deploying, verifying startup
→ AI-Fix-Loop... 2 issues found, 2 repaired automatically
 
✓ Migration complete — Java 17 / Spring Boot 3, packaged and ready
Docker Compose: generated, packaging-aware (Boot or WAR/Tomcat)
 
$

Standalone module, now in Beta

No Mainframe Discovery required — Molt works on its own, directly against your Java codebase.

Molt
Standalone module
Pricing on request
Get in touch for current Beta conditions — or start with a fixed-scope Java Modernisation Pilot.
  • ✓ Java 6/7/8 → Java 17 / Spring Boot 3
  • ✓ Camel, OAuth2, Kafka, Spring Batch & REST/Web migrated too
  • ✓ 47+ curated transformers, continuously expanded
  • ✓ Automatic Spring Boot or WAR/Tomcat path
  • ✓ Autonomous AI-Fix-Loop for compile & runtime errors
  • ✓ Immediately runnable, not just compiling
  • ✓ Packaging-aware Docker Compose output
  • ✓ Human escalation when automation can't safely proceed
Join the Beta

Ready to see your
Java in Java 17?

Molt is currently in Beta. Write to us with your use case — or let us upgrade a module of your choice in a Java Modernisation Pilot.

Join the Beta
Questions? Write to hello@ilumeny.com