Framework, runtime, and IDE customers / contributors · 12 rooms · ranked by yield
Devtools maker rooms. Ranked by deal-flow yield.
Vercel, Cursor, Bun, Supabase, Astro, the rooms where infra-on-infra repos surface.
Framework-, runtime-, and IDE-attached communities. The audience is half-builders, half-customers, same people, different hat. Repos that build on top of these stacks usually leak a launch plan inside the host community first.
Yield story
Primary surfaces are Vercel Community, Cursor forum, Bun Discord, Supabase Discord, Zed Discord, and Lovable Discord, six rooms where vibe-coding-era startups currently break first.
Cadence
Weekly read on the primary five. Watch-only on the rest.
Caveat
These rooms are heavily moderated against self-promotion. Engagement is reactive only, we never post a hero thread.
Yield breakdown · 12 rooms
6
Primary
Direct deal-flow surface. Multiple repos we surface first showed up here.
6
Secondary
Adjacent. Signals overlap, but rarely the first-mention surface.
0
Ambient
Culture / reading list. Useful for framing, not for sourcing.
Engagement status
0
Engage
12
Watch
0
Hold
0
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.
Next.js orbit + adjacent infra-on-Vercel orgs. Top deal-flow surface.
- 2.
AI-IDE user community. Vibe-coders building inside.
- 3.
JS-runtime community. Tooling-on-Bun startups surface here first.
- 4.
Backend-as-a-service customers. High overlap with seed-stage SaaS.
- 5.
Modern-editor users. Adjacent to AI-IDE attention map.
- 6.
Vibe-coding startup community. Generated-product crowd.
- 7.
Content-site framework. Adjacent media-and-publishing infra.
- 8.
Edge / Workers / R2 / D1 builders. Infra-on-edge orgs.
- 9.
Transactional-email customers. SaaS go-to-market overlap.
- 10.
Alt-JS runtime + Deploy customers. Niche but high-signal.
- 11.
Rust-desktop-app community. Single-binary-SaaS pattern.
- 12.
Build-tool community. Frontend-tooling org 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 devtools maker rooms 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 devtools maker roomsdoesn’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.
Devtools maker rooms roster regenerated quarterly. Status flags update weekly. Companion platform map at /voices. Master mixed list at /target-list.