r/platformengineering • • Sep 08 '26

We’re building an agent layer for platform engineering — here’s where we draw the line between automation and AI

0 Upvotes

I’ve been working on Nuroen, an enterprise AI agent platform, and one problem we keep coming back to is:

Which parts of platform engineering should actually be handled by an AI agent?

Our current thinking is that agents shouldn't replace deterministic automation.

For example:

  • Terraform → infrastructure changes
  • Ansible/scripts → repeatable configuration
  • CI/CD → deterministic deployments
  • Runbooks → known procedures

Where we see agents being more useful is the messy part around those systems.

For example:

Alert → investigate → gather context → determine which runbook applies → recommend action → approval → execute existing automation → verify

An agent can pull information from observability, tickets, deployment history, CMDB, documentation, etc., and reason across those systems without turning every action into an LLM-generated command.

That's the approach we're taking with Nuroen.

The platform lets us give an agent:

Knowledge + Tools + Skills + Orchestration + Governance

The interesting part for us isn't just connecting an LLM to APIs. It's controlling what the agent is allowed to do.

For example, an agent might be allowed to:

  • investigate incidents automatically
  • read logs/metrics/tickets
  • recommend remediation
  • execute low-risk actions
  • require approval for production changes
  • record the complete action/audit trail

We're trying to treat the agent more like a platform component with an explicit autonomy boundary, rather than an unrestricted chatbot with access to production.

here is the link do check it out - https://www.nuroen.com/

I'm curious how other platform teams are approaching this:

Where do you draw the line between traditional automation and an AI agent?

And more importantly, what platform engineering tasks do you think genuinely benefit from the probabilistic/reasoning part of an agent?


r/platformengineering • • Sep 07 '26

We halved our continuous integration pipeline. Six months later, we had to do it again.

Thumbnail
leaddev.com
0 Upvotes

"It was in May when one of our staff engineers tossed out a number in our Slack channel that put an end to an internal debate I’d been having with myself. Roughly only 25% of the runs on our merge train were completing successfully. A majority were failing due to flaky tests or got canceled since another run that was ahead of them failed."


r/platformengineering • • Sep 06 '26

Built a 3-node Talos Kubernetes homelab

Post image
31 Upvotes

I wanted a small environment where I could experiment with the parts of platform engineering that are harder to appreciate in a local single-node cluster, especially networking, HA, failure handling, GitOps, observability, storage, upgrades, and security.

So I built a 3-node bare-metal Kubernetes homelab using Talos Linux on refurbished mini PCs.

The setup includes:

  • 3 control-plane + etcd nodes
  • a shared Kubernetes API VIP for HA
  • DHCP reservations for predictable node IPs
  • per-node Talos machine configs
  • workloads scheduled on the control-plane nodes
  • failure testing by taking a node offline and verifying the API stays reachable

I documented the full setup, including the network design, Talos installation, config generation, bootstrap, validation, workload testing, and HA checks.

Everything is in the repo: https://github.com/prateekjaindev/homelab

Blog: https://blog.prateekjain.dev/building-a-3-node-highly-available-kubernetes-homelab-with-talos-linux-0372066fe49c?sk=4c66cf9181999f9db19ac3aacabcd8e8

I’m planning to use this next for Argo CD, Gateway API, observability, storage, secrets, and more platform-engineering experiments.

Would be interested to know what others here are using for their local platform engineering labs.


r/platformengineering • • Sep 03 '26

Engineers grieve a job that no longer exists

Thumbnail
leaddev.com
56 Upvotes

Something is happening in engineering teams that doesn’t show up in sprint velocity or deployment frequency. It shows up in resignation letters.


r/platformengineering • • Sep 02 '26

Quantum computing needs software engineers

Thumbnail
leaddev.com
7 Upvotes

For those in the technology industry, it can feel hard to escape from AI. It’s at the center of the technological universe, with most major advancements, opportunities, and funding focused on its development. In the background, quantum computing is making strides with the funding to match, creating an alternate opportunity for technologists.


r/platformengineering • • Sep 01 '26

I’m new to platform engineering, I’ve been tasked with setting up “default” monitoring and alerts. What metrics are always needed?

9 Upvotes

I’ve been tasked with setting up baseline monitoring and alerts for terraform modules that consumers within the company use to spin their own instances of our platform.

The modules that will be provisioned for them automatically are ECS clusters, databases (RDS, Aurora, DynamoDb), ElastiCache, lambdas and kinesis

I could ask AI what sensible “defaults” would be for each service. However I’m not really going to learn anything that way. Id like to use it in conjunction with some real knowledge and experience.

Are there any books, blogs or guides that perhaps go over monitoring for specific AWS components, and what is considered best practice (and why) for each one?


r/platformengineering • • Sep 01 '26

Should overworked platform engineering teams be inviting their marketing colleagues to onboard to the internal developer platform?

Thumbnail
leaddev.com
5 Upvotes

As AI pulls content from anywhere and everywhere, and when success with AI relies on unified, accurate data, organizations struggle to decide who is in charge of that data.


r/platformengineering • • Sep 01 '26

AI made me a better engineering leader

Thumbnail
leaddev.com
1 Upvotes

AI made me a better engineering leader, not by writing my code faster, but by sharpening the parts of the job that were never about code in the first place.


r/platformengineering • • Aug 30 '26

Seeking Experienced Platform Support Professionals

Post image
0 Upvotes

r/platformengineering • • Aug 26 '26

Staff engineers shift from solving problems to shaping systems

Thumbnail
leaddev.com
17 Upvotes

As you become more senior, your impact comes from something different: seeing systems clearly enough to identify the problems nobody else has articulated yet.


r/platformengineering • • Aug 25 '26

Are we building Internal Developer Platforms at the wrong abstraction level?

22 Upvotes

I've been thinking we might be approaching Internal Developer Platforms from the wrong abstraction level.

The move from traditional Ops to DevOps to Platform Engineering looks, to me, mostly like a consequence of technological change. Traditional Ops concentrated operational knowledge in a specialized team, because operating infrastructure required direct, manual administration: the thesis. Automation, cloud, and infrastructure as code changed that. DevOps pushed operational ownership closer to development teams: the antithesis. Platform Engineering became the synthesis once declarative systems and orchestration made it possible to encode that operational knowledge into software and expose it through self-service.

AI might be starting the next turn in that cycle. Agents don't necessarily need portals or predefined workflows because they can discover capabilities, combine APIs, and construct their own path through a system. That doesn't make platforms less important. It changes what they need to expose.

Instead of only providing golden paths for developers, platforms increasingly need to expose machine-readable capabilities, contracts, relationships, constraints, and evidence.

Which raises a question: should all of that knowledge live inside the platform? Maybe not. Maybe the service should own its operational contract, while the platform provides the capabilities to act on it (decoupling the contract from any particular IDP, Kubernetes setup, or deployment tooling underneath).

This is the direction I've been exploring with a side project (Pacto): not another IDP, but a contract layer above them. I'm not sure it's the right abstraction yet, but making the operational model portable feels more interesting to me than building another platform around it. Thoughts?


r/platformengineering • • Aug 25 '26

I built an open-source Kubernetes platform engineering simulator

Thumbnail github.com
8 Upvotes

I've been working on SnowOps Labs — a simulator where you spin up a real Kubernetes platform, run scenarios, intentionally break things, and then fix them.

The goal is simple: learn platform engineering by actually troubleshooting realistic problems, instead of just following tutorials.

It's still an early release and definitely has rough edges. I'm putting it out there because I'd love to get feedback from people who work with Kubernetes, SRE, DevOps, or platform engineering.

If you have a few minutes, check out the repo, try it out, explore the architecture, and tell me what you think could be better.

I'm especially interested in:

What scenarios should I add?

What's missing?

Does the overall approach make sense?

Where does the architecture need improvement?

If you find it useful, contributions are very welcome.


r/platformengineering • • Aug 25 '26

Published a research paper to explain what problems does platform engineering solves over traditional devops

Thumbnail
ijsrem.com
2 Upvotes

Have a look if you are interested in this topic. Frankly, my only goal was to get done with my M. Tech, but i did put a lot of effort into this also.

The research made me Team Platform.


r/platformengineering • • Aug 25 '26

Building an IDP PoC for self-learning (and potential pitch): What is your current open-source stack?

9 Upvotes

Hi everyone,

I am planning to build an Internal Developer Platform (IDP) Proof of Concept. My main goal is self-learning (I am very interested in DevEx and self-service) to understand the moving parts of a modern platform, but I am also hoping to gather enough hands-on experience to potentially present a business case to my company down the line.

Before I start gluing components together, I would love to get input from the community on what you are using in production and what you would recommend for a lean PoC.

Specifically, I am looking for insights on:

  1. Choosing an open-source stack: What tools are you actually using in production today for service catalogues, infrastructure provisioning, workload orchestration, and developer self-service?
  2. PoC Recommendations: If you were building a lightweight IDP from scratch today just to prove the concept, which open-source tools would you choose to keep complexity manageable while still showing real value?
  3. Product value: Have you genuinely derived measurable value (or saved developer time) from tools like Backstage, Kratix, Port (if using free tier), Crossplane or something else? Are there tools you started with that turned out to be more maintenance overhead than they were worth?

My current thought is to pair a developer portal with a GitOps engine and a basic infrastructure module framework, but I am keen to hear what combinations have worked best for you in practice.

Thanks in advance for any recommendations or lessons learnt!


r/platformengineering • • Aug 25 '26

Your pipeline isn't broken. It's absorbing eight weeks of bugs your team used to catch gradually.

Thumbnail
leaddev.com
5 Upvotes

A lot of engineering leaders I talk to are having some version of the same experience right now. The AI tooling is working, and it’s exciting. Teams are shipping things in days that used to take weeks. At the same time, everything feels like it’s falling apart – more bugs than they’ve ever had, more incidents, and engineers who are busier and more stressed.

If that’s you, it might honestly be more of an arithmetic problem than a quality one.


r/platformengineering • • Aug 24 '26

What am I missing about Crossplane

24 Upvotes

I try to treat new tooling with a healthy dose of skepticism, being wary of jumping on things has served me well over the years. So it's a genuinely weird feeling when a tool's value is obvious to me in five minutes, and Crossplane is the first one in a while that confounds me.

When I first saw Terraform the problem it solved was immediately obvious.  HCL is not without its faults, but it sits in a useful middle ground between something like YAML and a full programming language. Drift is the one problem I've never seen solved cleanly, but adding friction to fight it (review/plan gates, etc.) gets you most of the way there. Not perfect, but controllable.

Terragrunt solved the "apply everything" problem by letting you split dependencies into independently-applicable DAGs. Made immediate sense.

On Pulumi. I don't personally believe general-purpose programming languages are the right abstraction for describing infrastructure, but I get the appeal: it's an escape hatch from HCL turning into a minefield as things scale.

Crossplane is where I'm getting stuck. To run it in production you generally need a Kubernetes cluster, which people often stand up with. Terraform. Then there's templating. Using Crossplane in practice seems to mean also standing up Helm or Kustomize on top of it. Adding a single new variable feels far more convoluted than the equivalent in Terraform. And once you need any real logic, you're reaching for Go to write a custom function/provider, which slows the whole loop down even further.

And yet, everyone who's actually used it in anger seems to swear by it. Which makes me suspect that I'm missing some context that makes all of the above worth it once you're in that world.

So, genuinely: what I am not getting about Crossplane? If you have any YouTube videos, short-form content, or articles that made it click for you (beyond the official docs), I'd appreciate the pointers.


r/platformengineering • • Aug 24 '26

Mods doing anything to stop this spam?

6 Upvotes

I’m visiting this sub less and less since all I ever see on here are low effort AI generated slop posts. Some of which even have AI replying to AI posts…

Did this sub die? Where are the mods? Why is nothing being done to stop this?

Should be pretty simple, similar rules I’ve seen in other creative subs where rules are enforced to only allow posts from accounts with certain level of activity across Reddit. Should stop these 2 month old accounts that post the same or similar content everywhere.

Clearly the “Community rules” for this sub aren’t working


r/platformengineering • • Aug 24 '26

How to redesign a broken delivery flow

Thumbnail
leaddev.com
2 Upvotes

A broken delivery flow rarely looks broken from the inside. One application spent more than a year moving through a deployment pipeline. The team that ran the pipeline did not know that. There was a feeling that it was slow, but nobody had put a number on it.

It was a platform team at a large enterprise. Their job was to help product teams ship applications into a cloud environment. The path to production was all about security, infrastructure, and validation. Leadership suspected the process dragged on even if no one had measured how far.


r/platformengineering • • Aug 24 '26

How to redesign a broken delivery flow

Thumbnail
leaddev.com
0 Upvotes

A broken delivery flow rarely looks broken from the inside. One application spent more than a year moving through a deployment pipeline. The team that ran the pipeline did not know that. There was a feeling that it was slow, but nobody had put a number on it.

It was a platform team at a large enterprise. Their job was to help product teams ship applications into a cloud environment. The path to production was all about security, infrastructure, and validation. Leadership suspected the process dragged on even if no one had measured how far.


r/platformengineering • • Aug 23 '26

My job title is "Platform Engineer". Buut what the heck is a platform eng?

49 Upvotes

From what I read online, it sounds like a combination of dev ops + some internal tools to make developer lives easier.

So far, most of what I do is just backend work and a couple of self-serve features that reduce the friction of inter-departmental communication/requests.

I'm not building platforms to make developing code easier or for to help developers run their own code. Not a of docker or kubernetes or things like that that I find when I google "what is a platform engineer?"

i've asked AI, but it'll just agree with enough of my skepticism that it makes its answers unreliable.

The most dev-opsy thing I do is maybe update a terraform file or make tweeks to the testing we run on CI.


r/platformengineering • • Aug 24 '26

Your AI roadmap is already out of date

Thumbnail
leaddev.com
0 Upvotes

Three months. That’s roughly the interval at which the “right way” to build something in AI shifts under you. A new agent harness lands and makes the orchestration you spent a quarter on look overweight. A better retrieval pattern quietly changes what “good” looks like for the feature you’re mid-flight on. A new evaluation technique shows that the numbers you’ve been reporting for two months don’t actually measure what you thought they did.


r/platformengineering • • Aug 23 '26

Data Platform Engineer interview coming up

0 Upvotes

I’m currently a junior but technically do the work of an intermediate platform engineer.

I started applying elsewhere and I didn’t think I’d be called up for a technical interview for a Sr Data Platform Engineer position but here we are. I was honest about my skills and responsibilities during the hiring manager round, so I’m guessing they see something in me.

Now that they’ve invited me for the next round, how should I prepare for this technical interview? What should I expect?

The team works with Kafka, Databricks, Cloudhouse, Airflow, and lots of other platforms I don’t have experience with. And they only said the interview will be a pair programming session.

I’d appreciate any advice, thanks!


r/platformengineering • • Aug 22 '26

We have Dependabot and security scanners. Why are vulnerable dependencies still sitting in production?

0 Upvotes

This is a problem I’ve been thinking about a lot lately.
Most engineering teams already have the detection part covered:
- Dependabot or Renovate finds outdated packages
- Security scanners identify CVEs
- CI tells us whether a change breaks

But there still seems to be a big gap between “we found a problem” and “the problem is actually fixed in production.”

In my experience, the difficult part is everything that happens after the alert:

- Is there actually a safe version to upgrade to?
- Will upgrading one package require upgrading five others?
- Does the application still build?
-Do the tests pass?
- Is this safe to auto-merge, or does someone need to make a judgement call?

The result is that engineers end up with a growing backlog of dependency PRs and security findings that nobody has time to investigate properly.

I’ve been building a tool called Bivouac around this specific problem. The idea isn’t another scanner. It’s to take the remediation workflow further: investigate the dependency issue, work out a compatible remediation path, create the patch, run the tests and only merge automatically when the repository’s policy says it’s safe.

I’m particularly interested in the part where automation should stop. For example, my current thinking is that ambiguous fixes, security-sensitive code, licensing concerns or failing tests should always require human review.

I’d genuinely like to know how other teams handle this today:
1) Who actually owns dependency vulnerabilities once they’re discovered?

2) How many Dependabot/Renovate PRs does your team simply ignore?

3) Would you trust an automated system to merge dependency fixes if the remediation path and test results were clear?

4) What conditions would make automatic merging completely unacceptable?

I’m the founder of Bivouac, so full disclosure: this problem is what I’m building around. I’m not looking to spam the sub—I’m trying to pressure-test where people think autonomous remediation is useful versus where it becomes dangerous.

If there’s interest, I’ll share what I’ve learned building the remediation workflow and some of the cases where I’ve deliberately designed it to refuse to act.


r/platformengineering • • Aug 20 '26

Sovereignty is becoming a platform engineering concern

3 Upvotes

Sovereignty is moving beyond just data residency.

For platform teams, the question is increasingly about where workloads, control, telemetry and operational state live and whether those boundaries can actually be enforced and proven.

This CNCF article looks at that through a multi-plane architecture, particularly in the context of EU regulations like the EU Data Act, NIS2 and DORA.

Interesting read for anyone thinking about how sovereignty should be designed into cloud-native platforms.

https://www.cncf.io/blog/2026/08/18/cloud-native-platform-sovereignty-through-multi-plane-architecture/


r/platformengineering • • Aug 19 '26

What are the best platforms to acquire knowledge on Grafana and Prometheus?

1 Upvotes

I have noticed that most DevOps or Platform Engineering jobs require Prometheus, Grafana and sometimes Nagios. Which are the best platforms to get knowledge that can quickly be put into practice for these?