Open source by default

Every studio has a private folder of "things we always rewrite". Auth flows, settings panels, contact forms, importers, scheduling helpers, the same five rate limiters. We treat that folder as a bug. When we notice we are writing the same component for a third time, we stop, lift it out into its own package on GitHub / Packagist / npm, and use it from there forever after. The customer who paid for the third instance gets the feature they actually wanted; we get a reusable building block; everyone after them gets it for the price of composer require.

When we are extracting a module out of your project, the clock is off. That is the deal. You paid for "we need a working scheduler for our staff", you did not pay for "Blax now has a polished Laravel-Schedule package". The packaging work is our investment in our own toolbox; billing you for it would be billing twice for one piece of value. The same goes for tooling: the test harnesses, the Docker images, the CI templates we use across projects come out of our pocket, not yours.

A module is only useful if it keeps working. When the next Laravel or Nuxt or PHP version drops and breaks something, we fix the module, not your snapshot of it. That fix flows to every project that depends on it, including yours, at no extra charge. Security advisories get the same treatment: a CVE in a shared dependency means one patch and one release, not seven panicked client calls. This is how we can quote tight numbers on real work; the foundation under that work is paid off.

We could keep our modules in a private registry and pretend that the moat matters. It does not. Open code gets read, audited, improved and fixed faster than private code, and a customer who can read what we wrote can tell whether to trust us with the rest. Open also means you are never locked in: if Blax disappears tomorrow, the modules you depend on are still on Packagist, still under a permissive licence, still maintainable by whoever you hire next. We think that is the right posture for a vendor to have.

Our catalogue lives at /links and on the Blax Software GitHub organisation. Laravel packages, Nuxt modules, browser-side components, WordPress plugins, microcontroller firmware libraries. Whatever shape the reuse takes, that is where it lands. If something we have built would obviously belong in your stack and we have not packaged it yet, ask. It is usually a week-of-Tuesday away.