The Eliza Report
ELIZA/WIRE · 36 apps tracked · 63 events logged · 15 prices verified · last check 2026-08-06

About

What The Eliza Report is

The Eliza Report is an independent tracking publication for the AI companion app industry. At its core is a structured database — currently 36 apps under continuous watch, 15 with pricing verified at the primary source, 63 dated change events logged, last check 2026-08-06. Profiles, pricing tables, statistics, changelogs, rankings, and hands-on reviews are all views of that one database.

How we work

Every claim carries a provenance flag: a ✓ means we loaded the operator's own pricing or terms page on a dated visit and recorded what it said; everything else is marked as directional until our next pass. Price changes, policy shifts, filter changes, and shutdowns land as dated changelog events — not silent rewrites. Reviews are standardized test passes over tracked apps, scored by published weights. The full rules, including what gets an app excluded from recommendation lists, are on the methodology page.

Why "Eliza"

The site is named for ELIZA (1966), Joseph Weizenbaum's pattern-matching therapist at MIT — the first chatbot people caught feelings for. Sixty years later an industry ships the same effect at scale, for money. Somebody should be writing down what it charges and what it changes. ELIZA has the graveyard's monument spot.

Independence & funding

The Eliza Report is funded by affiliate commissions on some outbound links, always marked as sponsored. Commissions never affect the data: rankings are computed from tracked fields by published rules, warnings stay on paying apps, and apps with no affiliate program are tracked identically to apps with one. When an app we earn from does something user-hostile, that lands in the changelog like everything else — several already have.

Corrections

If a number here disagrees with what an operator's page says today, the operator may have changed it — that's the point of the tracker — but we also make mistakes. Corrections with a source get re-checked on the next pass and fixed with a dated changelog entry.