I build and operate self-hosted infrastructure, backend services, and internal tooling.
I'm a Platform & Infrastructure Engineer working across Linux systems, networking, containers, backend development, and automation.
I design and operate self-hosted infrastructure, build internal tooling, and write backend services primarily in Go.
My work focuses on practical systems that are understandable, observable, reproducible, and easy to operate.
Current areas of focus include:
- Linux and containerized infrastructure
- Networking, DNS, TLS, reverse proxies, and access control
- Infrastructure automation and CI/CD
- Monitoring and observability
- Backend and internal tooling in Go
- Distributed systems and reliable event delivery
Self-hosted event delivery platform for routing operational events without coupling producers to notification providers.
- Event ingestion and routing
- Template-based rendering
- Independent Core and Dispatcher runtimes
- Valkey / Redis Streams transport
- Gotify, ntfy, Discord, and Slack providers
- Prometheus metrics and operational observability
- Retry and delivery reliability work in progress
Navire is developed toward a public open-source release.
Website • Project Origin • Roadmap
I operate a self-hosted environment used for running services, testing infrastructure patterns, and building internal tooling.
It includes Linux virtual machines, containerized workloads, segmented networks, internal DNS, reverse proxies, monitoring, databases, CI/CD, and custom Go services.
I document the architecture, operational decisions, and experiments on Nexacloud.
For reusable service definitions, see homelab-blueprint.
Go CLI for bootstrapping and maintaining local development environments through declarative configuration.
- Declarative YAML configuration
- Bulk package management
- Idempotent execution
- Reproducible workstation provisioning
Self-hosted service launcher that turns the browser address bar into an entry point for internal services.
It uses fuzzy matching and existing Homepage configuration as its source of truth, avoiding a second service registry.
Modular dotfiles built around reproducibility, maintainability, and a minimal host configuration.
My homelab is also my engineering sandbox.
I use it to operate real services, test infrastructure patterns, build automation, observe failure modes, and validate architectural decisions outside of toy environments.
The environment includes:
- Proxmox virtualization
- Linux virtual machines
- Docker-based workloads
- Segmented VLAN networks
- Internal DNS
- Reverse proxies and TLS
- Secure external access
- PostgreSQL and Valkey
- Prometheus and Grafana
- Self-hosted Git and CI/CD
- Custom Go services and infrastructure tooling