TL;DR
Kasava keeps its entire platform—including frontend, backend, docs, marketing, and more—in a single monorepo so changes propagate from one commit. The team emphasizes AI-native workflows that use the repository as a single source of truth to speed updates, reduce mismatches, and unify review and deployment.
What happened
Kasava consolidated its product, documentation, marketing assets, integrations, and tooling inside one repository. The company reports a codebase with thousands of TypeScript files and directories for a Next.js frontend, a Cloudflare Workers backend, marketing and docs sites, email templates, and multiple external integrations. Routine updates—such as changing billing limits stored in a shared JSON file—are made in a single commit that the backend enforces, the frontend displays, and the marketing and docs sites reflect. The monorepo is presented as the canonical context for their AI tooling: models can read implementation, docs, and site content simultaneously to suggest or validate changes. All content and code are versioned and shipped via the same git workflow, pull requests, and CI/CD pipeline, so marketing copy, investor slides, and feature changes go through the same review and deployment path.
Why it matters
- A single repository gives AI tools direct access to code, docs, and marketing content, enabling context-aware updates and validations.
- Atomic commits across frontend, backend, and docs reduce version mismatches and coordination overhead between teams.
- Using git for code and content standardizes review, auditing, and rollback procedures, reducing reliance on separate CMS or marketing tools.
- Consolidated tooling and pipelines simplify dependency management, testing, and cross-project refactoring.
Key facts
- Kasava stores everything in one repo that contains 5,470+ TypeScript files (as reported).
- Frontend: Next.js 16 with React 19; Backend: Cloudflare Workers API.
- A single billing-plans.json config is used by backend enforcement, frontend UI, and the marketing pricing page.
- Content such as blog posts, emails (MJML), and an investor deck are kept as code, reviewed in PRs and deployed via git push.
- The backend includes services, workflows (Mastra AI workflows), a Drizzle ORM schema, durable objects, and queue consumers.
- Examples show features added in one commit that include backend routes, frontend components, docs, and website pages.
- The monorepo approach is framed as enabling 'AI-native development' by providing unified context for automated tools.
What to watch next
- Whether the monorepo approach exposes new scaling or CI/CD bottlenecks as the codebase grows: not confirmed in the source.
- How other organizations respond to or adopt an "everything-as-code" monorepo model over traditional polyrepo setups: not confirmed in the source.
- Potential security, access control, or governance trade-offs of putting all code and content in one repository: not confirmed in the source.
Quick glossary
- Monorepo: A single version-controlled repository that contains multiple projects, applications, and assets instead of separate repositories for each.
- CI/CD: Continuous integration and continuous delivery/deployment — automated processes that build, test, and deploy code changes.
- Cloudflare Workers: A serverless platform for running JavaScript or WebAssembly at the edge, used to host APIs or application logic.
- JSON: JavaScript Object Notation, a lightweight data-interchange format often used for configuration files.
- AI-native development: A workflow designed so AI tools have immediate access to code and related artifacts, enabling context-aware automation and validation.
Reader FAQ
What does 'everything as code' mean at Kasava?
It means code, docs, marketing content, email templates, and even the investor deck are versioned and managed in a single git repository.
Does Kasava use AI to validate changes?
Yes — the company describes using AI tools to read code, docs, and site content in the repo to suggest and verify updates.
Do they use Contentful or other external CMS platforms?
No — the source says they avoid separate CMSs and publish marketing and docs from Git instead of external admin panels.
Is the Kasava repository public?
not confirmed in the source
Are there known drawbacks or limits to this approach?
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
- What is monorepo? (and should you use it?) – Semaphore CI
- Monorepo Explained
- What is a monorepo and should you use one?
Related posts
- Show HN: I remade my website in the Sith Lord Theme and I hope it’s fun
- FediMeteo: How a €4 FreeBSD VPS Evolved into a Global Weather Service
- Show HN: 22 GB of Hacker News in SQLite — Hacker Book dataset post