Developer Tooling & Open Source
Libraries, SDKs, and internal tooling — designed as public APIs, with the docs, types, and versioning discipline that implies.
A library is a promise about an API you will keep supporting. That changes how you build it: the surface has to be small, the types have to be precise enough to catch misuse at compile time, and breaking changes have to be a deliberate act rather than an accident.
We publish our own packages under this discipline — zero runtime dependencies, full TypeScript types, documented API references, semantic versioning, and CI running the test suite on every commit. encryptix and strio are both live on npm.
The same approach applies to internal tooling: the SDK your teams build against, the CLI that automates a painful workflow, the shared component library that stops three squads reinventing a button.
Tell us what you're building
A few sentences is enough to start. If it's a fit we'll come back with questions and a rough shape; if it isn't, we'll say so rather than waste your time.