We build practical systems that make living and building easier.
We prioritize utility over attention. If a tool doesn't remove friction or reduce decision fatigue, we don't build it.
Software should be boring.
Most widely-used tools today solve symptoms while adding complexity. We focus on causes. We design systems that are readable, maintainable, and built to outlive the teams that created them.
- Clarity over cleverness. We prefer code that is easy to read over code that is fast to write.
- Dependencies are liability. We add them only when necessary.
- Scarcity is a feature. Constraints breed better solutions than abundance.
Our work is not an experiment. These are the tools we use to run our own organization.
- SecretsCLI: A simple, secure way to manage environment secrets across projects without leaking them into your workflow
→ Built for developers who want less ceremony and fewer mistakes
We open our work because clarity compounds when it is shared.
We value attention from engineers who care about craft.
- Star the repositories that resonate with your own philosophy.
- Read the code. We treat documentation as part of the codebase, not an afterthought.
The best way to understand our systems is to use them.
clone a repository, read the CONTRIBUTING.md, and run the test suite. If the setup isn't simple and reliable, that's a bug—please report it.
We welcome contributions that align with our values.
- Think in systems. Don't just patch a bug; understand why it exists.
- Reduce complexity. We prioritize PRs that delete code over those that add feature bloat.
- Discuss first. Open an issue to discuss your approach before writing code. We prefer to align on the "why" before the "how."
The work happens here on GitHub. The story happens on our website.
If you are looking for hype, you won't find it here. If you are looking for tools that respect your time, welcome.