r/devops
Platform, SRE and infrastructure engineers
- Size
- Large
- Buying intent
- High
- Promotion
- Conditional
The strongest single community for infrastructure tooling. Members hold real budgets, evaluate continuously, and post detailed write-ups of what they tried and why they abandoned it. Those comparison threads are some of the most commercially useful content on Reddit.
The culture rewards specificity above everything. A reply containing a version number, a failure mode and a trade-off is treated seriously. A reply containing the words scalable and seamless is ignored, and the account that wrote it is remembered.
What we have measured
Lidar reads this community every day. These figures come from the 63 posts we collected here over the last 30 days, read a median of 19 hours after they were posted.
- Posts asking a question
- 44%
- Median replies when we read them
- 8
- Median upvotes when we read them
- 2
The question share is the one to weigh. A community where half the posts ask something is a community that wants answers, and a community where almost none do is one where people are broadcasting rather than asking. The engagement figures are deliberately measured at the moment we collect a post rather than at its final score, because that is the state a thread is in when replying to it is still worth doing.
What people actually post
The incident post-mortem
Something broke and the tooling did not help. Names the gap precisely and usually ends with the author asking what others use.
The build-or-buy debate
Whether to maintain an internal tool or pay for one. The single best thread type to be present in, because the alternative to you is explicit.
The vendor pricing thread
Observability and CI pricing in particular. High engagement and frequently the start of an actual migration.
What people get wrong about it
Vendors assume this community wants less complexity. Many members want more control and read simplification as hidden behaviour.
Can you promote in r/devops?
A disclosed mention answering the exact question asked is accepted. Anything that reads as marketing copy is downvoted immediately, and the community has a long memory for vendors who only appear when their product is named.
What gets you removed
Marketing adjectives. The words seamless, scalable and enterprise-grade are each independently sufficient to have your comment ignored.
A good first contribution
Answer an incident thread with a specific diagnostic path. Naming the exact metric or log line to check earns more credibility than a paragraph of advice.
Products that fit here
- Observability, logging and alerting
- CI/CD and deployment tooling
- Infrastructure as code and secrets
- Cost management for cloud spend
What does not work
Anything closed-source with no documented pricing. Both are treated as red flags, and the second more than the first.
Timing
Steady. Cloud bill reviews in Q4 and after large incidents produce clusters of migration threads.
How it compares to the neighbours
The communities closest to r/devops, and how they differ on the three things that decide whether one is worth your time.
| Community | Size | Intent | Promotion |
|---|---|---|---|
| r/devops | Large | High | Conditional |
| r/sysadmin | Very large | High | Conditional |
| r/kubernetes | Mid-size | High | Conditional |
| r/selfhosted | Large | High | Open |
Where this fits in a wider plan
r/devops appears in our list of the best subreddits for developer tools, which sets it against the other communities worth watching in that market. If you are starting from nothing, the six-week plan in finding your first 100 users covers how to build standing before you mention a product at all.
Watch r/devops without reading it.
Lidar reads it every day, scores each post against what your product does, and sends you the ones worth answering. Along with the rest of engineering and infrastructure.