OXIDT// meet the developer
Hi, I'm Hauke Jung — I build the Rust pieces my products keep needing.
Every SaaS I ship needs the same foundation: sign-in, billing, docs, a blog, a way to hear from users. Instead of rebuilding it each time, I pull it out, polish it, and release it — as crates, a starter, and soon a hosted cloud. OXIDT is where that work lives, along with notes on what worked and what I'd do differently.
oxidt.
What happens to everything that stays here long enough: it turns to Rust.
the name
Iron that meets air turns to rust.
Oxidised metal is rust — and Rust is the language every product here is written in: the servers, the dashboards, the CLIs, the MCP servers. OXIDT is the German-flavoured spelling of that process.
It's also a promise about the code: it is meant to last. Pieces that proved themselves in one product get extracted, hardened, and reused in the next, until they are boring in the best way.
why oxidt
Small tools, built to be kept.
One developer, a focused scope, and a long-term commitment to the people who build on it.
what i'm building
Products behind the notes
- Stepshots turns a product walkthrough into an interactive demo you can edit and share.
- SeggWat collects feedback where people use your website, with screenshots and context attached.
- infra.page brings a project's public metrics and infrastructure signals onto one page.
what i write about
Notes from real projects
Most posts start with something a real project needed: a typed WebSocket connection, a feedback integration, a deployment that search engines should notice. I also experiment with AI-assisted development and self-hosting, and document what helps.
get in touch
Say hello
Questions about a crate, the starter, or working together? Write me — I read everything and answer as soon as I can.