r/devops
Platform engineers, SREs and the people who carry the pager talk shop in r/devops. Threads range from pipeline design and observability to incident stories and on-call fatigue, and a steady share ask what others run for logs, secrets or CI. Guides describe the crowd as skeptical of vendors: a feature announcement without technical depth tends to be removed, while a post that solves a concrete operational problem can stay. No promotion thread is reported. If you sell infrastructure tooling, earn attention with the reasoning behind an answer, such as cost at a given volume, migration effort and failure modes, and say openly when self-hosting an open-source project would serve the poster better than your product.
Community rules change. Read the sidebar and the pinned rules in r/devops before you post. r/devops on Reddit
Last reviewed by Agent Agency Editorial (AI-drafted from third-party sources, checked 2026-10-22)
About r/devops
Practitioners discuss DevOps work: cloud infrastructure, tooling, incidents, architecture, observability and security, plus fatigue and on-call life.
Common threads:
- Tool comparisons and 'what do you use for X' threads
- Incident and on-call war stories
- Architecture and pipeline design questions
- Troubleshooting posts
- Vendor and market research questions (a flair GummySearch lists)
What people ask in r/devops
- What are teams using for log aggregation that doesn't cost a fortune at our volume?
- Is there a lighter alternative to a full observability suite for a small platform team?
- How are people managing secrets across several clouds without building it themselves?
- Which CI system copes well with a monorepo and long test suites?
- Has anyone moved off their incident management tool, and what did you pick?
How to answer well
- Lead with how you'd solve it (config, architecture, cost reasoning) and only then mention tools.
- Give honest pricing and scaling caveats, including when self-hosting an open-source option is the better call.
- Disclose the affiliation up front and compare against at least one competitor fairly.
- Share concrete operational experience (failure modes, migration effort) rather than feature lists.
When not to post
- Live-incident or burnout threads where the poster needs support, not a vendor.
- When the customer's product does not integrate with the poster's stated stack.
- Threads explicitly asking for open-source-only or self-hosted answers when the product is closed SaaS.
Reported self-promotion norms
Several third-party sources report on this. Guides describe a vendor-skeptical sub. One says vendor content survives only with real technical depth and that surface-level feature announcements are removed. Another says promotion is fine when it solves a real DevOps problem with technical detail. A third calls the sub strict on promotion. A fourth rates its self-promo tolerance as moderate. No promo thread or karma threshold is named.
Similar communities
Questions
Can a brand promote its product in r/devops?
Several third-party sources report on this. Guides describe a vendor-skeptical sub. One says vendor content survives only with real technical depth and that surface-level feature announcements are removed. Another says promotion is fine when it solves a real DevOps problem with technical detail. A third calls the sub strict on promotion. A fourth rates its self-promo tolerance as moderate. No promo thread or karma threshold is named. Read the sidebar and the pinned rules in r/devops before you post.
How should a brand answer questions in r/devops?
Lead with how you'd solve it (config, architecture, cost reasoning) and only then mention tools. Give honest pricing and scaling caveats, including when self-hosting an open-source option is the better call.
When should a brand not post in r/devops?
Live-incident or burnout threads where the poster needs support, not a vendor. When the customer's product does not integrate with the poster's stated stack.