TL;DR
Kasava keeps its entire platform — apps, backend, marketing, docs, and more — inside a single monorepo so one commit can update product behavior, marketing copy, and documentation at once. The setup is presented as an "AI-native" development model where tooling and AI agents can operate across the whole codebase as a single source of truth.
What happened
Kasava consolidated its product, services, marketing assets, documentation and internal specs into a single repository. The repo contains thousands of TypeScript files and distinct top-level folders for frontend (Next.js + React), backend (Cloudflare Workers), website, docs, marketing content, email templates (MJML), external tools, and internal architecture documents. The team describes workflows where a single JSON change (for example, pricing limits) updates enforcement in the backend, UI in the frontend, and copy on the marketing site and docs without cross-repo coordination. Developers open one pull request that may include API code, frontend components, docs, and marketing pages together. The company frames this approach as enabling AI tools to read and validate changes across the entire codebase, and as simplifying deployment and review by treating content and code the same way: git-based commits, unified CI/CD, and shared reviews.
Why it matters
- A single repository reduces the risk of inconsistent versions across frontend, backend and marketing by enabling atomic, cross-boundary commits.
- AI tools can operate with full context when code, docs and marketing live together, enabling automated validation and faster updates.
- Uniform workflows (git push, PR review, CI/CD) let non-engineering contributors ship changes through the same processes as developers.
- Shared tooling and a single pipeline make searching, refactoring, and auditing changes simpler compared with fragmented repositories or separate CMSs.
Key facts
- The top-level repository reportedly contains 5,470+ TypeScript files.
- Frontend is built on Next.js 16 with React 19 and includes 25+ route directories and about 45 component directories.
- Backend runs on Cloudflare Workers and includes 55+ business-logic services plus AI workflows and database schemas.
- Documentation and marketing content are versioned in Git: public docs (Mintlify), marketing site (kasava.ai), and blog posts live as Markdown with frontmatter.
- Marketing assets include an investor-deck implemented as a Next.js site and email templates authored in MJML.
- The team keeps canonical configuration files (example: billing-plans.json) that the backend enforces and the frontend and website consume.
- Feature additions and integrations (example: Asana) are shown as single commits that span backend routes, frontend components, docs and website pages.
- All content and code changes are shipped through the same git-based review and CI/CD flow rather than separate CMS dashboards.
What to watch next
- How repository scale affects developer tooling performance and CI/CD times: not confirmed in the source
- Whether governance and access controls evolve to manage more contributors in a single repo: not confirmed in the source
Quick glossary
- Monorepo: A single version-controlled repository that stores multiple projects, services, libraries, and assets together rather than splitting them across separate repos.
- CI/CD: Continuous Integration/Continuous Delivery — a set of practices and tooling that automatically build, test, and deploy code after changes are made.
- MJML: A markup language for designing responsive email templates that can be converted into HTML for sending campaigns.
- AI-native development: An approach that structures code and processes so AI tools have direct access to the full context they need to assist with writing, validation, and automation.
- JSON: A lightweight data-interchange format commonly used to store configuration and structured data in codebases.
Reader FAQ
Why keep everything in one repository?
Kasava says a monorepo enables atomic changes across frontend, backend, docs and marketing so updates and reviews happen in a single PR and stay consistent.
How are marketing and docs managed?
Marketing pages, blog posts and docs are stored as code — Markdown and MJML files — versioned in Git and deployed via the same pipeline.
Does AI verify changes across the repository?
The source describes using AI agents that can read the whole repo to validate implementations and surface inconsistencies.
Are tooling or scaling limitations discussed?
not confirmed in the source
Back to Blog Engineering Everything as Code: How We Manage Our Company In One Monorepo Ben Gregory – Dec 29, 2025 Introduction Last week, I updated our pricing limits. One…
Sources
- Everything as code: How we manage our company in one monorepo
- How We Manage Our Company in One Monorepo
- Monorepos: A Comprehensive Guide with Examples
- What is monorepo? (and should you use it?) – Semaphore CI
Related posts
- Professional Software Developers Don’t Vibe, They Control: AI Agent Use in 2025
- Zpdf: Zig PDF text extraction library — up to 5x faster than MuPDF
- F-Droid upgrades core server with donated hardware to boost build speed