We release open source for a selfish reason: the alternative is writing the same glue code on every project, and we got tired of that years ago. Most of our public packages started life as private code inside a paid project, got extracted once they stopped changing every week, and are now running in production on whatever we’re building next.
What we ship as open source
The public catalogue covers three rough categories.
Language bindings. Native addons that bring a non-JavaScript SDK into the
Node ecosystem. @vygr-labs/ndi-node is the current example: a Node.js binding
for the NDI (Network Device Interface) SDK used for video and audio streaming
over IP networks.
Desktop applications. Cross-platform desktop software released under
copyleft licenses. noted (a distraction-free note-taking application) and
crater (a scripture projection tool for churches) are the two current
public projects, both built on Electron with a Solid.js front-end and SQLite
persistence.
Developer tooling. Smaller utilities that remove a specific friction from our own workflow. These rarely get marketed; they are indexed here because someone else's team has usually hit the same friction.
How we maintain it
Every public package has a named maintainer inside the studio. Issues are triaged weekly. Security reports receive a written acknowledgement within two business days and a patched release on the same schedule as any other priority work. We do not abandon packages; when a project reaches end-of-life, it is marked as such in the README rather than left to accrue stale issues.
Sponsored work
For companies that depend on one of our packages and want specific features, guaranteed response times, or a security audit, we take on sponsored maintenance on a retainer basis. The contract terms are written, not hand-shaken; the package stays open source.