Uncategorised decision

AuraClaw

Public pages provide no product detail; a capable developer can assemble a useful replacement from mature open-source scanners (Nuclei, Tsunami) but delivering a polished, hosted product with support and proprietary feeds is multi-week and nontrivial.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off120 h to build

$0/mo10 h/mo upkeep

No published price to break even against.

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. All AuraClaw alternatives, with the arithmetic →

What a replacement has to do

  • Integrate open-source scanning engines, schedule and run scans, store and present results, and notify users.

What it still won’t have

  • proprietary integrations, commercial support, polished UI/UX
  • any closed-source data or proprietary vulnerability feeds
  • single-vendor SLAs and hosted availability

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

AuraClaw 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 minimal hosted vulnerability-scanning web app using Go for backend, React for frontend, Postgres for storage, RabbitMQ (or Redis) for job queue, and Docker to run scanner engines. Core features: user authentication (single admin account), import target lists, launch on-demand scans and schedule recurring scans, run open-source engines (Nuclei and zgrab2) in isolated containers, parse engine outputs into a unified schema, store results in Postgres, searchable results UI with filters and CSV export, webhooks/email notifications, basic usage metrics, and logs. Out of scope: multi-tenant billing, trained ML models, proprietary vulnerability feeds, and integration marketplace. Include error handling for container failures, timeouts, and malformed outputs; include unit tests for parsers and integration tests for job queue and scan execution.
How we checked3 sources · 2/3 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.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded