Open Source Tools.
We publish real tools. You can verify our engineering on crates.io and the Chrome Web Store.
By Brian Gagne, CTO · March 19, 2026
Talk is cheap. Code ships.
Anyone can claim they are good engineers. We publish ours. Our open source tools are available on crates.io and the Chrome Web Store for anyone to inspect, use, and evaluate. This is not marketing. It is proof of work. When a prospect evaluates us, they do not have to take our word for it. They can look at the code, read the commits, and use the tools themselves. That is the kind of transparency that builds trust faster than any sales deck.
de-slop is a Chrome extension that detects and removes AI-generated slop from web pages. 180+ detection patterns across a 3-tier weighted scoring system covering AI-specific patterns, corporate buzzwords, and marketing spam. Real users on the Chrome Web Store. GPL-3.0 licensed. The same technology powers our content pipeline's quality gate.
What we publish
A Rust-based enterprise secrets manager with AES-256-GCM encryption and Argon2 key derivation. Published on crates.io. A Rust-based system information display, also on crates.io. An Arch Linux security scanner for AUR package vulnerability analysis, built as a multi-crate Rust workspace. And de-slop, our Chrome extension for detecting AI-generated content. 180+ patterns, 3-tier weighted scoring, real users. The same slop detection engine runs in our content automation pipeline, which means every piece of content we publish passes the same quality gate our users can install for free.
Verifiable proof of quality
Our open source work is public proof that we build things correctly. AES-256-GCM encryption with Argon2 key derivation is not a checkbox claim. It is published code you can audit. Our custom tooling portfolio of 40+ internal tools follows the same engineering standards.
From internal tool to public proof
Problem
AI-generated content was flooding the web with low-quality text that followed predictable patterns. Our own content pipeline needed a quality gate to ensure nothing we published sounded like AI slop.
Solution
Built a 3-tier weighted pattern detection system. Deployed it first as an internal quality gate for our content automation pipeline, then published it as a free Chrome extension so anyone could use it.
Outcome
180+ detection patterns. Real users on the Chrome Web Store. GPL-3.0 licensed. The same engine runs in our production content pipeline, which means our published content passes the same filter our users apply to everything else on the web.
Building tools you actually use yourself is the best quality assurance. If it is good enough for our production pipeline, it is good enough to publish.
Why we open source
Open source is not charity. It is accountability. Publishing code means our engineering is subject to public scrutiny. That raises the bar for everything we build, open or not. It also means prospects can evaluate our work before any conversation happens. Check our Trustpilot reviews at trustpilot.com/review/kief.studio, look at the code on crates.io, install de-slop from the Chrome Web Store. Then decide if you want to talk. First conversation is free at kief.studio/contact.
Frequently asked questions
Can I use your open source tools commercially?
Check the license on each tool. de-slop is GPL-3.0. Other tools have their own licenses specified in the repository. If you have questions about a specific tool, reach out.
Do you build custom tools for clients too?
Yes. We have built 40+ custom internal tools and build purpose-specific tooling for clients regularly. The open source tools are a sample of the engineering quality you get in a client engagement. See our custom tooling article for more detail.
Where can I find your published tools?
Rust tools on crates.io. de-slop on the Chrome Web Store. Trustpilot reviews at trustpilot.com/review/kief.studio. All publicly available for you to evaluate before any conversation.