Default to public
General-purpose tooling we build for ourselves gets published where we can publish it. Client deliverables never do, and that boundary is agreed before an engagement starts.
Tooling we publish
The parts that aren't yours.
Client deliverables belong to the client. General-purpose tooling stays ours, and where it's useful to anyone else we publish it under a permissive license.
How we think about it
Three commitments.
These are what keep a repo of ours worth using six months after we published it.
Maintained, not dumped
We don't toss code over the wall and walk off. We answer issues, review pull requests and keep the libraries we lean on actually alive.
Yours to fork
Everything here ships under a permissive license. Use it, change it, ship it inside your own product without asking us first.
The workshop
Everything we can, in the open.
Browse what's published below, or go straight to the org on GitHub.
Lend a hand
How to get involved.
These are shared things, so the door's always open. Whether you've found a rough edge, fixed one, or just want to keep the lights on, here's where to start.
Open an issue
Hit a bug, a gap in the docs, or a missing feature? Tell us. A clear issue is genuinely one of the most useful things you can send.
Send a PR
Fixed something or built an improvement? We review pull requests properly, and first-timers are very welcome.
Sponsor
If something here saves your team time, sponsorship keeps it maintained for everyone. Or just tell us where it ended up.
Open by default
Want us to open-source part of your stack?
If there's a library, starter or tool inside your product that the wider world could use, we'll help you carve it out, document it and ship it in the open, with you owning the result.