# Build brief — a focused alternative to Animam.ai

> **Verdict:** Partly, if you narrow it · **Buildability:** 58/100 · **Category:** No Code Apps
> **Source:** https://www.canitbevibecoded.com/animam-ai
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Animam.ai. Verify current pricing and capabilities before acting.

## Context

**Animam.ai** — An agent that answers from your site's content, captures leads, quotes and books · server-side. It currently costs $32/mo.

The chat is the easy part. Everything that makes it safe to point at customers is not. Ingest a site, search it, stream an answer · that part is commoditised and the prompt below really does it. What resists is the boring half: an amount computed by the server and never by the model, a visitor email verified before it triggers anything, signed webhooks with retries, and a sending domain whose reputation you did not build.

This brief describes a focused, single-operator replacement for the part of Animam.ai that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Crawl the sitemap, strip the chrome, store the text, retrieve the 5 best passages by keyword, stream a grounded answer, and refuse to answer outside the context.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- A place to run a small Node server (a 5 EUR VPS is enough).
- SQLite, or any database you already run.
- A domain you can serve the widget from.

### Data and integrations

- An LLM API key (Anthropic, OpenAI, or a local model).

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build a website chat widget that answers strictly from a site's own content. Node 20 + TypeScript, no framework.

1. Install hono, @anthropic-ai/sdk, cheerio, turndown, better-sqlite3.
2. scripts/ingest.ts takes a sitemap.xml URL as argv and fetches every page, concurrency 4, skipping non-HTML.
3. Strip nav, header, footer and script tags with cheerio, then convert what is left to markdown with turndown.
4. Upsert into SQLite pages(url PRIMARY KEY, title, body, fetched_at) so re-running updates rows instead of duplicating them.
5. src/search.ts takes the 3 to 6 most distinctive words of the question and runs SELECT url, title, substr(body,1,1200) FROM pages WHERE body LIKE ? for each.
6. Rank by number of hits and return the top 5. No embeddings: under ~500 pages LIKE is cheaper, instant, and you can read why a passage was picked.
7. src/server.ts is a Hono app with POST /chat {message, sessionId}.
8. Put the 5 passages and their URLs in the system prompt, call claude-haiku with stream:true, and pipe SSE to the client.
9. System prompt: "Answer only from the CONTEXT below, and cite the page you used."
10. Continue it: "If the answer is not in the context, say you do not know and offer to take a message."
11. And the line that matters: "Never state a price, a date or an availability that is not written in the context."
12. public/widget.js is an IIFE that injects a bubble into a shadow DOM and keeps sessionId in localStorage.
13. It consumes the SSE and writes every message with textContent, never innerHTML · the text comes from a model that read the internet.
14. Store sessions and messages in the same SQLite file, so you can read back what people actually asked.
15. ANTHROPIC_API_KEY lives in .env, server-side only, and never reaches the bundle.
16. No telemetry, no third-party script in the widget.
17. Serve /widget.js with CORS * and a 5 minute cache so a single <script> tag installs it on any page.

Out of scope on purpose, and each of these is a week rather than a line: booking on a real calendar, payments,
quotes with amounts computed server-side, human handover, transactional email that reaches the inbox,
multi-tenancy, GDPR consent, rate limiting and abuse protection.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Amounts computed server-side from a price grid · the model picks the SKU, it never produces the number.
- Visitor identity verified by one-time code before any server-to-server action runs.
- Signed outgoing webhooks with exponential backoff, delivery log and manual redelivery.
- SSRF guard with DNS resolution on every URL the agent is allowed to call.
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Chatwoot](https://github.com/chatwoot/chatwoot) — Self-hosted support inbox with a website widget
- [Typebot](https://github.com/baptisteArno/typebot.io) — Open-source conversational forms and chat flows
- [Onyx (ex-Danswer)](https://github.com/onyx-dot-app/onyx) — Open-source RAG chat over your own documents

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/animam-ai