About
Real architectural decisions for senior engineers and platform architects working across Azure, AWS, and GCP.
Every video starts with a decision. Not a feature demo. Not a getting-started guide. A real architectural decision with real trade-offs.
Platform Decisions exists because most cloud content stops at the surface. It shows you how to create a resource, not why you'd choose one architecture over another — and not what breaks when you get it wrong at scale.
This channel covers the decisions that define whether a platform is maintainable in three years or a liability. Private networking, identity, landing zones, Terraform at scale, CI/CD, cost, and AI agents in infrastructure — treated with the seriousness they deserve.
Every video ships with a GitHub repository. Not a sanitised demo — actual infrastructure code you can fork, adapt, and run in your own environment. The goal is to leave you with something you can take into a design review on Monday.
Host
Platform Decisions
Cloud & Platform Architect
Platform Decisions is run by a cloud and platform architect with experience designing and operating infrastructure at enterprise scale across Azure, AWS, and GCP. The work spans private networking, identity federation, multi-cloud landing zones, and platform engineering toolchains.
The channel came from a simple frustration: the gap between what cloud vendors document and what actually works when you have 50 teams, a security team with opinions, and a platform that needs to last. These videos are the conversations that should happen in every architecture review — but often don't.
Every video opens with a real architectural decision — the kind that lands in a design review or a Jira ticket. Not a feature walkthrough.
Decisions look different at scale. We model them against real constraints: blast radius, security posture, team topology, and cost.
Every video has a GitHub repository with infrastructure code you can fork, adapt, and run. Not a demo — something you can actually use.
If something is complex, we go through it. If there are gotchas, we name them. The goal is to leave you better equipped, not just informed.