chatbot vs claude-quickstarts
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
claude-quickstarts
Independent Claude API starter projects, one folder per pattern
| What we compare | chatbot | claude-quickstarts |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 80, popular | 75, popular |
| Freshness | 98, active | 100, active |
| Maintenance | 15, weak | 33, patchy |
| Easy to run | 33, some setup | 0, hard |
| Agent-ready | 0, none | 40, minimal |
| Facts from GitHub and the README | ||
| Stars | 21k | 17.9k |
| License | Apache-2.0 (permissive) | MIT (permissive) |
| Last commit | Jul 2026 | Oct 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 |
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
claude-quickstarts
Independent Claude API starter projects in one repo, not one app: a customer support agent with a knowledge base, a financial data analyst with charts, computer-use and Playwright browser-use demos, a two-agent coding loop on the Agent SDK, and Managed Agents examples for Slack, Linear, Sentry, MCP and CopilotKit AG-UI. Mixed Next.js and Python, each folder with its own setup. For developers copying out one pattern.
Who it is for: Developers copying one Claude pattern into their own app
Strengths
- Covers computer use, browser use, Agent SDK and Managed Agents in one checkout
- Each quickstart is self-contained with its own README and setup
- Tracks current toolset shapes (computer_toolset_20260801, browser_toolset_20260801)
- Ships a CLAUDE.md for agent-driven edits
Weaknesses
- Not a single forkable app; you extract one subfolder
- No auth, billing or database at the root; only what each sample needs
- Anthropic-only; no provider abstraction
- No root .env.example or Docker files
- TypeScript, anthropic
- Needs anthropic-api-key
More in Chat apps
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.