For buyers

Know what you are buying.

A dated report on an AI-built app: what was read, what was verified, and what was not.

Price: ask for one.

How you get it

  1. 1

    You send the app

    Its web address, or its GitHub repository.

  2. 2

    Its owner says yes

    We never read an app its owner has not let us read.

  3. 3

    We read it

    Every area of the map, and every line of the bar.

  4. 4

    You get the report

    One page first, the detail behind it, and the moment each part was read.

The map: 24 areas, in 6 groups

  • Safe

    • Data access
    • Keys
    • Logins
    • Access holes
    • Input safety
    • Cost guard
    • Parts
    • Old runtimes
    • Browser protections
    • Build robot

  • Works

    • Tests
    • Errors and uptime
    • Backups
    • Speed

  • Legal

    • Legal pages
    • Personal data
    • Accessibility
    • Open-source licences

  • Money

    • Payments

  • Reach

    • Email
    • Search and launch
    • Marketing

  • Run

    • Staging and deploys
    • Support

What each area checks

The bar: 29 lines a real product needs

  • 8Safe
  • 2Data
  • 3Works
  • 4Legal
  • 4Money
  • 2Reach
  • 2Run
  • 3Kept
  • 1AI features
  • Verified
  • Not current
  • Not read yet

A line counts only when its test passed on the current version and is still in time: a rule that merely ran does not count. A try on the app expires after 30 days, a performed test after 90, and a reading of the code when a night passes without a new one.

What the report does not read

  • Your running site. We read your code, not the live site, so a setting made in a host's dashboard is not seen.
  • Email. The code's side only; your domain's mail records (SPF, DKIM, DMARC) are not read.
  • Backups and restores. We look for a backup in your code. None is run, and no restore is tried.
  • Measured speed. No page is timed. The rules read your code for what makes pages slow.
  • Payments beyond the code. We read your payment code. No payment is made, test or real.
  • Other databases. Data rules are read for Supabase and Firestore. Any other database is not.
  • Your git history. We read your code as it stands now, so a key deleted but still in the history is not seen.
  • Colour contrast. It needs the live page, so it is not read.

A clean reading says the rules found nothing. It is not a promise that nothing is wrong.

Want one?

Price: ask for one.

Not sure yet? See the free check