Can AI replace MagicChat?
A retrieval chatbot over your own docs is one of the most one-shottable products there is: crawl the site, chunk and embed it, answer from the top matches with an LLM, drop in a widget. What you don't get for free is the boring operational layer, scheduled re-crawls, analytics, lead capture and human handoff, multi-source connectors, and a hosted widget that stays up. Buildable in a weekend, real gaps after that.
01What it costs
Checked Aug 12, 2026 · source: magicchat.ai.
| Plan | Monthly | Billed yearly | What you get |
|---|---|---|---|
| Free | Free | Free | 1 chatbot; 100 messages/month; 50 training pages; website embed; community support |
| Lite | $29 | — | 1 chatbot; 7,500 messages/month; 500 pages; 1 team member; manual refresh |
| Starter | $59 | — | 1 chatbot; 15,000 messages/month; 1,000 pages; 1 team member; manual refresh |
| Growth | $129 | — | 2 chatbots; 33,000 messages/month; 10,000 pages; 4 team members; monthly auto-refresh; API access |
| Scale | $429 | — | 10 chatbots; 110,000 messages/month; 50,000 pages; 10 team members; weekly auto-refresh; daily auto-scan |
| Enterprise | — | — | Custom message volume, chatbot count, seats and compliance; HIPAA eligible with DPA/BAA on request |
Hidden costs: Removing MagicChat branding costs $59/month. Each extra 5,000-message block costs $59/month. Prices exclude tax; paid plans have a 7-day trial.
02Could AI build it for you?
The core job: Crawl a site or docs, chunk and embed the pages into a vector store, retrieve the top matches for a visitor question, and answer with an LLM through an embeddable chat widget.
What a working version needs:
- OpenAI/Anthropic API key
- an embeddings model
- a vector store (pgvector or sqlite-vec)
- a public HTTPS deployment for the widget
AI 'chat with your docs' support bot; the RAG core is a weekend build, the refresh/analytics/hosting layer is the moat.
03What you'd give up
- scheduled auto re-crawl and content refresh
- analytics and conversation-history dashboards
- lead capture and human handoff
- multi-source connectors and integrations
- hosted uptime for the widget
- team seats and enterprise compliance (HIPAA/DPA/BAA)
People pay so they never touch the plumbing: the crawler that re-indexes when docs change, the dashboard that shows what customers asked, the connectors to their help desk, and a widget that stays up without them running a server. The RAG is easy; keeping it fresh, measured and online is the recurring work.
04Free and cheaper alternatives
Self-hosted chat over your own docs with connectors and permissions; heavier to run than a widget, but the whole RAG loop is yours.
onyx.app →05The build prompt
Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.
Build me an AI support chatbot that trains on my own website and docs, to replace MagicChat, in an empty repo. Stack (no alternatives): Next.js 15 (App Router) + TypeScript, Postgres with the pgvector extension via Drizzle ORM, and Docker Compose so `docker compose up` runs Postgres and the app together. Use the OpenAI or Anthropic API for both embeddings and answers (keys in .env). Core loop: - `npm run ingest -- <sitemap-or-url>`: crawl the pages, strip to clean text, chunk (~800 tokens with overlap), embed each chunk, and store text + vector + source URL in Postgres. - A /api/chat route: embed the incoming question, pull the top-k chunks by cosine similarity, and ask the LLM to answer ONLY from that context, returning the source URLs it used. Stream the answer. - A single embeddable widget: one <script> tag mounts a floating chat bubble on any site, talking to /api/chat with CORS locked to configured origins. Details: - One config file: bot name, greeting, allowed origins, model, top-k. - Store everything locally in Postgres; `npm run reindex` re-crawls and replaces. - Secrets in .env, ship .env.example, never commit keys. - Handle empty, loading, and "I don't know from the docs" states honestly; never invent answers outside the retrieved context. - Out of scope: multi-channel (email/WhatsApp/Slack), team seats, an analytics dashboard, human handoff, scheduled auto-refresh (leave a documented cron hook), and any hosted control plane. - README: setup, the ingest command, embedding the widget, and where data lives.
06Open-source starting points
- Onyx (formerly Danswer): Open-source AI assistant that answers questions over your own documents
- Flowise: Open-source builder for RAG chatbots you can embed
App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.