Security and privacy decision

wasitaigenerated

A competent developer can build a useful text-only AI-detection replacement in about a week, but reproducing the vendor's full multimodal coverage, claimed accuracy, and enterprise features is not realistic without larger engineering and data investments.

Visit website

Built by Patrick Gerard, who ships 6 products in this index

You pay

$9.99/mo

$120/yr

Read off the official pricing page.

You’d pay instead

$50one-off20 h to build

$50/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 6 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

  • Accept text, run an AI-detection model/classifier, return JSON with isAI/confidence/patterns, log usage and deduct credits.

What it still won’t have

  • Image, audio and video detection (multimodal)
  • Cryptographic 'verified' content-credential checks
  • Bulk/enterprise processing optimizations and SLAs
  • Pretrained proprietary models and claimed accuracy benchmarks
  • Built-in analytics/dashboard parity

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 6 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 text-only AI-content detection service using FastAPI + Uvicorn, PostgreSQL (or SQLite for single-user), and Hugging Face transformers (or an external LLM classifier) for inference. Core features: POST /v1/detect/text that accepts {content}, authenticates via Bearer API key, returns JSON {isAI, confidence, patterns, sentences[]}, per-word credit accounting, request logging, basic admin UI to view usage, and automated tests for endpoints and billing. Out of scope: image/audio/video detection, cryptographic verification, enterprise clustering. Deploy as a Docker container to a single small VPS (or Heroku) with HTTPS, include error handling, input validation, and CI that runs tests.
How we checked2 sources · 3/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • 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 · 2

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