Customer support decision

ShowTrust

A small team or single competent engineer can reproduce the core functionality (hosted submission page, moderation, and a tiny embeddable widget) for far less than the hosted price; ShowTrust's claims don't show durable moats that stop a rebuild.

Visit website
You pay

$4.99/mo

$60/yr

Read off the official pricing page.

You’d pay instead

$50one-off30 h to build

$30/mo4 h/mo upkeep

On cash alone, building overtakes the subscription at 7 seats.

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

  • Collect testimonial via hosted submission page → store and moderate submissions → serve embeddable widget JS that renders cached HTML cards on client sites.

What it still won’t have

  • Hosted AI-agent install skill that signs up and injects the snippet automatically
  • Built-in video transcoding + transcription infra at scale (production-ready)
  • Polished analytics per-testimonial (impressions, CTA attribution) and multi-domain attribution UI
  • Prebuilt integration guides and framework-specific snippets maintained by vendor
  • SLA-backed uptime and managed infra

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 7 seats.

Paid seatsseats

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 ShowTrust replacement using Node.js (Express), Postgres, and a tiny client widget in plain JS. In scope: (1) a hosted submission page at /c/:project that accepts text testimonials and stores them; (2) an admin moderation UI to list/approve/edit/pin testimonials; (3) a REST API endpoint that returns server-rendered HTML for a project's wall and a 5KB async embeddable widget script that injects that HTML into a host page; (4) basic webhook support for new approvals; (5) deploy instructions for Heroku or Render, and a docker-compose dev setup. Out of scope: production video transcoding/transcription pipeline, AI-agent install skills, and advanced per-testimonial analytics. Include error handling, input validation, tests for API endpoints, and CI-based deployment steps.
How we checked3 sources · 3/3 runs agreed · evidence score 88

How the score was reached

  • Build verdict base78
  • 3 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score88

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.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded