AI assistants and search decision
AvaChats LLC
A small, single-user chat assistant is realistic for one capable engineer to build and maintain in ~24 hours plus modest monthly upkeep; no durable moats were evident on the supplied product page.
Visit website↗Built by Rohan Gilkes, CFA, who ships 4 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off24 h to build
$50/mo4 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All AvaChats LLC alternatives, with the arithmetic →
What a replacement has to do
- Single-user chat assistant: send message → call LLM API → persist and render reply.
What it still won’t have
- Hosted product with vendor support and SLA
- Any proprietary models, data, or integrations Ava Chats may provide
- Brand, marketing, and built-in user onboarding
- Potential cross-account features (multi-seat billing, analytics, plugins) if present
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
AvaChats LLC does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal, self-hosted chat assistant: use React for the frontend and Node.js + Express for the backend, PostgreSQL for message storage, and host on Vercel (frontend) + Heroku or Render (backend). Core features in scope: user sign-up (email or passwordless), one-on-one conversations, streaming LLM responses via OpenAI-compatible API (configurable key), persistent conversation history, basic input validation, error handling, logging, and unit/integration tests for API and core flows. Out of scope: multi-tenant billing, plugins marketplace, enterprise SSO, and advanced analytics. Deliver Dockerfiles, terraform/infra notes for deployment, CI for tests, and documented env vars.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Evidence score86
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productAva Chats — official product
- open sourceQuivr — prior art
- open sourcenanobot — prior art
Integrity checks
What held up, and what did not.
