← Blog

engineering

One repository, until there is a reason

Splitting early buys coordination overhead and sells nothing.

14 July 2026 · By Marcus Bell, Platform · 4 mins

The SDK, the docs, the gateway and the control plane all live in one repository. Every few weeks someone suggests splitting them, and the answer keeps being no.

The boundary that matters is not the repository — it is the import graph. A dependency-cruiser rule stops the gateway importing Stripe or the console, and that rule works whether or not the code lives in the same folder.

What a split would buy is four release processes and a coordination problem every time a type changes. What it would sell is nothing we have needed yet.

Subscribe to our newsletter

Enter your contact details to get the latest news and trends to help boost your product.

Seams collects and processes your personal data to deliver the newsletter you requested. Learn more about how we manage your data and your rights.

Ready? Let's go.

Whether you want to examine the specific needs of your product, or go over the benefits of Seams, we are here for you.