RhysLippmann

Infrastructure as craft

Seven years in IT operations has taught me that reliable infrastructure is equal parts technical detail, disciplined process, and clear communication. My work has moved from day-to-day systems support into the automation and platform thinking that keeps services dependable at scale.

I enjoy understanding how the pieces connect: identity, networking, virtual machines, monitoring, documentation, and the people relying on them. The goal is always the same—make production feel predictable, even when the work behind it is complex.

Azure Cloud

Azure is the cloud platform I know best across enterprise and managed-service environments. I work with virtual machines, resource groups, identities, access, networking, and the operational practices that make cloud services maintainable after they are deployed.

Rather than treating cloud as a collection of portals and products, I focus on clean foundations: sensible organisation, repeatable changes, visible ownership, and enough observability to understand what a platform is doing.

Containers & orchestration

Containers are where I turn experiments into repeatable services. In the homelab, Docker and Compose make it practical to run, rebuild, and document applications without relying on one-off machine state.

I am building toward deeper orchestration knowledge with Kubernetes, while keeping the operational basics front of mind: clear configuration, persistent data, secure secrets, health checks, logs, and a redeploy process that still makes sense at 2 AM.

Pipeline automation

Bash, GitHub Actions, and Azure DevOps are the tools I reach for when a process needs to become reliable, reviewable, and repeatable. If a task runs twice, it is usually a strong candidate for automation.

Good automation is more than a script that works once. It needs useful output, sensible failure handling, version control, and documentation so the next person can understand exactly what changed and why.

Observe everything

Grafana dashboards, metrics, logs, and alerts turn infrastructure from a black box into something teams can reason about. I care about knowing what changed, where a bottleneck is forming, and whether a service is behaving as expected.

The best monitoring is actionable rather than noisy: clear signals, useful context, sensible thresholds, and dashboards that help someone investigate a problem before it becomes an outage.

Junior DevOps Engineer · Present

ADITS

DevOps across managed IT and client platforms — automation, cloud infrastructure, deployment pipelines, and observability for Queensland businesses.

Designing repeatable workflows, supporting Azure based environments, and building the monitoring and tooling that keeps client systems reliable. The work sits at the intersection of practical operations and continual improvement: reduce friction, expose useful signals, and leave systems easier to run than before.

That means approaching changes with an operator’s mindset. Understand the environment, make the process visible, automate what is stable, and document enough context for reliable handover and support.

NetMap

Selected project · Self-hosted

NetMap is a practical network overview built to make a homelab easier to understand at a glance. It brings together device mapping, IP tracking, downtime alerts, and firewall logs in one place instead of leaving those signals scattered across separate tools.

The project is an exercise in operational visibility: know what is connected, notice when something disappears, and have enough context available to start network triage with confidence.

Focus

Visibility

Environment

Homelab

Purpose

Network triage

Homelab engineer

The homelab is where I test ideas before they become habits. Grafana stacks, nginx proxies, self-hosted services, and password-management tooling provide a safe environment to practise the trade-offs that matter in real infrastructure.

Every build is an opportunity to work through deployment, backups, upgrades, networking, documentation, and recovery. It is hands on learning with the same question in mind: how would this behave if someone needed it to be dependable?

The numbers

• 7+ years experience
• 180+ deploys
• 99% uptime focus
• 2 clouds

These numbers are a snapshot of the direction behind the work: a long operational foundation, a growing automation practice, and a consistent focus on dependable services rather than one-off fixes.

Brisbane, Australia

Based in Brisbane, I bring seven years of IT experience into a DevOps-focused career at ADITS. I am especially interested in cloud platforms, automation, monitoring, and practical applications of AI that reduce repetitive work, improve productivity, and help teams make better decisions. For me, the value of AI is in using it thoughtfully to strengthen projects and systems—turning information into useful insight, accelerating well-defined work, and leaving people with more time for the problems that need human judgement.

Outside work, the homelab keeps that curiosity active—researching new releases, testing upgrades, and learning by building services that have to be maintained over time.

Let's talk

I am always happy to talk about DevOps, cloud infrastructure, automation, observability, or the lessons that come from building systems at home and supporting them in production.

If you are working on a platform problem, a practical automation idea, or a team that values reliable engineering, I would welcome the conversation.