AI assistants and search decision

MindPet

A competent engineer can build a usable self-hosted MindPet-like assistant (chat UI, LLM integration, storage) in a few weeks and run it cheaply, but reproducing a polished paid product with integrations, hosting, support, and brand is non-trivial; use prior-art self-hosted assistants to accelerate development.

Visit website

Built by Kites.Dev, who ships 6 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off60 h to build

$20/mo6 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 MindPet alternatives, with the arithmetic →

What a replacement has to do

  • User enters prompts -> assistant sends requests to an LLM -> assistant returns responses and stores conversation history

What it still won’t have

  • Hosted uptime, monitoring, and SLA
  • Proprietary integrations and any vendor-managed features
  • Brand, polish, onboarding flows, and commercial support
  • Potential proprietary data or model training the vendor may offer

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

MindPet 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal self-hosted web AI assistant using React for the frontend, Node.js + Express for the backend, Postgres for conversation storage, and Redis for sessions. Core features in scope: user signup/login (email or OAuth), persistent conversations, sending user prompts to an LLM provider (configurable OpenAI/Anthropic key), streaming responses to the UI, and basic rate-limiting. Out of scope: training custom models, multi-tenant billing, mobile apps, advanced analytics, or enterprise SSO. Include input validation, error handling, unit tests for backend routes, and deployment scripts (Docker + docker-compose or Cloud Run).
How we checked3 sources · 1/2 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • Evidence score60

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.

Integrity checks

What held up, and what did not.

! 1 of 2 runs agreed; the verdict is the middle of them✓ Citations limited to fetched pages! 1 moat recorded