What FreeOxide is
FreeOxide is where I publish my Rust tools. It isn't a company and it isn't a team. It's one person writing the things he wanted to exist, then putting them out under a permissive license. Free software, oxide as in Rust.
The list stays short on purpose. Each project does one job all the way through instead of half of five, and nothing gets listed until it clears the standard below. That's why you're looking at 4 shipped and 2 in progress rather than a page full of abandoned repos.
Everything is MIT or dual MIT / Apache-2.0 unless a repo says otherwise. The git history is readable, there are no hidden dependencies, and none of the binaries phone home.
The standard every project clears
I decide architecture by hand. For audits and tests I run the same model across several fresh sessions, because each one catches what the last one missed.
- Architecture by experience
- Folder structure, module boundaries, and layout decided upfront from what I know works.
- Five AI audit passes
- Same model, different sessions. Each finds things the last missed. After five, the returns thin out.
- Five testing rounds
- Same approach. AI writes tests, I review, next session catches what the previous one missed.
- Idiomatic & documented
- Clippy-clean with sensible defaults. If something needs a comment to use safely, it gets one.
- Open by default
- MIT / Apache-2.0, readable git history, no hidden dependencies.
Five rounds of audits and five of tests is where it stops paying. Past that you're burning tokens. Coverage sits above 90% and clippy runs clean before anything ships.
What has shipped
- gpui-starter↗ : A batteries-included starting point for native GPUI apps. The scaffold I wanted on day one.
- gpui-query↗ : Reactive async queries for GPUI apps. Fetch, cache, and invalidate without leaving the render tree.
- tunnel↗ : Serves a local directory over an ephemeral Cloudflare Quick Tunnel. You get a public HTTPS URL in a few seconds without a Cloudflare account or any DNS setup.
- wake↗ : Keeps a machine awake for as long as you ask. When the OS refuses the lock it says so instead of failing quietly, and ow doctor prints what each backend can actually guarantee.
Install commands and the endpoint list live on /developers. /activity has a build-time snapshot of commits, pull requests and releases across every repo.
Who's building this
hmziq (@hmziqrs). I write the Rust, ship the tools, and open-source the results. Architecture, implementation, tests, audits, releases and this website are all me. Which is slow, but it does mean there's nobody to hand a shortcut to.