langchain-nextjs-template vs chatbot
Two of the top chat apps, side by side: score, setup, license, activity and what each review found.
langchain-nextjs-template
Next.js routes for LangChain.js chat, agents, structured output and RAG
chatbot
Next.js chat template with Auth.js, Postgres history and AI Gateway models
| What we compare | langchain-nextjs-template | chatbot |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 64, popular | 80, popular |
| Freshness | 100, active | 98, active |
| Maintenance | 33, patchy | 15, weak |
| Easy to run | 67, easy | 33, some setup |
| Agent-ready | 0, none | 0, none |
| Facts from GitHub and the README | ||
| Stars | 2.5k | 21k |
| License | MIT (permissive) | Apache-2.0 (permissive) |
| Last commit | Oct 2026 | Jul 2026 |
| Last release | None published | None published |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
langchain-nextjs-template
Five Next.js API routes that each show one LangChain.js pattern: plain chat, Zod structured output, a prebuilt LangGraph.js agent with Tavily search, and RAG as a chain and as an agent over a Supabase pgvector table. Tokens stream to the client through the AI SDK, routes run on Edge functions, and there is no auth or persistence beyond the vector table. For developers learning LangChain.js who want runnable routes to copy.
Who it is for: Developers learning LangChain.js on Next.js
Strengths
- Each pattern is one route file you can lift into your own app
- Hosted demo on Vercel
- Mock-backed integration tests run without API keys or a live database
- Supabase adapter reuses the documents table and match_documents function; no migration
Weaknesses
- No auth and no chat history persistence
- OpenAI only out of the box; other providers need code changes
- Re-ingesting the same text duplicates vectors; no dedupe
- Agent and search examples need a Tavily key
- TypeScript, openai, langchain, langgraph, ai-sdk
- Needs openai-api-key, supabase, tavily-api-key
- GitHub template
- env example file
chatbot
Clone it and you get a Next.js App Router chat app on the AI SDK with Auth.js login, chat history in Neon Postgres through Drizzle migrations, file uploads to Vercel Blob and a streaming UI on shadcn/ui. Models route through Vercel AI Gateway; Mistral, Moonshot, DeepSeek, OpenAI and xAI are preconfigured in lib/ai/models.ts. For teams starting a chat product on Vercel who want auth and persistence wired on day one.
Who it is for: Teams starting a chat product on Next.js and Vercel
Strengths
- Auth.js, Postgres chat history and Drizzle migrations wired out of the box
- Live demo plus a separate docs site
- Per-model provider routing in lib/ai/models.ts; swapping vendors is a small edit
- Tests included
Weaknesses
- Defaults to Vercel services: AI Gateway, Neon Postgres, Vercel Blob
- Off Vercel you must set AI_GATEWAY_API_KEY and replace Blob storage
- No Docker or compose files
- TypeScript, ai-gateway, ai-sdk, openai, mistral
- Needs postgres, vercel-blob, ai-gateway-api-key
- GitHub template
- env example file
- sign-in: Auth.js