Selected Projects

View all on GitHub

A few things I’ve been building around infrastructure, Terraform, and tooling.

Glyphra

AI-assisted infrastructure summariser and tooling playground. Long-term goal: help teams understand Terraform plans, drift and tagging conventions more easily.

Go · Terraform · Infra summarisation

GitHub ↗

Terradendro

Experimental Terraform plan visualiser and diff classifier, with Markdown exports for plan reviews and change documentation.

Go · Terraform · DevEx

GitHub ↗

Inori (language experiments)

A long-term language design side quest exploring pipelines, templating and infra-adjacent computation, inspired by type theory and category theory.

Language design · DSLs

Experiments ↗

gitorch

Local Git hygiene CLI to surface divergence, stale branches and repo health so you don’t accidentally ship from a haunted feature branch.

Go · Git tooling

GitHub ↗

Infrastructure Hermeneutics

A working lens for interpreting operational systems.

Infrastructure Hermeneutics is a way of approaching operational systems that treats failures, metrics, abstractions, and tooling as signals to be interpreted rather than merely optimised.

It assumes that many operational incidents stem from mismatches between declared system behaviour, observed behaviour, and the shared understanding held by teams.

The practice focuses on making those mismatches visible through interpretive artifacts — such as annotated plans, narrative postmortems, and explanation-first tooling — so teams can reason about systems collectively and adjust their abstractions over time.

This is not a delivery methodology, but a technical lens that can be applied alongside DevOps, SRE, and platform engineering practices.

Now

Inspired by the /now page idea – a quick snapshot of what I’m focused on right now.

  • Consulting on AWS landing zones, CI/CD and platform reliability.
  • Building and refining infra-focused tooling in Go (Glyphra, Terradendro, gitorch).
  • Exploring Rust and language design ideas through Inori.
  • Writing about infrastructure, cost, and ideology on Substack.

Professional Overview

Download CV (PDF)

Danny Molnar – AWS Consultant / Cloud & Platform Engineer based in London, UK. I work mainly on landing zones, infrastructure automation, and developer tooling across AWS (and occasionally GCP).

Professional Summary

Cloud and Platform Engineer with experience designing and operating large-scale AWS environments, landing zones and CI/CD platforms. I specialise in Terraform/Terragrunt, GitOps, cost optimisation and observability, with a strong bias towards automation, repeatability, and developer experience. I enjoy building small tools (mostly in Go) around infrastructure to make complex systems more understandable and safer to change.

Experience

Currently working as an AWS Consultant / Platform Engineer, helping teams design and operate secure landing zones, CI/CD pipelines and cloud-native platforms (GitLab, Kubernetes, observability stacks, FinOps dashboards).

Previous work includes cloud platform engineering and DevOps roles across consultancy and enterprise environments, focusing on infrastructure-as-code, migration projects, and improving deployment reliability.

Tech Stack

  • Cloud: AWS (primary), GCP experience
  • Infrastructure as Code: Terraform, Terragrunt, Terratest
  • Platform / CI/CD: GitLab, GitHub Actions, Jenkins
  • Configuration Management: Ansible
  • Containers & Orchestration: Docker, Kubernetes, k3d/kind
  • Programming: Go, Python, JavaScript/TypeScript
  • Observability & Monitoring: Prometheus, Grafana, CloudWatch
  • FinOps & Cost Insights: AWS CUDOS / CID, Budgets, Compute Optimizer
  • OS & Tooling: Linux, Bash, Nix (exploring)

Currently Exploring

  • Deeper Go backend/tooling patterns
  • Rust and systems-adjacent tooling
  • Language design experiments (Inori)
  • GitOps and progressive delivery
  • ML / Agent-style automation around infra
  • Advanced Kubernetes & home-lab setups

For a detailed overview of my professional background, you can read my full CV.