What's New

​

May 12, 2026

​

Multi-repo support is generally available

The Morph Platform now supports many-to-many modernization projects across multiple source repositories and multiple target repositories. This is especially important for enterprise backend modernization projects where the application is spread across services, shared libraries, APIs, generated clients, and separate target applications. What changed

• The Morph Platform can support many source repos to many target repos.
• Modernization projects can include multiple related codebases.
• Backend modernization workflows can better reflect real enterprise application structures.

Why it matters Most enterprise systems do not live in one clean repository. Multi-repo support allows the Morph Platform to work across the actual shape of customer software instead of forcing teams to simplify their architecture before starting a modernization project.

---

​

ModelDaemon

ModelDaemon introduces a more secure and scalable execution model for customer environments. MD runs inside the customer’s infrastructure using outbound-only connectivity. the Morph Platform continues to orchestrate the work, while execution happens closer to the customer’s code, dependencies, tools, and internal systems. What changed

• ModelDaemon runs inside the customer environment.
• Connectivity is outbound-only.
• The Morph Platform can execute work closer to private code, private dependencies, and internal infrastructure.
• The daemon now supports smarter execution through the morph-agent at the edge.

Why it matters Customers do not need to expose inbound access or move private code and dependencies outside their environment. This makes the Morph Platform more practical for enterprise and regulated deployments.

---

​

Smarter local execution with morph-agent

With ModelDaemon, the daemon is no longer just a remote command runner. The morph-agent can run full LLM-driven and it allows the agent to reason through dependencies, make code changes, run commands, execute tests, and handle workflows directly inside the customer’s infrastructure. What changed

• The daemon can run LLM-driven execution loops locally.
• Code changes, dependency handling, and workflow execution can happen inside the customer environment.
• The Morph Platform orchestration coordinates the work while the daemon performs richer local execution.

Why it matters Enterprise projects often depend on internal services, private packages, local tooling, and environment-specific setup. Smarter local execution helps the Morph Platform operate in those environments with fewer assumptions.

---

​

Distributed and scalable execution architecture

ModelDaemon also moves the Morph Platform toward a more distributed, async, event-driven execution architecture. This replaces the older tightly coupled Docker-control model with a more flexible execution system based on parallel workspaces and event-driven coordination. What changed

• Execution is now more async and event-driven.
• Parallel workspaces improve flexibility and scalability.
• The Morph Platform is less dependent on tightly coupled Docker control paths.

Why it matters Large modernization projects need execution infrastructure that can handle long-running work, retries, partial progress, and customer-specific environments. This architecture gives the Morph Platform a stronger foundation for more complex projects.

---

​

Improved ModelDaemon setup experience

The Morph Platform now provides a more continuous setup and execution flow for ModelDaemon projects. Instead of requiring users to complete a rigid multi-step configuration process, the Morph Platform can analyze the repository, detect dependencies, identify missing metadata, and provide clearer next-step guidance during execution. What changed

• Repo analysis is more integrated into setup.
• Dependency detection is clearer.
• Missing metadata is surfaced earlier.
• Execution progress is streamed with better guidance.

Why it matters Modernization often starts with the hardest question: “How does this application actually run?” These improvements help the Morph Platform guide users through setup instead of requiring perfect configuration up front.

---

​

Robust functional testing

The Morph Platform can validate parts of your application, such as APIs and services, and continue making progress even when some dependencies are missing. What changed

• Missing dependencies no longer have to block all progress.
• The Morph Platform can continue useful work even when the full environment is incomplete.

Why it matters Enterprise environments are rarely perfect on the first run. Partial execution helps teams avoid all-or-nothing failures and continue moving forward while missing dependencies are identified and resolved.

---

​

Clearer errors and chat driven resolution

The Morph Platform now provides clearer explanations for configuration and lifecycle command errors. For common setup issues, the Morph Platform can suggest a fix, apply it, and retry execution through chat. What changed

• Configuration errors are easier to understand.
• Lifecycle command failures include clearer explanations.
• Common issues can be resolved with the Morph agent
• The Morph Platform will automatically retry execution after applying a fix.

Why it matters Setup issues will still happen, especially in large enterprise applications. The goal is to make those issues less manual, less mysterious, and less likely to stop a project.

---

​

Frontend modernization support

The Morph Platform now includes early support for frontend modernization workflows. Why it matters Many modernization projects are not purely backend. They include server-rendered templates, embedded frontend logic, and older UI frameworks that need to be separated from backend business logic. This release is the first step toward broader frontend stack support.

---

​

Azure DevOps support

The Morph Platform now supports Azure DevOps. This expands the environments where customers can connect the Morph Platform to existing source control and delivery workflows. What changed

• Added Azure DevOps repository support.
• Enabled the Morph Platform project setup for Azure DevOps-based customers.
• Completed support for HealthEquity and RadarHealth workflows.

Why it matters Many enterprise teams use Azure DevOps as their primary development platform. This update removes friction for customers who want to use the Morph Platform without changing their existing source control workflow.

---