The open-source engine for automated code change.

OpenRewrite is the open-source refactoring framework and recipe ecosystem: the visitors, the Lossless Semantic Tree, and the recipe catalog. Moderne is the commercial platform that runs OpenRewrite across enterprise codebases. The same recipes that run on a single repository with OpenRewrite run across your entire codebase on Moderne, with coordinated PRs, full audit trail, and impact analysis.

On its own, OpenRewrite runs recipes one repository at a time. Scaling means running recipes across thousands of repositories simultaneously, opening coordinated pull requests, tracking every change in an audit trail, and previewing impact before changes ship. Moderne is the platform built for this: orchestration, multi-repo PR management, dashboards, and recipe execution at codebase-wide scope.

Teams automate large-scale modernization across the whole codebase: Java and language version upgrades, Spring Boot and framework migrations, CVE and security remediation, dependency management, and internal standardization, all executed through OpenRewrite recipes and delivered as reviewable pull requests.

Yes. Recipes operate on the Lossless Semantic Tree, so every transformation is deterministic and semantically accurate rather than regex or AI guesswork. Every change is delivered as a clean, reviewable pull request so teams validate before merging, using your team’s normal review workflow.

When a new CVE is disclosed, Moderne applies the relevant OpenRewrite fix recipe across your entire codebase in a single campaign. Instead of triaging and patching repositories one by one, security and engineering teams see exposure across every repo and push remediation pull requests organization-wide. What used to take months takes days.

Work that traditionally takes months of manual engineering can land in days or weeks. Because recipes run across thousands of repositories in parallel and deliver changes as ready-to-review PRs, teams spend their time reviewing and merging rather than writing migration scripts or hunting deprecated patterns one file at a time.

Yes. Custom recipe authoring is a first-class capability. Teams encode internal standards, migration patterns, and modernization workflows as custom recipes, then run them at the same scale as the thousands of community recipes across the entire repository estate. The Moderne CLI supports custom recipe development locally and against the platform.

Native integration with GitHub, GitLab, and Bitbucket. Moderne opens PRs in your existing repositories using your team’s normal review workflow, and CI integration is standard. Recipes can run in your pipelines, or campaigns can be triggered from the platform with results landing as PRs ready for review.

No. Many enterprise teams come to Moderne without prior OpenRewrite experience. The community recipe catalog covers the most common modernization, migration, and security work, and the platform previews changes before any ship. OpenRewrite expertise helps for custom recipe authoring but is not required to deliver migrations or remediation campaigns.

Agents reach for recipes the way they reach for any tool, through the Moderne MCP server. Instead of hand-editing files and hoping, an agent calls a deterministic recipe that makes the same correct, type-aware change every time, and when no recipe exists yet, it can author a new one. Trigrep gives agents structured search and Prethink gives them codebase context, so the agent plans while OpenRewrite does the structural work. See the agent tools.