Konveyor
Konveyor: assess the estate, then migrate it.
An open-source toolkit that scans application portfolios for migration work. Useful for the inventory. It does not do the migration for you.
The short answer
Konveyor is an open-source project that helps organizations assess and migrate application portfolios toward Kubernetes and newer platforms. It analyzes source code and binaries against rule sets, reports what must change and tracks effort across many applications. It finds the work. Engineers and other tools still have to do it.
Definition
What is Konveyor?
Konveyor is a community project for application modernization. Its core is a static analysis engine with rule sets for common migration paths, such as moving a Java EE application off a proprietary application server or preparing an application to run in containers. Red Hat ships a supported distribution of the same technology as the Migration Toolkit for Applications.
The project has two parts that matter to a buyer. The analyzer scans one application and lists the issues it finds. The hub collects those results for a whole portfolio so a team can see which applications are easy, which are hard and which should be left alone.
Output
What does a Konveyor analysis report?
For each application the analysis produces a list of findings, each tied to a file and line, with a rough effort rating. Typical findings fall into a few groups.
- Use of server-specific APIs, such as WebLogic or WebSphere classes and JNDI lookups.
- Dependencies on libraries that have no supported release or no Jakarta equivalent.
- Configuration that assumes a particular server, such as deployment descriptors and security realms.
- Code patterns that conflict with containers, such as writing to local disk or hard-coded host names.
- Technologies flagged for replacement, such as EJB 2 or old XML-based configuration.
AI
Where does AI assistance fit in Konveyor?
The project has added AI-assisted fixing on top of analysis: the analysis finds an issue, a language model proposes a code change for it, and a developer reviews the proposal. That is the same split Ace8 uses everywhere. The tool drafts. A person decides.
It helps most on repetitive findings that follow a pattern. It helps least on findings that depend on how your server is configured at runtime, because the model never sees that configuration. Treat every proposed change as untrusted until the build and the tests pass. See AI-assisted modernization for how we gate model output.
Comparison
Konveyor, OpenRewrite and AWS Transform: what is each for?
They are not rivals. Konveyor answers what to change. A tool such as OpenRewrite does the mechanical change. Neither replaces the assessment, which adds test coverage, licence dates and business priority.
| Tool | Main job | Output | Still needs |
|---|---|---|---|
| Konveyor | Assess a portfolio, find migration work | Findings per application, effort ratings | Engineers to make the changes |
| OpenRewrite | Apply deterministic code rewrites | Changed source code | Review of every diff, tests |
| AWS Transform | Automate some upgrade tasks on AWS | Proposed code changes | Review, tests, an AWS account |
Judgment
When is Konveyor the right starting point?
It is a poor fit for a single application with a clear path. There, a direct run of a recipe and a manual review is quicker.
- You have dozens or hundreds of applications and need a first-pass inventory fast.
- The target is Kubernetes or a container platform, which is what its rules favor.
- You want an open-source tool with no per-application licence.
- You have an engineer who can tune rules and read the output.
Method
How does Ace8 use it?
- 1
Scan the portfolio
Run the analyzer across the applications in scope and collect the results in one place.
- 2
Filter the noise
An engineer removes findings that do not apply and adds checks for patterns the rules miss.
- 3
Add what the scan cannot see
Test coverage, licence renewal dates, data dependencies and who owns each application.
- 4
Rank and plan
Group applications into waves. Each wave has a tool, a reviewer and a rollback.
Evidence
What we have measured
We have not yet published a Konveyor run on a sample codebase. When we do, it will sit beside our OpenRewrite and AWS Transform runs on the same application, and we will link it from here. Until then this page makes no claims about speed or accuracy.
Assessing a portfolio of applications for migration to Kubernetes and newer platforms. It scans code and binaries against rules, lists the changes needed and tracks effort across many applications.
They share technology. Konveyor is the open-source community project. The Migration Toolkit for Applications is Red Hat's supported distribution of it.
No. It finds and rates the work. Its AI-assisted features can propose fixes, but a developer must review them and the tests must pass.
The open-source project has no licence fee. You still pay for the engineers who tune the rules, read the results and make the changes.
Usually both, for different jobs. Konveyor inventories the estate. OpenRewrite applies repeatable code changes once you know what to change.
Know the cost before anything moves.
A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.
Book a Fixed-Price AssessmentGet in touch
Talk to a modernization engineer
Tell us what you run today. An engineer, not a sales script, replies within one business day.