December 30, 2025
One repo to rule them all (and split the room)
Everything as Code: How We Manage Our Company in One Monorepo
One giant code folder runs the company—converts cheer, veterans warn of “scale hell”
TLDR: Kasava runs everything from one code folder and uses AI to keep the app, website, and docs in sync. The crowd is split: converts love the speed and single source of truth, while veterans warn about future scaling headaches, messy dependencies, and deployment chaos—crucial trade‑offs for fast‑moving startups.
Kasava just bragged they run their entire business—from app to website to docs—out of one giant code folder (a monorepo). They changed one pricing file and boom: backend, frontend, marketing page, and docs all updated in one swoop. Their pitch: this is AI-native work. Give tools like Claude full company context, and they can update pages, verify claims, and keep everything in sync. One button (“git push”) publishes code, blog posts, even prices—no dashboards, no content systems.
The comments? A spicy split. One former hater is now a believer: Claude made monorepo click. But old-school vets warn this path leads to the dreaded “scale hell”—the nightmare where one folder grows too big and breaks teams. Some worry constant deployments could turn chaotic, and the “no workspaces” setup could cause those infamous “works on my machine” bugs. A multirepo loyalist (many smaller folders) dropped a throwback: use git submodules and avoid the pain we had “20 years ago.”
The memes flew fast: “one folder to rule them all,” “press push, pray,” and “ship a typo to the homepage at the speed of light.” Fans love the speed and single source of truth, skeptics say it’s perfect… until your team grows and the wheels wobble. Drama level: high.
Key Points
- •Kasava stores code, website, documentation, and marketing assets in a single monorepo.
- •A single JSON change updated pricing across backend, frontend, marketing site, and docs in one commit.
- •The repo includes a Next.js 16 + React 19 frontend, Cloudflare Workers backend, Mintlify docs, and extensive tooling and services.
- •The approach is positioned as AI-native, enabling AI tools (e.g., Claude) to validate and update content using full repository context.
- •All publishing and deployments use a unified git push workflow, avoiding separate CMSs and multi-tool synchronization.