# The developer community stack (https://devrel.directory/stacks/developer-community)

**Where should a developer community live, and what keeps it alive?**

Choosing a chat platform is the smallest of these decisions and the only one most teams make deliberately. Six more: where answers go to be found again, how you hear the conversations happening off your turf, and how you tell whether anyone is actually showing up.

Curated shortlist of 16 tools across 7 decisions, last read against the live products on 2026-07-27. Live from devrel.directory as of 2026-07-27.

## 1. Pick the room

Real-time chat is where a community feels alive and where knowledge goes to die - messages scroll away and search is an afterthought. Pick on where your developers already are rather than on features: Discord if they came from open source or gaming-adjacent tooling, Slack if they are at work and their employer already pays for it, Zulip if threading matters more than vibe and you want to host it yourself.

- [Discord](https://devrel.directory/directory/discord.md): Real-time chat platform used by developer communities for group communication and community building.
- [Slack](https://devrel.directory/directory/slack.md): Team chat platform where developer and customer communities collaborate and automate workflows.
- [Zulip](https://devrel.directory/directory/zulip.md): Open-source threaded team chat; the community home of Rust and other projects that outgrew unthreaded chat.

## 2. Give answers a permanent home

The step teams skip, then spend two years regretting. A forum is where a good answer stays findable a year later, by someone who never joins your chat. If your project already lives on GitHub, Discussions is the version of this decision with no new account and no new moderation surface - which is often the version that actually survives.

- [GitHub Discussions](https://devrel.directory/directory/github-discussions.md): Threaded forums attached to your repos; the lowest-friction community home for open-source projects.
- [Discourse](https://devrel.directory/directory/discourse.md): The standard open-source forum software for long-form developer community discussion.
- [Apache Answer](https://devrel.directory/directory/apache-answer.md): Open-source Q&A platform for running a self-hosted developer support forum with reputation and moderation.

## 3. Make what you already answered findable

If the room is Discord and the answers are staying there, this indexes support threads so they show up in search results instead of being re-answered every week. It is a direct patch for the failure mode in step one, and it is worth installing before the archive gets big rather than after.

- [Answer Overflow](https://devrel.directory/directory/answer-overflow.md): Indexes Discord help channels into Google so community answers become searchable content.

## 4. Hear the conversations you were not invited to

Most of what gets said about a developer tool is said somewhere you do not control: a Reddit thread, a Hacker News comment, someone's issue tracker. Alerting on your own name is the cheapest signal in this entire list, and the one that most often surfaces a problem while it is still small.

- [F5Bot](https://devrel.directory/directory/f5bot.md): Free email alerts when your product is mentioned on Reddit, Hacker News, or Lobsters; the zero-budget listening option.
- [Octolens](https://devrel.directory/directory/octolens.md): Social listening tool tracking mentions across Reddit, X, LinkedIn, and other platforms; evolving to serve the agent era with API and MCP integrations.

## 5. Know who is actually showing up

Member counts measure signups, not community. These stitch together the same person across chat, GitHub, and events so you can see who keeps returning and who answered someone else's question. Worth it once you have more activity than one person can hold in their head, and overhead before that.

- [Common Room](https://devrel.directory/directory/common-room.md): Platform that aggregates member activity across Discord, Slack, GitHub, and social to provide buyer intelligence and community insights through AI agents.
- [Advocu](https://devrel.directory/directory/advocu.md): Runs developer ambassador and experts programs: applications, activity tracking, and program reporting in one place.

## 6. Run the recurring moment

A community with nothing on the calendar is a support channel. Something regular and small - office hours, a monthly call - does more than an annual conference, and the tooling only needs to handle a page, a date, and a reminder.

- [Luma](https://devrel.directory/directory/luma.md): Event pages, registration, and calendars used heavily for developer meetups.
- [Bevy](https://devrel.directory/directory/bevy.md): Platform for distributed chapter and meetup programs; powers Google Developer Groups and CNCF community groups.

## 7. Borrow from people doing this full time

Community work is unusually lonely inside a company, because nobody else in the building does your job. These are where the practitioners compare notes on the parts nobody writes down: moderation calls, burnout, what to do when the room goes quiet.

- [DevRel Collective](https://devrel.directory/directory/devrel-collective.md): Slack community of DevRel practitioners; the de-facto watercooler of the profession.
- [CMX](https://devrel.directory/directory/cmx.md): Community for community professionals with events and research, much of it DevRel-adjacent.
- [Community Pulse](https://devrel.directory/directory/community-pulse.md): Podcast on community and DevRel topics, hosted by long-time practitioners.

## Method

These are shortlists, not rankings. Every tool named here has its own directory entry with the facts it publishes and the date they were checked, and the order within a step is the order it was written in, not a verdict about which is better. We do not run these tools in production and we take no money for inclusion. Where a step has two options that genuinely suit different situations, it says which is which instead of picking one.

Background reading: https://devrel.directory/docs/practices/community-building.md

## Open roles doing this work

11 currently listed under community roles:

- Startup Community Manager at Nebius (Paris, France): https://devrel.directory/jobs/nebius-startup-community-manager-2026-07
- Staff Developer Advocate, Community & Events at LiveKit (Hybrid (San Francisco, CA)): https://devrel.directory/jobs/livekit-staff-developer-advocate-2026-07
- Developer Community Manager at Nebius (Remote (US)): https://devrel.directory/jobs/nebius-developer-community-manager-2026-07
- Technical Community Lead, Campus Leaders at OpenAI (San Francisco, CA): https://devrel.directory/jobs/openai-technical-community-lead-2026-07
- Technical Community Manager at PostHog (Remote): https://devrel.directory/jobs/posthog-technical-community-manager-2026-07
- Event Programs Manager, Developer Community & Ecosystem at Supabase (Remote): https://devrel.directory/jobs/supabase-event-programs-manager-2026-07
- Enterprise Community Lead at Anthropic (San Francisco, CA): https://devrel.directory/jobs/anthropic-enterprise-community-lead-2026-07
- Community Manager at Modal (San Francisco, CA): https://devrel.directory/jobs/modal-community-manager-2026-07
- Technical Community Manager at Postman (San Francisco, CA): https://devrel.directory/jobs/postman-technical-community-manager-2026-07
- Developer Relations Engineer at Supabase (San Francisco, CA): https://devrel.directory/jobs/supabase-devrel-engineer-2026-07
- Head of Developer Community at Vercel (Hybrid (SF, NYC, Austin)): https://devrel.directory/jobs/vercel-head-developer-community-2026-07

## Upcoming events on these topics

- Write the Docs Berlin (Berlin, Germany), 2026-09-06: https://devrel.directory/events/write-the-docs-berlin-2026
- Kubernetes Community Days Argentina (Buenos Aires, Argentina), 2026-10-02: https://devrel.directory/events/kubernetes-community-day-s-argentina-2026
- Open Source Summit Europe (Prague, Czechia), 2026-10-07: https://devrel.directory/events/open-source-summit-europe-2026
- All Things Open (Raleigh, NC), 2026-10-19: https://devrel.directory/events/all-things-open-2026
- Bergen Open Source (Bergen, Norway), 2026-10-23: https://devrel.directory/events/bergen-open-source-2026
- Community Day for Java (Ahmedabad, India), 2026-10-23: https://devrel.directory/events/community-day-for-java-2026

