K8s, SRE, devops, platform-team practitioners · 12 rooms · ranked by yield
Infra and platform-engineering circles. Ranked by deal-flow yield.
K8s Slack, Platform Engineering, r/sre, buyer + builder at the same table.
Platform-engineering and infra-ops rooms. The audience is overwhelmingly buyers, but they are also the early-adopter user base for the infra-grade tools we surface inside the product.
Yield story
Primary surfaces are Kubernetes Slack, Platform Engineering community, r/devops, and r/sre, four rooms whose membership shows the highest crossover with infra-grade GitHub orgs we surface.
Cadence
Weekly read on the four primary surfaces.
Caveat
Platform-eng rooms reward operational precision and punish marketing language. Engagement is technical Q&A only.
Yield breakdown · 12 rooms
5
Primary
Direct deal-flow surface. Multiple repos we surface first showed up here.
4
Secondary
Adjacent. Signals overlap, but rarely the first-mention surface.
3
Ambient
Culture / reading list. Useful for framing, not for sourcing.
Engagement status
0
Engage
7
Watch
0
Hold
5
Read
0
Blocked
The ranked roster
12 rooms, sorted by yield tier, numbered, linked.
Primary first, then secondary, then ambient. Hand-authored order within each tier, top of tier = highest attention density.
- 1.
K8s-project community. Cloud-native infra deal-flow.
- 2.
Platform-team practitioners. Buyer-archetype + builder archetype overlap.
- 3.
Infrastructure-as-code, observability, platform engineering.
- 4.
Reliability-engineering audience. High-overlap with observability orgs.
- 5.
Cloud-native foundation Slack, listed again here for infra-eng angle.
- 6.
K8s practitioner audience.
- 7.
HashiCorp-tooling discussion. Infra-OSS pattern memory.
- 8.
Reliability-eng practitioner Slack. SRE-buyer crossover.
- 9.
Observability-customer community. Adjacent buyer pool.
- 10.
Conference-attached community. Ambient ops-culture signal.
- 11.
AWS-customer audience. Cross-confirms cloud-native bets.
- 12.
Honeycomb-customer observability community. Niche but high-signal.
Frequently asked
Four questions about this list.
- What is the "deal-flow yield" of a community?
- Yield is a three-tier rating, primary, secondary, ambient, describing how often a community has been the first public surface where a repo or founder we now surface inside the product appeared. Primary means multiple deals trace back to the room; ambient means the room is read for framing, not sourcing.
- Why is infra and platform-engineering circles indexed by type instead of by platform?
- The platform map at /voices already covers per-platform rosters (Reddit-100, HN-100, X-100). Indexing by type cuts the same audience differently, a Cursor user in a Cursor Discord is a different deal-flow signal than the same user in a CNCF channel, even though both are on Discord.
- Do we engage in every community on this page?
- No. Each community is tagged with an engagement status (engage / watch / hold / read / blocked). The default for most rooms is "watch" or "read", we listen but do not post. The "engage" tag is reserved for a small number of rooms where comment-only engagement on technical Q&A is allowed by both the room rules and our anonymity rule.
- Are the individuals inside these communities listed anywhere?
- No. The anonymity rule that governs the entire site applies here: we name communities, not individuals. The specific founders, maintainers, and contributors we surface live inside the paid product, that is the buyer's edge.
Where the deal-flow signal actually lives
Rooms tell us where to look. Telemetry tells us what to fund.
Reading infra and platform-engineering circlesdoesn’t produce a deal. It sharpens the question we ask the GitHub-side telemetry. The actual deal-flow signal lives at /predicted, /firstlook, and the rest of the signal stack below.
Infra and platform-engineering circles roster regenerated quarterly. Status flags update weekly. Companion platform map at /voices. Master mixed list at /target-list.