Health, home and travel decision

OULANG欧浪

A capable technical user can build a useful minimal classifieds replacement in about a week; the product's value appears to come from its user base and volume rather than proprietary tech, so self‑hosting a smaller clone is realistic.

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-off28 h to build

$40/mo6 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 OULANG欧浪 alternatives, with the arithmetic →

What a replacement has to do

  • Allow a user to create, view, search, and message about classified listings; store listings and images; moderate and remove listings.

What it still won’t have

  • existing user base and listing volume
  • brand recognition and trust
  • built-in moderation and fraud-detection workflows
  • network effects that make listings more valuable as more users join

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

OULANG欧浪 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 classifieds web app using Next.js (React) + TypeScript, Postgres (Supabase or Neon), and S3-compatible image storage (DigitalOcean Spaces or AWS S3). Core features in scope: user auth (email/password), listing CRUD with image uploads, category/tag taxonomy, full-text search on listings, simple in-app messaging or contact-by-email, admin UI to remove listings. Out of scope: payments, advanced moderation automation, recommendation/ranking ML. Deliverables must include: Dockerfiles for local dev, CI configuration (GitHub Actions) for tests and deploy, basic unit/integration tests for API routes, server-side validation, and error handling for file uploads and DB failures.
How we checked2 sources · 2/3 runs agreed · evidence score 84

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 2 cited sources+1
  • Evidence score84

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.

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