Health, home and travel decision

Flowy

A small technical team can build a useful replacement (chat + journaling + mood scoring + simple analytics) in a few weeks using existing OSS components and hosted AI APIs; no durable moats were evident from the supplied page.

View on the App Store
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/mo4 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • User writes / speaks an entry → AI processes response and provides supportive reply or task → entry is scored and stored → user reviews trends / performs calming task

What it still won’t have

  • App Store distribution, ratings, and discovery
  • Mobile-app polish (native iOS UX, onboarding, App Store presence)
  • Any proprietary AI models or data aggregation the vendor may have
  • Existing user community and network effects

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Flowy 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 AI emotional companion as a web-first app using React (frontend), Node.js + Express (backend), Postgres (storage), and OpenAI or similar for chat/sentiment. Core features in scope: 1) conversational chat UI connected to the AI API, 2) journal entry CRUD with timestamps, 3) server-side sentiment/mood scoring that produces a daily numeric score, 4) a trends dashboard (simple charts) showing score history, and 5) a library of short guided calming exercises selectable per entry. Out of scope: social/community features, full App Store native iOS packaging, advanced personalization models. Include authentication (email or magic link), input validation, API error handling and retries, rate limiting, logging, basic unit/integration tests for backend routes, and automated DB migrations.
How we checked2 sources · 2/3 runs agreed · evidence score 53

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Evidence score53

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 · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

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