Why we don't open source every package, yet

We build a lot of internal packages, and people sometimes ask why they are not all on GitHub for anyone to use. It is a fair question, and the honest answer has a few parts. We like open source, we depend on it every single day, and we want to give more back over time. We also run a small studio, and a handful of those tools are the edge that lets us ship faster and steadier than we otherwise could.

We are not hoarding code

Open source is most of our stack. Laravel, the TALL stack, and countless community packages: we would not have a business without them. We try to be good citizens by reporting issues, sending fixes upstream, and sharing what we can. Keeping a few packages private is not about gatekeeping. It is about focus and staying around long enough to be useful.

A polished open source project is a product in itself. It needs documentation, versioning, issue triage, and real support. We would rather maintain a small number of public packages well than publish a pile of half-documented repositories and quietly abandon them. Quality of service applies to open source too.

The private tools are how we move fast

Some of our packages encode years of production lessons: an import pipeline, a media library, a content engine, the unglamorous plumbing that turns a great idea into software people actually rely on. They are battle tested on our own products before they ever touch a client project.

When you work with us, you get those building blocks from day one. That is not a paywall around knowledge. It is the difference between starting a project halfway done and starting from a blank file. The tools, plus the team that built and operates them, are what we actually offer.

We do plan to open source more, over time

Our intent is to release more of these packages publicly as they mature and as we can commit to maintaining them properly. A few are already close. When one is stable, documented, and useful beyond our own walls, we would rather share it than keep it locked away, and we will say so right here when it happens.

So the short version: we are not the kind of studio that hides everything and calls it strategy. We open what we can, we keep a few things private so we can keep the lights on and keep shipping, and we are steadily working toward giving more back.

If you want early access to the proven tools behind our products, the fastest path is to build something with us. Write to us at hi@kadiaak.com, or follow along in the newsletter, where we open the workshop once a month.