Coming soon · 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 — dependency and config rewriting, automated compile- and runtime-error repair, and a deploy-ready package at the end. No COBOL, no Mainframe, no manual line-by-line rewriting.

Notify me See how it works
4
real legacy codebases migrated end-to-end
6/7/8 → 17
Java version jump
2
migration paths — Spring Boot & WAR/Tomcat
What it does

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.

🧭
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.
🛠️
Dependency & config rewriting
A growing, curated library of rewriters fixes the version-skew and breaking-change traps that JDK 17 and Spring Boot 3 introduce — not generic find-and-replace.
🤖
Autonomous AI-Fix-Loop
Compile errors and runtime failures are diagnosed and repaired automatically, with configurable limits against infinite loops.
🧑‍💻
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.
How it works

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 rewrites dependencies, plugin versions and configuration 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)
 
$
Pricing

Standalone module, coming soon

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

Molt
Standalone module
Pricing TBD
Not yet in Beta — get in touch to be notified when it opens up.
  • ✓ Java 6/7/8 → Java 17 / Spring Boot 3
  • ✓ Automatic Spring Boot or WAR/Tomcat path
  • ✓ Autonomous AI-Fix-Loop for compile & runtime errors
  • ✓ Packaging-aware Docker Compose output
  • ✓ Human escalation when automation can't safely proceed
Notify me

Ready to see your
Java in Java 17?

Molt isn't in Beta yet. Write to us with your use case and we'll let you know as soon as it opens up.

Notify me
Questions? Write to hello@ilumeny.com