> ## 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.

# Introduction

> Automated code modernization for your repositories

export const ProductName = "The Morph Platform";

export const productName = "the Morph Platform";

{ProductName} automates the migration of codebases from one technology stack to another. Whether you're upgrading Python 2 to Python 3, translating Ada to C++, or migrating a legacy framework to a modern one, {productName} handles the heavy lifting.

## How It Works

{ProductName} connects to your repositories and modernizes them according to your goals. A project can include one or more repositories, each with a defined role in the migration. The process is designed to be transparent and controllable:

1. **You define the goal** — Describe what you want: "Translate from Ada to C++" or "Upgrade to Python 3.12"
2. **You set up the build environment** — Configure how your project builds, runs, and tests
3. **{ProductName} understands your code** — We analyze your repositories and document their architecture
4. **You approve the plan** — When your Project Spec is ready, {productName} opens [**Project Knowledge**](/customization/project-knowledge) automatically the first time (the Roadmap drawer with your spec, chat, and related context) so you can review and approve it using chat before any code is generated
5. **{ProductName} executes in milestones** — The migration happens in logical chunks, each delivered as a Pull Request for your review
6. **You control the merge** — Every change goes through your normal code review process

## Why This Approach

### You Stay in Control

Automated migrations can be risky. {ProductName} is designed so you never lose control:

* **Nothing changes without your approval** — The Project Spec must be explicitly approved before migration begins
* **Progressive delivery** — Changes come in milestones, not one massive PR
* **Standard GitHub workflow** — Every milestone produces a PR you can review, comment on, and merge like any other

### The AI Understands Context

Before generating any code, {productName} builds a comprehensive understanding of your repositories:

* What technologies and frameworks are in use
* How components connect to each other
* Architectural patterns and conventions

This context ensures the migrated code respects the intent and structure of your original application.

### Multi-Repository Support

Real-world modernizations often span multiple repositories. {ProductName} supports multi-repo projects where each repository has a defined role:

* **Modified** — An existing repository that will be transformed
* **New** — A new repository created as part of the migration
* **Reference Only** — A repository used for context but not modified
* **One-to-One Migration** — Direct migration from one repository to another

Each project has a [lifecycle configuration](/setup/build-environment/lifecycle-setup) — scripts, environment variables, and a lifecycle document that define how the application builds, runs, and tests. For both cloud projects and projects on a [V2 self-hosted daemon](/setup/build-environment/self-hosted-daemon), these are auto-discovered from the codebase and editable in the UI.

### Customizable to Your Standards

Every team has coding standards. {ProductName} lets you define **Rules** that encode your preferences:

* "Always use dependency injection for database connections"
* "Follow our naming convention for React components"
* "Use our internal logging library instead of console.log"

These rules apply across all milestones, ensuring consistent output that matches your team's expectations.

## What You Can Migrate

{ProductName} handles a wide range of modernization scenarios:

| Scenario                       | Examples                              |
| ------------------------------ | ------------------------------------- |
| **Language upgrades**          | Python 2 → Python 3, Java 8 → Java 21 |
| **Language translations**      | Ada → C++, COBOL → Java               |
| **Framework migrations**       | AngularJS → React, Express → FastAPI  |
| **Architecture modernization** | Monolith → Microservices              |

## Next Steps

Ready to start? Head to the [Quickstart](/quickstart) guide to create your first migration project.