> ## Documentation Index
> Fetch the complete documentation index at: https://docs.modelcode.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Supported Architectures
> The project types, languages, and application shapes that Morph currently supports
export const ProductName = "The Morph Platform";
export const productName = "the Morph Platform";
{ProductName} keeps expanding the kinds of modernization projects it can take on. This page describes what is supported **today** so you can pick projects that will produce the best results, and know what to expect before you start.
This list reflects the current state of the platform. We are actively adding support for more languages, frameworks, and application types — check back regularly, and reach out to [support@modelcode.ai](mailto:support@modelcode.ai) if you have a use case you'd like to see covered.
***
## At a Glance
{ProductName} supports **backend, full-stack, and architectural modernization projects**, with capabilities expanding through ModelDaemon.
| Dimension | What's supported today |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project shape | One or many source repositories → one or many target repositories (1:1 or many-to-many) |
| Transformation type | Language-to-language translation or framework upgrades, architectural transformations |
| Backend | All common backend languages and frameworks (see [Supported Languages](#supported-languages) below) |
| Frontend | All common frontend languages and frameworks (language-to-language translation and framework/runtime migrations) |
| Application shape | RESTful services, CLI tools, and full-stack applications |
| Runtime environment | **Linux** and **Windows** (amd64 or arm64) on [Modelcode Hosted](/setup/build-environment/modelcode-hosted) and [self-hosted ModelDaemon](/setup/build-environment/self-hosted-daemon); **macOS** (Apple Silicon or Intel) as a self-hosted daemon host |
| Dev environment | Assisted setup via lifecycle discovery (developer input may be required) |
| Testing | CLI, API, and UI-based validation supported |
***
## Project Shape
{ProductName} supports both **single-repo and multi-repo modernization projects**.
### One-to-One (1:1)
* One source repository → one target repository
* Can be in-place migration or full rewrite
### Multi-Repo (Many-to-Many)
* Multiple source repositories → multiple target repositories
* Supports:
* Monolith → microservices decomposition
* Cross-repo transformations
* Service extraction and restructuring
***
## Transformation Types
{ProductName} supports multiple categories of transformation depending on the scope of your system.
***
### 1. Backend Modernization (Core Capability)
Backend migration projects with the following attributes:
* Many-to-many or one-to-one repository transformations
* Language-to-language translation or framework upgrades
* Target applications may be RESTful APIs, CLI tools, or service-oriented systems
* Supports monolith → microservices transformations
* macOS and POSIX-compatible Linux distributions
* Windows 10/11 and windows server 2019+
Morph capabilities:
* Detects dependencies and architecture across repositories
* Generates and executes structured migration milestones
* Assists in identifying missing metadata and configuration
* Supports build, run, and test workflows within the target environment
***
### 2. Full-Stack Modernization
Projects that include both backend and frontend components:
* Backend and frontend systems (e.g., PHP + Twig → Java/Spring + React)
* Frontend framework migrations (e.g., Angular → React, Twig → React)
* Multi-repo or mono-repo architectures supported
* Requires lifecycle configuration for frontend build and test processes
Morph capabilities:
* Understands cross-layer dependencies between backend services and UI layers
* Generates frontend transformations aligned with backend changes
* Supports validation through build and test workflows where available
* Assists with configuration of frontend tooling and environments
***
### 3. Architecture & Refactoring Transformations
Projects focused on improving system structure and maintainability:
* Monolith → microservices decomposition
* Service extraction, consolidation, or restructuring
* Codebase refactoring without full language migration
* Dependency standardization and modernization
Morph capabilities:
* Builds architectural understanding across repositories
* Applies transformations incrementally through milestones
* Maintains compatibility with existing system behavior
* Enables iterative modernization without requiring full rewrites
***
## Supported Languages
{ProductName} supports modernization projects whose source and/or target is one of the following languages:
## For each of the above, all common frameworks and micro-frameworks (web, RPC, CLI, background worker, etc.) are in scope.
## Application Shape
The target application can be:
* A **RESTful service** (HTTP API, gRPC gateways, etc.)
* A **command-line (CLI)** tool
* A **full-stack application** (backend + frontend)
{ProductName} validates migrations by executing build, test, and runtime workflows.
* CLI and API-based validation are fully supported
* UI-based validation is supported where build/test workflows are available
***
## Environment & Execution Model
{ProductName} operates directly within your application environment via ModelDaemon.
* With ModelDaemon, execution environments are more portable and less dependent on fixed filesystem or container assumptions
* Lifecycle discovery and guided setup assist in configuring build and runtime environments
* In complex or highly customized systems, developer input may still be required
For best results:
* The application should build and run in the target environment
* Dependencies (services, APIs, packages) should be accessible
* Testable workflows (CLI, API, or UI-based) should be available
***
## What's Not Fully Supported Yet
{ProductName} is built for **backend services, CLIs, and full-stack web apps**. The following kinds of projects are **not supported as modernization migrations today**:
* **Native mobile applications** — iOS, Android, and other mobile-first stacks (device SDKs, mobile UI frameworks, app-store packaging workflows)
* **Desktop GUI applications** — thick-client or native desktop apps whose primary artifact is a desktop installable (as opposed to a service or web app you run locally)
* **Plugins and extensions** — IDE plugins, browser extensions, editor extensions, and other code that runs inside a host application rather than as a standalone service or site
If your project mixes supported and unsupported surfaces (for example, a web API plus a mobile client), focus the migration on the supported components or contact [support@modelcode.ai](mailto:support@modelcode.ai) before committing. For any complex requirements, validate setup during project initialization.
***
## Evaluation & Performance
Morph performance is continuously evaluated across single-repo and multi-repo modernization scenarios.
* Supports both single-repo and multi-repo transformations
* Designed to achieve high test pass rates and successful milestone completion
* Outcomes vary depending on system complexity, dependency availability, and test coverage
***
## Checking Whether Your Project Is Supported
When you create a project, {productName} analyzes your source repository and flags whether it matches supported criteria.
If it doesn't, you'll see guidance in the Project Spec explaining what needs to be adjusted.
See [Project Knowledge](/setup/project-knowledge) for more.
***
## Still Not Sure?
If you're unsure whether your project qualifies, or you have a modernization in mind that doesn't quite fit, reach out to [support@modelcode.ai](mailto:support@modelcode.ai).