Conversational AI
Chat assistants, support bots, internal-tool copilots — anything where the LLM is the primary surface a user talks to. Featured builds ship persona + retrieval architecture notes and cost/quality routing strategies.
Apps
What teams ship on Nemo Router, curated when we have builds to feature
The build directory opens once real customer apps are running through the network. No placeholder logos, no fake testimonials. Submissions are rolling — featured entries get published with model mix, routing strategy, and what they would do differently.
apps · directory preview
Sample preview
Featured this quarter~12
Categories at launch6
Submission cadenceRolling
Editorial reviewWeekly
Live nowComing soon
CuratedNot pay-to-listArchitecture notes
- Categories
- 6
- Featured slots
- ~12 / quarter
- Submission cadence
- Rolling
- Status
- Coming soon
Conversational, devtools, docs, localization, content, analytics
Curated; not pay-to-list
Reviewed weekly during launch ramp
Opens once we have real builds to feature
Coming soon. The directory opens once we have builds to feature with real production traffic on the network — currently 97+ models on Anthropic, Google & OpenAI, with Anthropic (Claude), Google (Gemini), and OpenAI (GPT, o-series) live today — AWS Bedrock shipping next.
Planned categories
Six categories we plan to feature first
The directory is editorial, not a marketplace. These six cover the dominant workloads we see teams routing through Nemo Router.
Developer tools
Code completion, refactor assistants, CLI helpers, IDE extensions, and CI agents — the category where TTFT-optimized routing and tool-use correctness are the differentiator.
Document processing
PDF extraction, contract analysis, knowledge-base ingestion, OCR-plus-LLM pipelines. Long-context, batch-friendly, and a strong fit for the cost-tier rankings.
Localization
Translation services, glossary-aware adapters, and locale-specific evaluation — the highest-throughput category we expect, and where one-key multi-provider really earns its keep.
Content
Marketing copy, blog generation, social, product descriptions, and editorial workflows. Brand-voice prompt templates and A/B tests are typically what teams ship next.
Analytics & data extraction
Turning unstructured text into structured JSON — entity extraction, relationship graphs, schema-validated outputs. Latency-tolerant, accuracy-critical, observability-heavy.
How we choose
What gets featured — and what gets a polite no
The directory only matters if every entry is worth reading. Here is the rubric editorial uses for every submission.
Real production traffic
We feature builds that customers actually use, not landing pages. The simplest signal is consistent token volume on Nemo Router — pinned to the org for at least 30 days.
Public problem statement
A one-paragraph description of what your build does and who it serves. Editorial-quality, not a sales pitch. We will ghost-write polish, not the substance.
Architecture transparency
Model mix, routing strategy, guardrails, and retrieval pattern. The directory exists to help other teams learn — vague entries get returned for revision.
Submit
How to get featured at launch
Email us with three things — what you built, why it matters, and a contact for editorial follow-up. Decisions land within two weeks during the launch ramp.
- 01
Send the email
Email support@nemorouter.ai with subject line Submit a build.
- 02
Share the build
A link to the live product, your category, and a one-paragraph description of who uses it and why. Architecture notes optional but appreciated.
- 03
Editorial follow-up
We reply within two weeks during the launch ramp. Featured builds get a draft to review before publication; declined submissions get a one-paragraph reason.
Launch list · ~weekly drops
Get the email when the directory opens
One email when the first batch publishes. Then nothing until something interesting happens.
Already shipping on Nemo Router? Tell us at support@nemorouter.ai.