Developer tools we build and maintain
Libraries we needed, could not buy at a sane price, and therefore wrote — now packaged, documented and licensed for everyone else.
Most of what we build is client work, and it stays with the client. Occasionally a piece of it turns out to be a problem nobody has solved well — something we needed, went looking for, and found only behind a four-figure licence tied to a seat count and a native binary we could not deploy. When that happens often enough, we write the library properly and license it ourselves.
That is the entire product line. It is small on purpose. Each tool exists because we hit the wall it removes, use it in production ourselves, and maintain it as a real dependency rather than an abandoned side project. There is no roadmap of things we hope someone wants — just the ones that already earned their place.
Everything here is aimed at developers, so the documentation is written for developers: install command first, working example second, honest list of unsupported edge cases third. You can evaluate every feature on a free tier before you pay anything, and the paid tiers exist to fund maintenance, not to gate functionality you have already built against.
What you can expect from anything on this page
One price, deploy anywhere
No seat-count audits, no separate licence for running in a container, no OEM tier that costs five times the entry price. If you bought it, you can ship it.
Benchmarked, not asserted
Where we claim fidelity or performance, the number comes from a reproducible test on a real corpus and it is gated in CI. We publish the method alongside the result.
Degrade, never crash
Unsupported input produces a labelled placeholder and a warning, not an exception. A batch job should not die at slide 300 because one shape was exotic.
Need something like this built for you?
The engineering behind these tools is the same engineering we bring to client projects — rendering pipelines, file-format work, Python packaging and the kind of test discipline that lets you publish a fidelity number. If that is the sort of problem you are facing, see our custom software development services or the products we've built.
Questions about licensing?
Volume, redistribution or a use case that doesn't fit a tier — just ask.