Loading...
Indexed by community type · Ranked by deal-flow yield · 120 rooms
/voices indexes rooms by platform — 100 subreddits, 100 X accounts, 100 HN attention slots. Community Signal indexes the same audience by community type instead — the indie-founder forum, the AI-builder Discord, the OSS-maintainer Slack, the platform-eng circle. Same map, different cross-section.
Each entry is a public surface — a subreddit, a Discord invite, a Slack landing page, a Discourse forum, a newsletter homepage. Each community is ranked by its deal-flow yield tier (primary / secondary / ambient) and tagged with our engagement status (engage / watch / hold / read / blocked).
Anonymity rule, restated: we name communities, not individuals. Listing a Discord ≠ listing its members. The individual founders and contributors we surface live inside the paid product — that’s the buyer’s edge.
How the yield tiers read
Primary
Direct deal-flow surface. Multiple repos we surface first showed up here.
Secondary
Adjacent. Signals overlap, but rarely the first-mention surface.
Ambient
Culture / reading list. Useful for framing, not for sourcing.
/community-signal/indie-founder-forums
12 roomsBootstrapped, indie, build-in-public — the rooms where a repo first leaks a commercial plan.
Bootstrappers, build-in-public crowd, micro-SaaS operators
Open the roster →
/community-signal/ai-builder-rooms
12 roomsLangChain, HF, Latent Space, MLOps — where the next AI-infra repo gets its first 100 users.
Agent, model, and inference-infra builders
Open the roster →
/community-signal/devtools-maker-rooms
12 roomsVercel, Cursor, Bun, Supabase, Astro — the rooms where infra-on-infra repos surface.
Framework, runtime, and IDE customers / contributors
Open the roster →
/community-signal/vc-and-angel-forums
12 roomsWhere the buy-side discusses what it just saw. Inverse signal of /devtools-maker-rooms.
Capital-side rooms — VCs, angels, scout networks
Open the roster →
/community-signal/b2b-saas-operator-groups
12 roomsr/SaaS, RevOps Co-op, ProductLed — where SaaS GTM patterns leak first.
GTM, RevOps, PLG, sales — the operator-side rooms
Open the roster →
/community-signal/open-source-maintainer-spaces
12 roomsGitHub Discussions, CNCF Slack, Sustain OSS — where 'we're going commercial' leaks earliest.
Maintainers, foundation-grade infra contributors
Open the roster →
/community-signal/infra-and-platform-eng-circles
12 roomsK8s Slack, Platform Engineering, r/sre — buyer + builder at the same table.
K8s, SRE, devops, platform-team practitioners
Open the roster →
/community-signal/frontend-and-product-builder-rooms
12 roomsNext.js Discord, Reactiflux, Tailwind, shadcn/ui — the surface where frontend-org repos surface first.
UI, design system, web framework practitioners
Open the roster →
/community-signal/data-and-ml-eng-collectives
12 roomsdbt, MLOps, r/dataengineering, Modern Data Stack — where production-data orgs first leak hiring + roadmap.
Pipeline, warehouse, modern-data-stack, ML-engineering practitioners
Open the roster →
/community-signal/founder-newsletter-comment-sections
12 roomsLenny's, Latent Space, Pragmatic Engineer, Trends.vc — where thesis-shaping happens in public.
Analyst-led reading rooms with attached comment threads
Open the roster →
Why a type-cross-section, not just a platform one
The platform map at /voices answers where the developer-investor reads. The type map here answers which room are they reading inside that platform. The same Discord user is one of half a dozen archetypes depending on which server they’re in — a Cursor user with a maintained repo is a different signal than the same user in a CNCF channel.
The two maps don’t replace each other. They overlay. The company-side weekly working board uses both: platform map for cadence, type map for sectoring.
How to use this list
We don’t source deals out of any of these rooms — the rooms tell us where to look, not what to fund. The actual deal-flow signal comes from the GitHub-side telemetry that powers /predicted and /firstlook. The rooms above are the second derivative — they reveal which sectors the dev-side audience is bending toward, weeks before the telemetry confirms it.
Refreshed 2026-05-22. Each type roster is regenerated quarterly. Status flags update weekly when engagement state changes. Companion platform map at /voices.