Documents and notes decision

Journey

A competent developer can reproduce a useful self-hosted journal (entries, media, search, exports) using existing open-source components, but matching Journey's polished multi-platform apps, plugin ecosystem, and integrations would require substantially more work and resources.

Visit website
SubscriptionCustom pricing
Initial build80 hours
Monthly upkeep6 hours + $25
Evidence1/2 runs agree

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.

Code Journey publishes itself

Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.

What a replacement has to do

  • Create, search, and view dated journal entries with attached photos/videos/audio and optional location tags; sync and export entries.

What it still won’t have

  • Polished native mobile clients (iOS/Android) and cross-device app store presence
  • Official plugins ecosystem and prebuilt coach programs/templates
  • Built-in WhatsApp chat integration and other chat ingestion flows
  • Brand polish, large user base, and curated UX
  • Some advanced media organization features (smart photo suggestions) unless reimplemented

What remains hard

  • Brand trustJoin millions of Journey users, from all walks of life, to embark on your unique life journey towards a deeper gratitude for life, better health, and a calmer mind through journaling.
Read the build prompt

First-year cost

No published price

Journey 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 self-hosted web journal using Next.js (React) + PostgreSQL + S3-compatible storage (MinIO) + a small Node/Express or Spring Boot API. Implement: user registration/login (JWT), create/edit/delete journal entries with rich-text, attach/upload images/videos/audio to S3, store metadata and location tags in Postgres, per-user server-side encryption for entry content, full-text search (Postgres tsvector), export to ePUB/DOCX, and generation of read-only shareable links. Out of scope: native mobile apps, AI coach programs, and WhatsApp chat ingestion. Include error handling, unit tests for API endpoints, basic E2E tests for the editor flow, Dockerfiles for deployment, and a Helm or docker-compose manifest for single-node production.
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 quoted from the page