Skip to content

Frequently asked questions

Why use a monorepo for multiple applications?

A monorepo keeps related applications and packages in one repository. In our foundation, Turborepo and pnpm help coordinate tasks and dependencies across frontends, APIs and shared code.

A customer portal and a backoffice can share models or interface components while keeping their own screens and responsibilities. Keeping those contracts together makes changes spanning several parts of a product easier to review.

Sharing a repository does not mean deploying everything together or sharing customer data. Deployments, access and storage need their own decisions. We use this structure when coordination adds more value than maintaining separate repositories.

More questions

Reading guide · Markdown
Why use a monorepo for multiple applications?