A monorepo is a single version-control repository that holds the code for many projects or services, often owned by different teams. Instead of giving each service its own repository, everything lives in one place, with shared tooling and a single history. A monorepo is a way of organizing code, not a statement about architecture, so it can contain many independently deployed services and is not the same as a monolith.

Supporters point to easier code sharing, simpler cross-project changes, consistent tooling and one place to see how everything fits together. A change that touches several projects can be made and reviewed together.

The approach has costs. As the repository grows, builds and tests can slow down unless the tooling can work out what a change affects and reuse earlier results. Access control, code ownership and repository performance need deliberate attention, and a broken change in shared code can affect many teams at once.

Whether it suits a team depends on its size, tooling and how closely its projects are connected. Teams considering it should check whether they can invest in build caching, dependency analysis and clear ownership rules, and should measure outcomes such as review time and build time rather than assume benefits.