r/platformengineering • • Mar 21 '26

Looking for Mods

11 Upvotes

Hello, after the recent change in the mod team, r/platformengineering is now actively managed. We are reducing spam and increasing the sub’s activity. As a result, r/platformengineering has grown from 3k to 6.3k members over the last 45 days. We would like to keep this momentum and are recruiting another member for the mod team.

We need someone who can:

- post or encourage engaging content
- moderate fairly (no bias, consistent decisions)
- active on Reddit (daily or near-daily)

Send Mod mail if you are interested.


r/platformengineering • • 31m ago

I built a game to learn kubernetes - Night Shift

Thumbnail
play.snowops.net
1 Upvotes

I have been working on multiple projects and one thing I felt was the biggest challenge for adoption. Setup time. If something takes up more than 5 minutes, you lose 90% of your potential users.

For this, i created a browser game which helps you learn real world kubernetes incidents within your browser. It's free and no setup required.

All the results are from logs of my another project - Snowops Labs. So, everything you will get is real.

It teaches you how the real engineering team works and gives you real incidents to solve and learn.

I'd genuinely like to hear what experienced engineers think. Especially if you've spent time troubleshooting production incidents.

TL;DR: An attempt to make practical DevOps troubleshooting more interactive and game-like. Give it a try and tell me what you think.


r/platformengineering • • 1h ago

Shutting down the whole platform to stop an attacker: what we revoked, rebuilt and brought back first (Bitrise incident review, with IOCs)

Thumbnail
bitrise.io
1 Upvotes

r/platformengineering • • 13h ago

how do you decide when a team really needs an internal developer portal

6 Upvotes

we keep seeing teams jump to backstage or something similar as soon as there are 10 services. my gut says it only pays off once people actually waste time hunting for owners, docs and runbooks, and before that a good readme template and a simple service list does most of the job. where is the line for you, number of teams, number of services, or just the pain of onboarding?


r/platformengineering • • 7h ago

Who owns policy orchestration once you have dozens of accounts?

1 Upvotes

Writing a guardrail is the easy part. Rolling it out across lots of accounts and OUs, with exceptions, without breaking someone’s deploy on a Friday, seems to be the actual job. That policy orchestration piece is what I’m curious about.

How do you handle it? Guardrails in Terraform with a PR review from security? A dedicated platform team? Rollout to a test OU first, then wider? And where do exceptions live so they don’t turn into permanent holes?

Blast’s angle is compiling security principles into native cloud guardrails and testing the business impact. Act Security tends to start from which access each workload actually uses and builds the policies from there. Should be upfront that Act is one of the companies my agency works with.

Mostly interested in the people and process side. Who gets paged when a guardrail blocks prod?


r/platformengineering • • 7h ago

who gets the vuln ticket when the app and base image have different owners?

1 Upvotes

say platform owns the base image, the app team has to rebuild and deploy it, and CODEOWNERS still points at the team that had the repo before the reorg. so the ticket bounces.

for people routing findings with Nucleus, Rival, or homegrown rules, who gets the first ticket? the team that can patch the image or the one that can get the fix into prod?


r/platformengineering • • 9h ago

Canary analysis on a thin metrics budget, worth it or just put tracing back?

1 Upvotes

We moved our Spring Boot services off New Relic to self-hosted Prometheus and Grafana and dropped most custom tracing. Then a release went out, rollout status green, 5xx flat, but one code path was failing inside a try/catch and returning a fallback. Rollback was easy. Finding the commit took a day.

Team’s split. Half want OpenTelemetry tracing back. Half want a canary step. Flagger and Spinnaker’s Kayenta both read the metrics we already have, and the one we needed didn’t exist. Hud counts calls and exceptions for every function, caught ones included, so nobody has to define the metric first.

Anyone pick rollout verification over rebuilding tracing and not regret it?


r/platformengineering • • 1d ago

Coding agents on laptops vs. on the cluster: a platform team’s view

4 Upvotes

Most teams let each developer run coding agents locally, which means no inventory, no consistent permissions and no cost attribution for the platform team. This post argues for running them as governed workloads on Kubernetes (security, reproducibility, scale, observability) and is explicit that Kubernetes doesn’t make them secure by default.

https://www.okteto.com/blog/why-run-ai-coding-agents-on-kubernetes/

Disclosure: I’m the CTO at Okteto.


r/platformengineering • • 1d ago

After a cloud scan, what actually gets the findings fixed in your team?

1 Upvotes

I posted a small open-source Azure scanner in r/AZURE this week. The best comments weren't about detection at all. They were about what happens after:

  • A CLI fix on a resource managed by Terraform gets reverted on the next terraform apply.
  • A flat list in severity order isn't a plan. Rank by what's actually exposed.
  • Someone doubted that teams even merge automated PRs.

I'm not asking you to try anything. I'm trying to learn what makes fixes actually land:

  1. When a scanner or Advisor flags something, who fixes it, and what makes it actually happen? Tickets, PRs, or someone chasing it in a weekly review?
  2. If the resource is in Terraform, would you want a patch or PR, or just the finding plus the Terraform address?
  3. Does your org really keep owner tags on resources, or is the resource group name the better guess at who owns it?

For context, here's what mine does today. For 16 of its 60 checks, it writes one script per resource with the risk, expected downtime, a rollback and a verify step. Every command is commented out, so a person reads it and enables it. The newest version groups findings by owner (from tags, falling back to the resource group) and ranks a short "fix first" list by whether a resource's own settings allow connections from the Internet. It's a ranking aid, not attack-path analysis.

Disclosure: I build it. It's free, Apache 2.0, and read-only: https://github.com/skyvedahq/skyveda


r/platformengineering • • 1d ago

howw are you reviewing MCP servers before letting devs use them???

3 Upvotes

Devs want to hook up a few MCP servers, GitHub, Jira, our internal docs. Security wants a review before anyone touches them and of course I got volunteered to write it.

What I’ve got so far: who maintains the server, what the tools can actually do, where creds live, what data and network access it needs, and whether we can log calls and pull access fast if something’s off. Plus someone has to actually own it after it’s approved, otherwise it just rots.

Been poking at Capsule and Lasso too but I honestly don’t know yet how much of this they’d cover vs what we’d still have to check ourselves.

What am I missing? And how are you keeping this from turning into a weeks-long approval queue for every server?


r/platformengineering • • 2d ago

Moving from CI work into Kubernetes roles?

5 Upvotes

In my role, I build reusable CI templates and policy gates, and we own code scanning and the artifact repository. My team also owns and runs the CI runners on Kubernetes.

I’d like to end up in a role with low-level Linux and Kubernetes work: nodes, scheduling, debugging production systems. Is that realistic from here, or would it be hard because of my current focus? Or more generally, how realistic is it to move from my delivery-focused work into runtime infrastructure roles or am I locked into the former?


r/platformengineering • • 3d ago

Moving coding agents from personal terminals into shared team channels: what we had to build

0 Upvotes

Disclosure: I work on AgentConnect. This is a write-up of how our own team uses it.

We’re fewer than ten engineers, running around thirty agents: one generalist for everyday engineering requests, plus specialists for cluster checks, alert investigation, code review, releases, upstream fork maintenance and customer support. Each specialist has its own repositories, tools, channels and schedules, with permissions scoped to its job.

Initially, everyone had their own scripts, schedules and credentials. We were duplicating the plumbing, and investigation context stayed in whoever’s terminal ran the task.

Moving agents into Slack threads made investigations visible to teammates, but introduced problems our first bots weren’t built for: picking up earlier messages, keeping workspaces separate, surviving restarts and preventing bots from triggering each other.

Permissions needed more than ‘can this person message the bot?’ We separated who can use an agent, which repositories and tools it can access, and who can read its sessions. Private-channel context and memory stay scoped to that conversation’s audience.

We kept the existing coding harnesses so engineers can reproduce channel behaviour locally. For fork maintenance, agents prepare changes and checks; people merge and publish.

Full write-up

For teams putting agents into operational workflows: how are you handling shared investigation context without making private conversations or privileged tools accessible to everyone?


r/platformengineering • • 4d ago

I built a free tool to find the minimum IAM role in Azure, AWS and GCP, plus a reverse lookup by action

Post image
4 Upvotes

Working in multi-cloud, I kept ending up with three tabs open, two reference docs, and still guessing whether a role was least-privilege or way too broad.

The hard part is never finding a role. It's knowing exactly what's inside it without reading hundreds of JSON/YAML policies. And the other way around: "which roles grant this specific action?" is surprisingly painful to answer.

So I built whatroledoineed.com:

- Intent-based lookup: pick a resource and what you want to do (read / write / assign / delete) and get the minimum role back
- Reverse search: type an action and instantly see which roles grant it
- Browse the built-in role catalogs of Azure, AWS and Google Cloud (in development) and inspect the actions each role includes

It's free and launched a few days ago (available in English and Spanish).

I'd love honest feedback from people who deal with IAM daily:
- Does the intent-based lookup return the role you'd expect?
- Is the reverse search useful in your workflow, or do you already solve this another way?
- Anything missing or wrong in the catalogs?

There's a feedback button inside the app too. Roast it if needed 🙂


r/platformengineering • • 4d ago

Are AI agents transforming Dev and Ops jobs differently?

0 Upvotes

I have the feeling that AI agents may not transform Dev and Ops jobs in the same way.

For Devs, writing code themselves is a central part of the job that is now being challenged. For Ops, it seems more like another level of abstraction, as the job is already largely about orchestrating automation.

I wonder if others share this view, or if I'm oversimplifying things.

I'm currently Ops, previously Dev.

Short essay here: https://cl3don.substack.com/p/dev-and-ops-facing-ai


r/platformengineering • • 6d ago

Platform folks: who owns “prove what’s in our software” at your company?

0 Upvotes

Quick disclosure: grad student (NYU), doing a class case study with a software supply-chain startup. Not selling anything, just trying to learn.

I spent 8 years as a frontend-biased software engineer and never really owned this problem, but I’m now hearing it lands on platform teams a lot. Customers in healthcare, finance or the EU (CRA) ask for SBOMs or security evidence, a big CVE drops, or someone needs to swap out a deprecated library, and suddenly the question is “where is this used and can we prove it?”

Curious how it works on your team:

  • Is this actually the platform team’s job where you are, or does it sit with security?
  • When a customer or auditor last asked for evidence, how painful was it to pull together?
  • Has more AI-generated code made dependency tracking harder, or no real change?

Would love to hear real experiences (including if this never comes up for you or your team), the messy ones especially. Happy to share a summary of what I hear back here.


r/platformengineering • • 6d ago

Claude Code touched a helper, two AI reviewers approved it, and our Kafka consumer fell over.

0 Upvotes

Python shop, Django plus a few Kafka consumers. Claude Code refactored a date parsing helper as part of a bigger PR. CodeRabbit and Greptile both reviewed it, no complaints, a human skimmed it, merged. Turns out that helper is also called inside our highest volume consumer and the new version does an extra db lookup per message. Consumer lag went vertical an hour after deploy. Nothing in the diff told anyone that function sits on a hot path, the reviewers read the diff and the diff looked fine. Someone on the platform team has been pushing hud because its PR check lists the functions a change touches with how much traffic they carry and who calls them, so the reviewer sees “this is called from the consumer” before merge. Haven’t rolled it out. How are others catching this, is it just better tests or do you actually feed production call data into review?


r/platformengineering • • 6d ago

Design review: a shell as the self-service interface to a platform, where every default is visible through explain. Is this a golden path or a footgun?

0 Upvotes

I'm designing Convoy Fleet Manager, a POSIX-like shell over Kubernetes, and I'd like platform engineers to review it before any code exists. The pitch to developers is "use the verbs you already know". The pitch to platform teams is "you set the defaults, and your users can always see them".

How it splits the work between the platform team and its users:

  • The platform owns the defaults. Storage classes, queues, packages, budgets, the release path, the provenance each environment requires, whether debugging is allowed: all of these are platform settings. Every command's explain prints the defaults it picked up and where each came from, so "why did my job land there" has an answer without a ticket.
  • Profiles are per environment. A test mount can accept images built in the cluster (provenance: session), while production accepts only CI-attested digests, refuses debug agents, and with release_diff=refuse refuses a release whose plan differs from where the digest last passed.
  • Groups own things, people act. Objects belong to groups, and processes run as svc:<group>. The person is recorded as the actor on every receipt.
  • Approvals are objects, not chat buttons. A policy (say, release to prod-*) creates an approval on the process. It pins the explain output it shows the approver, and only a different person can answer it, from their own session.
  • Cost is part of the plan. It's a band at plan time, a column in ps while running, and a receipt at the end that tightens the next estimate. Budgets are enforced at plan time, not discovered on the bill.
  • There's a typed escape hatch. Unknown commands still run, on one node, and explain says why. Nothing is blocked for lack of an annotation, but nothing gets parallelized by guessing.

It's design-only. The repo has 22 ADRs, nine workload walkthroughs and 24 persona-driven user stories (SRE, platform engineer, data engineer, ML engineer, auditor, app developer...). Their 181 findings have each been applied, drafted or accepted.

What I'd like from this community:

  1. Does a shell belong in an internal developer platform next to Backstage-style portals and golden-path templates, or does it undercut them?
  2. Is "every default is visible and attributed" enough governance, or do platform teams need defaults the user can't see?
  3. Who should own the command annotation database (which commands can be split, how their outputs merge): the platform team, the tool authors, or both?
  4. Would you hand the cost band and budget enforcement to a shell, or keep them in FinOps tooling?
  5. What's missing for you to offer this to your users?

r/platformengineering • • 7d ago

Benchmarked 10 LLMs on writing reusable OpenTofu modules for AWS/GCP/Azure: open-source harness, data, and results

12 Upvotes

Just because AI-generated infrastructure passes tofu plan doesn’t mean it would survive an org’s compliance, cost, or scale requirements.

We had 10 models each write 9 reusable OpenTofu modules (90 total) across AWS (S3), GCP (Cloud SQL Postgres), and Azure (App Service). Almost everything planned cleanly. No syntax errors, very few failed plans. But:

S3 access log delivery was missed in 30 of 30 attempts. Every model, every time.

Cloud SQL would drop the database on removal in 24 of 28 attempts. Take the DB out of the inputs and your data goes with it.

25 of 90 attempts failed at least one mandatory security item. 6/30 S3 modules didn’t guarantee the public access block, 9/28 Cloud SQL modules didn’t require encrypted connections, and 10/28 App Service modules left basic-auth publishing on.

Only 32/90 fully validated their inputs, and 26/90 shipped docs containing false statements about what the module does.

Provider version constraints allowed the next major version in 19/30 AWS and 22/28 GCP modules.

How it was scored: 70% mechanical checks against real tofu plan output, 30% LLM judge grading against a published 14-section quality doctrine. Nothing was applied, only planned.

The obvious objection: the judge is Claude Opus 5.5, and Opus came out #1. Two things on that. First, the judge had to agree with a human grader on at least 6 of 8 modules in every section, and GPT-5.5 failed that calibration, so it wasn’t used. Second, if you rank by the mechanical score alone, the order doesn’t change. The top four (Opus 5.5, Fable 5.1, GPT-6 Astra, Sonnet 5.5) have overlapping confidence intervals, so treat them as a tie.

Some other things that stood out:

GPT-6 Luna came 6th with zero security failures, at about $0.005 per attempt.

Gemini 3.6 Flash failed security items in 8 of 9 attempts.

Kimi K3 was the best open-weight model (5th), but 4 of its 9 attempts had security failures.

Full disclosure: I work at Massdriver, which ran this. The harness is Apache-2.0 and the data is CC BY 4.0, so you can rerun it, add your own checks, or tell us where the methodology is wrong. We’d like to hear that.

Rankings: https://www.massdriver.cloud/llm-rankings

Methodology: https://www.massdriver.cloud/blogs/iac-bench-2026-10-methodology

Repo: https://github.com/massdriver-cloud/iac-bench/tree/2026-10

Raw results + generated code: https://github.com/massdriver-cloud/iac-bench/tree/2026-10/results/2026-10

Quality doctrine we graded against: https://github.com/massdriver-cloud/iac-bench/blob/2026-10/docs/good-opentofu.md

I’m curious whether these match what you’re seeing with AI-generated IaC in your orgs. What would you add to the checks?


r/platformengineering • • 7d ago

Is post release verification worth its own line item or is that just your APM again?

2 Upvotes

We took a chunk out of the New Relic bill this year by cutting custom instrumentation and dropping some boxes to infra only. Nobody complained for a while. Then a deploy went bad on one of the services we’d thinned out and we had almost nothing to go on, so it turned into a log reading exercise and a long night.

What I can’t work out is whether the answer is buying back the instrumentation we cut, or buying something that watches the rollout itself. Harness and LaunchDarkly both do the guarded rollout thing off metrics you already send. Hud goes at it from the function side, so you aren’t picking metrics up front. Different money, different data leaving the building.

Has anyone actually swapped more APM for verify the deploy and been happy about it? Or did you end up paying for both anyway?


r/platformengineering • • 8d ago

Practice Real Production Outages

0 Upvotes

Disclosure: I built this.

Most of us learn incident response live, in prod, with everyone watching. I wanted somewhere to practice first, so I built Outage Gym.

How it works: a small production stack runs on your laptop with Docker: a service, a Postgres database, real traffic that keeps coming, and dashboards. Something is broken. You find the root cause, ship a fix (code, database or both), and keep "support" updated in an #incident channel while the clock runs. The system itself confirms when it's actually fixed and stays fixed. Nobody tells you where to look.

First problem: it's the first week of term, thousands of students are logging in, and the student service starts to drag. Some pages never load. No deploy, nobody touched the servers. It takes about 30–60 minutes.

Free to start: https://outage-gym.com


r/platformengineering • • 11d ago

Career choices: Platform engineer vs Swe

3 Upvotes

Hey all,

I'm having trouble landing interviews. I know the job marker is bad but i also suspect my resume isnt selling me well. For context, i come from a SWE (backend focused) background. I lost my job early this year, and decided to upskill. I built projects while learning and I do use them in my portfolio. Ive been applying to devops and platform engineering jobs but all i get is rejections. I thought my 5yrs experience in SWE was an added advantage.

Granted, in those 5 years i haven't exclusively worked as a devops/platform engineer but my roles kinda overlapped and so occasionally have handled devops tasks. I have reframed my resume to reflect my devops experience and backend engineering but still i'm not landing interviews. Yeah sure i'm not senior level perfect in platform /devops engineering but i can make a good mid level.

Would it be better if i just completely ignore devops/ platform engineering and just apply to backend engineering.


r/platformengineering • • 11d ago

AI makes content reproducible. I built a pipeline that does the same for the mobile architecture itself. Let’s talk about the future of development

0 Upvotes

AI has successfully automated a significant part of software creation. But what about the deployment and infrastructure stage? Here is a reproducible process that takes a technical specification and outputs a finished, standalone native mobile platform—independent apps for both iOS and Android driven by a unified backend — in about two hours.

This is strictly a Self-Hosted solution, not a SaaS or a drag-and-drop app builder. Every single output is a genuine native product with its own codebase, deployed directly onto the recipient's server under their absolute control.

There are two fundamental questions where I require raw feedback from engineers and practitioners:

  1. Does transitioning from the traditional "every app is a separate development project" model to a reproducible production pipeline reshape mobile engineering as a discipline?
  2. Does this level of structural automation threaten developers, or does it finally free them from routine to focus on building truly unique functionality?

r/platformengineering • • 12d ago

Preparing for a master’s dissertation on Platform Engineering / IDPs — where should I start?

4 Upvotes

Hi everyone! I’m starting a dissertation internship in February focused on Platform Engineering. The goal is to design and build an Internal Developer Platform (IDP) prototype for a development team.

The platform should provide self-service workflows for tasks such as creating projects from templates, provisioning infrastructure, and deploying applications. The dissertation will involve:

  • Researching Platform Engineering principles and Developer Experience.
  • Defining a use case and designing a modular architecture.
  • Building a prototype, potentially using Backstage, Terraform, and Kubernetes.
  • Enabling features such as project generation, deployment, and monitoring.
  • Documenting the platform and evaluating its usefulness and usability through developer feedback.

The focus is on reducing repetitive work and cognitive load through reusable components and golden paths. The tools mentioned in the proposal haven’t all been confirmed as mandatory.

My background: I code in Python and have used GitHub and GitLab, but I don’t have hands-on experience with Linux, Docker, Kubernetes, Terraform, or building internal platforms.

I have until February to build a foundation before the internship starts. I’m looking for a structured learning path with beginner-friendly explanations and practical exercises. I’m willing to pay for suitable training and have been considering KodeKloud and TechWorld with Nana’s DevOps Bootcamp.

For those working in this area:

  • What would you prioritise learning, and in what order?
  • Which course or learning path would you recommend for someone with my background?
  • What small practical project would help me connect these concepts?
  • What would you consider a realistic scope for an academic IDP prototype?

I’d appreciate any advice, especially from people who started with a similar background or have built an IDP!


r/platformengineering • • 13d ago

Our homegrown MCP gateway let a read only agent write, and nobody owned it.

2 Upvotes

It went on for three weeks in our ticketing system before anyone noticed, and when we did nobody could say who the agent belonged to or who it was acting for. Every agent reaches servers through an MCP gateway I wrote in Go over two weekends. It knows tokens and routes but nothing about owners, and now it fronts 23 servers through a yaml policy file nobody wants to own.
Classic case of not seeing the forest for the trees, we built agent access control around reachability and skipped AI agent identity.
A teammate mentioned in standup that the MCP spec now has enterprise managed authorization, which could remove some auth plumbing, though it does nothing for AI agent ownership.
I read newcore’s post The MCP Gateway Had a Good Run, and sure, a vendor would say identity matters more than routing, but it stung a little.
Then again, remember Simon Willison’s lethal trifecta post from last year? One agent with the wrong mix of tools is a problem no matter who owns it. For teams that sorted this out, did you give agents their own identity and owner before picking tooling, and what would you do differently? I feel pretty dumb asking, but appreciate any thoughts.


r/platformengineering • • 14d ago

Devenv local ci for Ai agent

0 Upvotes

Hello!

I've written a small series to explain how we moved from GitHub action to local ci with devenv with few tricks to make our bill lower and ci faster : https://etienne.deneuve.xyz/en/thinking/2026-10-09-ia-accelere-code-ci-doit-suivre-en/
I would love to have feedback on this !

How you manage this on your end ?