#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.
Community
Build alongside the people
who ship on Nemo Router.
A public Slack for Nemo Router developers. Get help with the API, post what you built, learn cost-optimization patterns from other teams. Free, every channel — no gated tiers.
Free · public · the team is on every channel
Channels
Where the conversation happens.
Every channel is public. The best answers carry forward into the docs.
#feature-requests
Tell us what is missing. One thread per request, upvote with reactions, the team comments on every one. Declined requests stay up with the reasoning — zero deletion.
#builders
Show-and-tell. Post what you shipped on top of Nemo Router — agentic apps, evals frameworks, internal tools, weird side projects. Featured builds get a /blog write-up.
House rules — community guidelines
- 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 Nemo Router-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.
Other channels
Find us where you already work.
Free · public · every channel
Join the Slack — your first ask gets answered.
Small enough that you will get a thoughtful reply, large enough that someone has hit the same problem you have. Slack's free tier rolls history past 90 days; canonical answers get pinned and migrated to /docs.
Long threads live on in /docs