Perhaps it's just confusing to people like me, who don't work on "platform engineering teams". The sentence is just too packed with terms I have no analogy for.
The best analogy I came up with is "It's like kubernetes and jenkins had a baby."
Nah, I worked on a "platform engineering team"/DevOps for a year and I have no idea what this service does or what it's for. I have a vague inkling, like I could make a guess, but even thinking about that makes my head hurt.
Probably relevant tho is that I left after a year and am no longer doing DevOps because C/C++ low level mathy or systems oriented coding is fun, and actually makes sense to me. :)
I don't really see the problem with that - you probably aren't the target audience. Good tools will frequently be specialized. You could probably understand the initial blurb for React or some library in whatever your speciality is that may just be confusing to a "platform engineer".
The best analogy I came up with is "It's like kubernetes and jenkins had a baby."