Open source
Giving back, with tools you can inspect.
What we build for our products, we share again: a family of Rust engines and applications, a family of TypeScript libraries, and skills for coding agents. The full catalogue with every project lives on the Open Source site; this page explains why we do it and what belongs together.
Ferramenta
Rust engines and applications for documents and text: parsing, rendering, and converting Markdown. Built because our products needed tools written in modern Rust, tested, and measurable. The family has its own site with benchmarks and comparisons.
ferramenta.dev →Effective
Libraries and skills for everyday work in TypeScript projects: colors, CSS, icons, favicons, shadows, setting up a new machine. Small tools we need in every project and therefore maintain instead of rewriting them each time.
To the Open Source site →Skills for coding agents
Six skills that put our way of working into verifiable instructions, so agents work the way we would expect in a review. Expertise you can read before you install it, with results that still depend on the model.
To the Skills site →Open source
Counted, not claimed.
Every number here is live from the metrics service, refreshed hourly from GitHub, npm, and crates.io, and republished with every build. We do not maintain figures by hand.
- 26
- Projects on GitHub
- 10
- Ferramenta: engines and applications in Rust
- 377
- References to our agent skills
Hourly from GitHub, npm, and crates.io
Why
Open source shaped our careers. We give back.
Three reasons we keep publishing, even when a tool would be easier to keep to ourselves.
Gratitude
Our careers began in open source: qooxdoo at 1&1, Unify at Deutsche Telekom, Jasy at Zynga. The tools and the people around them taught us most of what we know. Publishing what we build today is how we return the favor.
Trust through inspection
An open tool can be read, benchmarked, and corrected by anyone. That keeps us honest about quality and keeps our products on foundations that outlast any single vendor, including us.
Open standards
Open standards over proprietary formats: Markdown, gettext catalogs, plain files in a repository. Whatever we build should leave your data in a form you can take elsewhere.
Contact
Let's talk about what is meant to last.
For products and partnerships, an email is enough. Project support is at Sebastian Consulting, directly with the two founders.
