Things I build in the open, from hardware to backend
Full products I develop and run myself, from hardware to web UI.
AI-powered, dietician supervised (optionally) meal planning and body tracking application.
Why I built it: I wanted a meal planner that keeps my data on my server and lets a real dietician override the model. It doubles as my playground for Go + HTMX and a Flutter client sharing one API.
An autonomous gardening system that waters, monitors, and optimizes plant growth - from home to commercial scale.
Why I built it: it's the whole KhazLabz stack in one box: sensors and pumps on custom hardware, firmware talking to a Go backend, and dashboards on top. If a bug can hide between layers, this project finds it.
Small single-purpose services that keep khazlabz.eu self-hosted and script-friendly.
Self-hosted contact form backend. One Go binary, standard library only, forwards submissions by e-mail through Scaleway Transactional Email.
Why I built it: I wanted this site's contact form without third-party scripts, a strict CSP and form data that never leaves EU infrastructure I control.
Themed login page for a static site behind Caddy, using forward_auth. Browsers get a form and a signed cookie; scripts keep plain HTTP Basic Auth against the same bcrypt hashes.
Why I built it: the browser's Basic Auth dialog cannot be styled. This keeps the same credentials and a stock Caddy binary, and puts the KhazLabz theme on the staging login.
Everything here is open source and contributions are welcome: fork it, open a pull request, or report an issue.
Follow along on GitLab: gitlab.com/khazlabz
