chatbot vs chat
Two of the top chat apps, side by side: score, setup, license, activity and what each review found.
chatbot
Next.js chat template with Auth.js, Postgres history and AI Gateway models
chat
Nuxt UI chat template with GitHub login, SQLite history and AI Gateway
| What we compare | chatbot | chat |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 80, popular | 14, niche |
| Freshness | 98, active | 100, active |
| Maintenance | 15, weak | 33, patchy |
| Easy to run | 33, some setup | 67, easy |
| Agent-ready | 0, none | 0, none |
| Facts from GitHub and the README | ||
| Stars | 21k | 376 |
| License | Apache-2.0 (permissive) | MIT (permissive) |
| Last commit | Jul 2026 | Oct 2026 |
| Last release | None published | None published |
| Language | TypeScript | Vue |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
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
chat
A Nuxt app on Nuxt UI and the AI SDK: streaming replies with reasoning, three models through Vercel AI Gateway (Claude Haiku 4.5, Gemini 3 Flash, GPT-5 Nano), provider web search, dictation over WebSocket, and chart and weather tool calls. GitHub OAuth, chat history in SQLite or Turso through Drizzle, and NuxtHub Blob uploads are included. For Vue and Nuxt teams who want a complete chat UI with persistence.
Who it is for: Vue and Nuxt teams who want a complete chat UI
Strengths
- Auth, Drizzle migrations and uploads wired; local dev needs no external database
- Blob storage swaps between local disk, Vercel Blob, Cloudflare R2 and S3
- Live demo and a one-command scaffold (npm create nuxt -t ui/chat)
- Committed within the last day
Weaknesses
- Models and dictation go through Vercel AI Gateway; direct keys need code changes
- Auth is GitHub OAuth only
- No tests listed
- Production database path assumes Turso
- Vue, ai-gateway, ai-sdk, anthropic, google
- Needs ai-gateway-api-key, github-oauth-app, sqlite-or-turso
- GitHub template
- env example file