Everything as Code: How We Manage Our Company In One Monorepo

General Developer Forum In The News
1

Last week, I updated our pricing limits. One JSON file. The backend started enforcing the new caps, the frontend displayed them correctly, the marketing site showed them on the pricing page, and our docs reflected the change—all from a single commit.

No sync issues. No “wait, which repo has the current pricing?” No deploy coordination across three teams. Just one change, everywhere, instantly.

At Kasava, our entire platform lives in a single repository. Not just the code—everything…

Read in full here:

1 Like
2

I had the experience of working in a project with multiple repos. It was such as pain to work with.

3

Love the simplicity of this. Nice work!

I like the idea of using simple static files when possible, checked in to version control. I built my personal website completely statically and was surprised how much I could do without any kind of database or third-party integration and their associated state management problems (such as DB migrations, auth, etc).

4

Same here. Working with multiple repos was a real pain since everything was scattered all over the place. It made it hard to keep things consistent and really take advantage of the built-in project management features.