Community

Build alongside the people who ship on NemoRouter every day

A public Slack for NemoRouter developers. Get help with the API, post what you built, learn cost-optimization patterns from other teams. Free, every channel — no gated tiers.

Public channels
6

Support, features, builders, etc.

Median answer time
< 4h

Community + team during business hours

Pinned how-tos
40+

Curated answers carried into /docs

Office hours
Weekly

Live Q&A every Thursday

Channels

Where the conversation happens

Every channel is public. The team is on every channel. The best answers carry forward into the docs.

#support

Questions about the API, SDKs, routing, guardrails, evals. The team and the community both answer; the best replies get pinned and migrated to /docs.

  • Code-first answers — no "have you tried turning it off and on" replies
  • Repro instructions live in the channel topic
  • Pinned answers feed the docs roadmap

#feature-requests

Tell us what is missing. One thread per request, upvote with reactions, the team comments on every one. Shipped requests get tagged with the changelog entry.

  • Zero deletion policy — declined requests stay with the reasoning
  • Roadmap published quarterly from the highest-voted threads
  • Linked to GitHub issues for SDK + plugin work

#builders

Show-and-tell. Customers post what they have shipped on top of NemoRouter — agentic apps, evals frameworks, internal tools, weird side projects.

  • Featured builds get a write-up on /blog
  • Open-source projects get a sponsor invitation
  • Friday demos every two weeks
How to participate

The community works because everyone leans in a little

Ask great questions

Include what you tried, what you expected, what you got, and a minimal repro. The community rewards the question that helps the next person.

Answer when you can

You used NemoRouter for two weeks longer than someone else — your answer counts. The team curates the best ones into /docs with attribution.

Open a PR on the SDK

The Python SDK + 15-language examples are public. Bug fixes, new framework adapters, doc improvements — all welcome. We respond to every PR within a week.

House rules

Community guidelines

A short list. Read once, hold each other to it.

Be kind. Disagreements welcome; personal attacks are not.
Search before asking — answers from prior threads help everyone.
No referral-link spam, no recruiter DMs without consent.
Bug reports → #support with a repro. Security issues → security@nemorouter.ai (not Slack).
Promotion of your own NemoRouter-built project is encouraged in #builders. Once per launch — not weekly.
Paying-customer SLA support runs through support@nemorouter.ai. Slack is community best-effort, never SLA.

Free · public · every channel

Join the Slack now — first ask gets answered

The community is small enough that you will get a thoughtful reply, and large enough that someone has hit the same problem you have.

Slack free tier — message history rolls past 90 days. We pin canonical answers and migrate long threads to /docs.