Platform / infrastructure engineer. From code to production, through CI/CD, observability and security — an integrated ecosystem designed to be operated over the long run.
Working as an engineer for 10 years. My specialty: designing coherent distributed systems and keeping them operable over time.
What I show here is infrastructure actually running in production for my daily use, tested under failure, with full observability and an end-to-end CI/CD chain.
On the people side, I mentored two interns from the ground up on our stack — both were hired at the end of their internship. Helping others level up is part of how I approach the craft.
My areas of focus: Rust, container orchestration, security / isolation, networking, and self-hosted observability.
Three pieces that, together, cover the essentials of a platform profile: operating a system, designing a secure architecture, and thinking about scale.
A complete ecosystem — code → CI → production → observability — on bare metal, validated by real failure tests.
Having a reliable personal platform to host and operate my own services, with the standards of real production: resilience, alerting, zero data loss.
CoreDNS for *.internal resolution with fallback to Docker's DNS.A code-review and AI-assistance bot for Gitea, written in Rust, with a security-first agentic architecture.
No AI assistance solution exists for Gitea. A real need: solo code review, implementing tests/features, usable day to day — including from a phone.
The challenge of an agent that executes code isn't making it run, but making it run without risk of exfiltration or compromise. The decisions:
.git "disarmed" for reading (remotes removed, credentials cleared, hooks emptied) — on a copy, with the armed original staying on the host.postCreate.An extended imgproxy-style media processing pipeline, designed for horizontal scaling and streaming.
Process media (images, streaming) compositionally, with an architecture able to scale out horizontally — and serve as a real load-testing playground.
NATS.An ideal candidate for load tests (k6) instrumented by my observability stack — validating system behavior at scale and documenting the breaking points.
Rust (async / Tokio), TypeScript / Node. Looking for the right tool for the right problem.
Docker Swarm, bare metal, Fedora Bootc (immutable OS), CI/CD (Gitea, Woodpecker).
OpenTelemetry, Prometheus, Loki, Tempo, Perses, Alertmanager. Full stack, tested under failure.
WireGuard, CoreDNS, overlay networks, Caddy. Designing self-hosted private networks.
Container sandboxing, privilege separation (DBus / Polkit), threat modeling.
NATS, distributed architectures, claim-check patterns, horizontal scaling.
Interested in platform / infrastructure / staff roles where technical quality and autonomy matter. The code for everything shown here is available to review.