#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 nRouter.
A developer community for nRouter builders. Get help with the API, post what you built, learn cost-optimization patterns from other teams. Free, open, 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 nRouter: 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@nrouter.ai (not Slack).
- Promotion of your own nRouter-built project is encouraged in #builders. Once per launch, not weekly.
Paying-customer SLA support runs through support@nrouter.ai. Slack is community best-effort, never SLA.
Collaboration & Knowledge Sharing
Why developers and AI engineers build with our community.
An engineering-first space for discussing real-world routing architectures, prompt optimization, and agent reliability.
Peer-Reviewed Production Architectures
Exchange battle-tested patterns for high-throughput gateway configurations, multi-agent frameworks, dynamic failovers, and streaming concurrency across real-world workloads.
Zero-Markup Optimization & Token Economics
Collaborate with teams optimizing token consumption through intelligent semantic routing, prompt compression algorithms, and preflight budget controls that cut API expenses by 40-70%.
Direct Access to Infrastructure Engineers
Our core systems and gateway engineers actively engage in public channels, review architectural RFCs, and help debug routing edge cases alongside the community.
Open Source Tooling & Framework Adapters
Build and refine community integrations for LangChain, LlamaIndex, AutoGen, and local inference runtimes with shared reference implementations and code snippets.
Other channels
Find us where you already work.
Community FAQ
Frequently asked questions about the community.
How do I join the nRouter community?
Click the "Join the Slack" button on https://nrouter.ai/community. The link opens our public Slack workspace; every channel (#support, #feature-requests, #builders) is open to everyone.
What channels are in the nRouter Slack?
#support for API, SDK, routing, guardrails, and evals questions; #feature-requests for product input; #builders for show-and-tell of what customers shipped on nRouter; plus general public channels for casual chat. Every one open and free.
Is participation in the developer community open to everyone?
Yes. The nRouter community workspace is open to all AI engineers, developers, and researchers. There are no paywalled discussion channels, invite codes, or subscription requirements to collaborate.
How is formal enterprise support handled compared to community Slack?
Community Slack channels offer peer discussions, architecture exchanges, and best-effort team answers. For production SLAs, priority incident response, and compliance reviews, enterprise customers communicate directly via support@nrouter.ai.
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