--- title: When is a Monorepo Worth It? (And Why It’s Not Always a... description: A developer shares their experience deciding whether to adopt a monorepo for a project with two separate but highly similar web applications. The post outlines... canonical: https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: When is a Monorepo Worth It? (And Why It’s Not Always a Good Idea) | daily.dev og:description: A developer shares their experience deciding whether to adopt a monorepo for a project with two separate but highly similar web applications. The post outlines... og:url: https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd og:image: https://api.daily.dev/og/posts/gr24SyZQd.png og:image:alt: When is a Monorepo Worth It? (And Why It’s Not Always a Good Idea) og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # When is a Monorepo Worth It? (And Why It’s Not Always a Good Idea) **[Medium](https://daily.dev/sources/medium_js)** · 3 min read · 2 upvotes · 1 comments ## Summary A developer shares their experience deciding whether to adopt a monorepo for a project with two separate but highly similar web applications. The post outlines when a monorepo makes sense — shared components, unified TypeScript types, same team across multiple products — and when to avoid it, such as during an MVP phase, with independent teams, or when mixing radically different tech stacks. The conclusion is pragmatic: don't force architectural decisions before they're needed, but recognize the signals when they appear. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When should I switch a project to a monorepo instead of using separate repositories? A monorepo makes sense when code duplication starts seriously slowing development, specifically when apps share the same design components and authentication logic, need unified TypeScript type contracts across frontend and backend so API changes flag breaking changes at compile time, or are maintained by the same team who wants to avoid opening multiple pull requests across repos for one feature. _daily.dev surfaces perspectives like this for developers weighing monorepo tradeoffs before restructuring a project._ ### When should I avoid using a monorepo for my project? Avoid a monorepo when mixing distinct technologies and lifecycles, such as backend and frontend at scale, since forcing radically different architectures into one repository creates overcomplexity. It is also a poor fit when independent teams own separate applications and want isolated deployment flows, permissions, or Git history, or when a product is still in an early MVP discovery phase needing raw delivery speed. _developers sorting monorepo tradeoffs against MVP speed often compare notes like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 0 upvotes > This is a good rule of thumb: let shared code and team workflow pull you toward a monorepo instead of forcing one too early. For an MVP, separate repos can keep things simple until the duplication starts to hurt. ## Similar posts on daily.dev - [Monorepo vs. Polyrepo \(Multi-repo\): What’s the Difference?](https://daily.dev/posts/monorepo-vs-polyrepo-multi-repo-what-s-the-difference--ezmxleoxf) · Spacelift · 0 upvotes · 0 comments - [A Monorepo Is NOT a Monolith](https://daily.dev/posts/a-monorepo-is-not-a-monolith-bl4utxeac) · Nx · 98 upvotes · 8 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#general-programming](https://daily.dev/tags/general-programming), [#architecture](https://daily.dev/tags/architecture), [#typescript](https://daily.dev/tags/typescript) [View this post on daily.dev](https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"When is a Monorepo Worth It? (And Why It’s Not Always a Good Idea)","url":"https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd"},"datePublished":"2026-07-22T00:50:40.412Z","dateModified":"2026-09-14T08:41:06.752Z","description":"A developer shares their experience deciding whether to adopt a monorepo for a project with two separate but highly similar web applications. The post outlines...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"webdev,general-programming,architecture,typescript","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"When is a Monorepo Worth It? (And Why It’s Not Always a Good Idea)"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd","comment":[{"@type":"Comment","text":"This is a good rule of thumb: let shared code and team workflow pull you toward a monorepo instead of forcing one too early. For an MVP, separate repos can keep things simple until the duplication starts to hurt.","datePublished":"2026-07-22T02:50:04.229Z","url":"https://daily.dev/posts/gr24SyZQd#c-q6vUYxjvP","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/when-is-a-monorepo-worth-it-and-why-it-s-not-always-a-good-idea--gr24syzqd#faq","mainEntity":[{"@type":"Question","name":"When should I switch a project to a monorepo instead of using separate repositories?","acceptedAnswer":{"@type":"Answer","text":"A monorepo makes sense when code duplication starts seriously slowing development, specifically when apps share the same design components and authentication logic, need unified TypeScript type contracts across frontend and backend so API changes flag breaking changes at compile time, or are maintained by the same team who wants to avoid opening multiple pull requests across repos for one feature. daily.dev surfaces perspectives like this for developers weighing monorepo tradeoffs before restructuring a project."}},{"@type":"Question","name":"When should I avoid using a monorepo for my project?","acceptedAnswer":{"@type":"Answer","text":"Avoid a monorepo when mixing distinct technologies and lifecycles, such as backend and frontend at scale, since forcing radically different architectures into one repository creates overcomplexity. It is also a poor fit when independent teams own separate applications and want isolated deployment flows, permissions, or Git history, or when a product is still in an early MVP discovery phase needing raw delivery speed. developers sorting monorepo tradeoffs against MVP speed often compare notes like this on daily.dev."}}]} ```