DMS Software Reengineering Toolkit vs OpenRewrite
DMS Software Reengineering Toolkit
semdesigns.comOpenRewrite
openrewrite.orgSide by side
| Figure | DMS Software Reengineering Toolkit | OpenRewrite |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Code Refactoring Tools | 7.4 (#16) | 8.2 (#6) |
| Company | Semantic Designs, Inc. is headquartered in Austin, Texas, and its company history says it was established in October 1995. | Moderne's press kit lists Miami, Florida as its headquarters and says OpenRewrite originated as a project Jonathan Schneider started at Netflix. |
| Licensing | The maker says royalty licensing with significant discounts can allow redistribution of a DMS-based tool. | The core framework is Apache licensed, while some recipe modules use the Moderne Source Available License or a proprietary license. |
| Purpose | DMS provides customizable infrastructure for automating source program analysis, source code modification, and software generation. | OpenRewrite is an open-source automated refactoring ecosystem for eliminating technical debt in code repositories. |
| Support | Semantic Designs says it offers DMS training, expert advice, and implementation support as desired by the customer. | The OpenRewrite documentation invites users to ask questions in Slack or Discord and lists [email protected]. |
Plans
DMS Software Reengineering Toolkit
- DMS Software Reengineering ToolkitPriced on request
In their own words
DMS Software Reengineering Toolkit
DMS Software Reengineering Toolkit has no write-up on Specifiction yet; its figures are above.
OpenRewrite
OpenRewrite is an open-source ecosystem for automated code refactoring, aimed at updating code and reducing technical debt. It represents code as Lossless Semantic Trees, applies transformations, and prints the result back into source code for review. Its recipes cover framework migrations, security fixes, and style consistency, and can be written in YAML, Refaster templates, or Java. Maven and Gradle plugins run recipes locally as part of builds, one repository at a time. The Maven plugin offers a dry run that reports potential changes and writes diff files; recipes run only when explicitly activated by name. Documented support includes Java, Kotlin, and Groovy, plus formats such as HCL, JSON, Properties, Protobuf, TOML, XML, and YAML. Framework coverage includes Spring, Quarkus, and Micronaut. The recipe index lists 4,183 recipes across modules. Core and language libraries use Apache License 2.0, but some recipes have other licensing terms. Core is free; some artifacts require authenticated repository access, and some recipes require a Moderne subscription.