Health, home and travel decision

Subbasta

A functional replacement (listing ingestion, search, notifications) is realistic for one capable developer to build and maintain; nothing on the site indicates irreproducible data, proprietary models, or regulatory barriers.

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

$50one-off22 h to build

$30/mo3 h/mo upkeep

No published price to break even against.

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

  • Ingest new auction listings, store them, let users search/filter listings, and send notifications for matched auctions.

What it still won’t have

  • Any official affiliation or legal audit/validation from the Law Courts
  • Guaranteed accuracy or legal status of auction data
  • Proprietary or curated workflows the original site may provide
  • Polish of a production product (mobile apps, heavy UX refinements, multilingual support)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Subbasta 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 small web app using Django (or Flask) + Postgres, deployed on a single VPS (DigitalOcean). Core features: 1) periodic scraper job (Celery or cron) that fetches and parses judicial auction listings into a normalized Postgres schema, with deduplication and timestamping; 2) HTTP UI with listing index, search and filter by location/price/date, and detail pages; 3) user accounts with saved searches and email notifications via SendGrid; 4) admin CSV export and basic logging. Out of scope: legal verification of listings, payment processing, and mobile native apps. Include error handling for scraper failures, tests for scraping/parsing and API endpoints, and Docker-based deployment scripts and simple Terraform or Ansible for provisioning.
How we checked1 sources · 2/3 runs agreed · evidence score 78

How the score was reached

  • Build verdict base78
  • Evidence score78

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 · 1

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