Platform Ninjas — Community for Infrastructure Engineers

// who is this for

You belong here if...

You spend your days making infrastructure invisible — and you want a community that actually gets it.

Platform Engineering

You're building the internal platform your developers actually want to use

IDPs, golden paths, Backstage, self-service infra — and the constant battle between abstractions that help and ones that just add layers.

DevOps / CI-CD

You're the one who cares about pipelines when no one else does

GitOps, release strategies, deployment automation — the craft of getting code from laptop to production safely and fast.

SRE

You measure reliability in nines and fight toil with software

Error budgets, SLOs, incident retrospectives — and the perpetual challenge of making reliability a feature, not an afterthought.

Cloud & Infrastructure

You architect the systems that everything else runs on

Cloud cost, Kubernetes at scale, Terraform, security posture — the unglamorous work that keeps the internet running.

AI Infrastructure

You're figuring out how to run ML workloads without breaking the bank

GPU scheduling, MLOps pipelines, model serving at scale — the new frontier where infrastructure decisions have never mattered more.

Learning & Growing

You want honest answers, not Stack Overflow copy-pastes

Everyone in this community was a beginner once. Ask the questions you'd be embarrassed to ask publicly. Get real, direct help.

// what you get

Real value.
Zero noise.

Platform Ninjas is built for depth, not scale. Every channel exists because engineers asked for it.

Focused technical channels

Platform engineering, Kubernetes, IaC, observability, cloud, security — deep channels for deep conversations. No algorithm, no engagement bait.

Get unblocked fast

The best help you'll find is from someone who hit the exact same wall last month. Post your problem, get a real answer from engineers who've been there.

Honest trade-off discussions

No sponsored posts. No vendor cheerleading. Just engineers comparing tools and approaches based on what actually happened in production.

Show and tell your work

Built something worth sharing? Ship a blog post, demo, or open source project to people who will genuinely appreciate the craft behind it.

Career & hiring, no gatekeeping

CV reviews, salary transparency, job postings from engineers (not recruiters), and the kind of career advice you'd only get from a trusted mentor.

Weekly async standups

What are you working on this week? A low-pressure ritual that builds familiarity and keeps the community from feeling like a ghost town.

// inside the server

This is what
it looks like

# help-and-questions

mkaur SRE today at 9:14 AM

anyone dealt with OOMKilled pods that only happen under specific traffic spikes? our HPA is scaling correctly but we're still getting killed before new pods are warm

tsaunders Platform Eng today at 9:17 AM

hit this exact issue last month — check your readiness probe timing vs your startup probe. if your app is reporting ready before it's actually warm, HPA counts the pod before it can handle load

startupProbe: failureThreshold: 30 periodSeconds: 10

areed Cloud Eng today at 9:21 AM

also worth checking if your memory limits are too tight. sometimes it's not a leak — it's just the JVM / Go runtime asking for headroom during a GC cycle under pressure

// from the community

What engineers say

Finally a community where people actually want to discuss the trade-offs, not just tell you to use their favourite tool. The K8s channel alone has saved me hours of debugging.

Jamie W.

Senior DevOps Engineer

I asked a question about Backstage plugin architecture at 11pm on a Tuesday and had three detailed answers by morning. This is what a technical community should feel like.

Priya O.

Platform Engineer

The show-and-tell channel is exactly what I needed — real engineers sharing real work, not polished marketing content. Already found three tools I didn't know existed.

Dan L.

SRE at a scale-up

// community impact

The numbers
behind the ninjas

400+ active members across 30+ countries

1.2K+ questions answered avg. response in <2 hrs

85+ mentorship sessions 1:1 & group formats

40+ open source contributions tools, runbooks & templates shared

// what we give back

We don't just talk.
We contribute.

Platform Ninjas is more than a place to get help — it's a community that actively makes the tech ecosystem better. Members share runbooks, open-source tooling, write-ups from production incidents, and architecture decision records that others can learn from and build on. Knowledge hoarding has no place here.

From internal docs turned into public templates, to blog posts triggered by community discussions, to open source projects born in our #show-and-tell channel — the work created inside Platform Ninjas ships into the wild.

open source runbook library architecture templates blog posts conference talks public postmortems tooling interview prep

Runbook & template library

Members contribute real runbooks — incident response, DR procedures, K8s troubleshooting playbooks — that anyone in the community can adapt and use in production.

Open source first

Tools and scripts built by members get shared in #show-and-tell and encouraged to go public. Several have grown into maintained repos with contributors from across the community.

Honest postmortems

Anonymised write-ups from real incidents — what broke, why, and what changed. The kind of content that can't be found on vendor blogs because it's too honest.

Speaker & writing pipeline

Community members go on to speak at KubeCon, PlatformCon, and SREcon. We help engineers turn their technical depth into a public voice — through feedback, coaching, and encouragement.

// mentorship programme

Level up with
someone who's
been where you are.

Most mentorship programmes are awkward one-off calls. Ours is embedded in the community itself.

Platform Ninjas mentors are active members — engineers who answer questions in the channels, show up to AMAs, and are genuinely invested in helping others grow. The mentorship relationship starts naturally, not from a form submission.

Whether you're transitioning into platform engineering, preparing for a senior role, or navigating your first production incident as a lead — there's a mentor here who's done exactly that.

step 01

Join & introduce yourself

Tell the community where you are in your career, what you're working on, and what you're trying to figure out. This is where most mentorship relationships begin — organically.

step 02

Connect with a mentor

Browse the mentor directory in Discord, or ask in #mentorship-matching. Mentors list their specialisms, availability, and preferred format. No cold-form bureaucracy.

step 03

Grow on your terms

1:1 async check-ins, live voice sessions, code & architecture reviews, CV feedback, interview prep — the format is shaped by what you actually need, not a fixed template.

// meet some of our mentors

Aisha K.

Staff Platform Engineer · 9 yrs experience

Platform Engineering Backstage / IDPs Career growth

I spent years figuring out platform engineering with no one to ask. I mentor so others don't have to waste the same time I did.

12mentees

4promotions helped

asyncformat

Marcus O.

Principal SRE · ex-Google · 12 yrs experience

SRE fundamentals Incident management SLOs & error budgets

The gap between knowing about SRE and actually implementing it at scale is enormous. I try to close that gap for people earlier than I did.

18mentees

3FAANG hires

1:1format

Sonia P.

Senior DevOps Lead · Hashicorp ecosystem expert

Terraform / OpenTofu GitOps CI/CD architecture

I got into DevOps by accident — no formal CS background. If I could figure it out, I want to show others there's no single path in.

9mentees

6career pivots

groupformat

Jae N.

Cloud Architect · AWS & GCP certified · 10 yrs

Cloud architecture FinOps Multi-cloud strategy

Cloud decisions made early become very expensive to undo. I help teams make those decisions with eyes open — before the bill arrives.

15mentees

$2M+cloud saved

bothformats

Tolu R.

AI Infrastructure Engineer · MLOps specialist

AI/ML infra GPU scheduling Model serving

AI infra is moving so fast that most teams are building on sand. I mentor engineers who want to build it properly from the start.

7mentees

5teams advised

asyncformat

Clara W.

Security Engineer · DevSecOps & supply chain

DevSecOps Supply chain Zero trust

Security is everyone's job now — it's just that most engineers weren't taught that. I try to change that one engineer at a time.

11mentees

3certs achieved

1:1format

Are you a senior engineer? Become a mentor.

If you have 5+ years of experience in any of our core areas and want to give back to the next generation of infrastructure engineers, we'd love to have you. Mentorship here is on your terms — async, structured, or somewhere in between.

apply to mentor

// faq

Questions?
Answered.

Is Platform Ninjas actually free?

Yes — completely free, forever. No paid tiers, no premium channels, no upsell. The community is funded by the time and goodwill of people who believe in sharing knowledge openly. If we ever introduce optional paid perks, free access to everything that exists today will never go away.

I'm fairly new to DevOps — is this too advanced for me?

Not at all. Every senior engineer here was a junior once. We have a strict no-gatekeeping rule — there are no stupid questions, and any member who makes someone feel unwelcome for asking gets removed. The #help-and-questions channel is specifically for people who are stuck, regardless of experience level.

How is this different from Reddit or the CNCF Slack?

Reddit is great for passive consumption but terrible for real-time help and building relationships. CNCF Slack is enormous and hard to navigate. Platform Ninjas is smaller and more focused — the signal-to-noise ratio is higher because we moderate actively and the community has a clear identity. You'll recognise the same names week after week.

Can I promote my blog, product, or open source project?

Yes — in the right channel. The #show-and-tell channel exists exactly for this. Share something you built, wrote, or open-sourced and you'll get genuine feedback from engineers who care. What's not allowed is unsolicited cold promotion in unrelated channels, or DM-bombing members with pitches. We'll remove you for that.

What kind of moderation does the community have?

We have an active mod team that enforces a clear code of conduct. No harassment, no discrimination, no vendor shilling, no spam. We use Discord's AutoMod for obvious spam bursts and have human mods for everything else. Reports are handled within 24 hours. The goal is a space where people feel comfortable asking questions and sharing honestly.

Do I need to be active to be a member?

No. Lurking is completely valid — many of the most valuable members read everything and post occasionally. The community doesn't pressure anyone to contribute. When you have something useful to share or a question you're stuck on, we'll be here. There's no engagement quota or activity requirement.

Are there events, talks, or AMAs?

Yes, and more are being added as we grow. We run async AMAs where senior engineers answer questions over 48 hours, periodic live voice sessions on specific topics (think "K8s networking deep dive"), and a weekly async standup thread. Subscribe to the newsletter or join the Discord to get notified when new events are announced.

I want to help build the community — how?

We love this question. Join, introduce yourself, answer a few questions in #help-and-questions, and share something in #show-and-tell. Consistent, helpful members get offered moderator and contributor roles over time — we build the community from within. If you have a specific idea (a channel, an event format, a partnership), drop it in #general-chat and we'll discuss it.

Build. Deploy. Level up.

You belong here if...

Real value.Zero noise.

This is whatit looks like

What engineers say

The numbersbehind the ninjas

We don't just talk.We contribute.

Level up withsomeone who'sbeen where you are.