Can I vibecode Europe-Camions?

NOT REALLY · don't bother
price variesbuild time one sittingcategory 🛒 commercereplaced by 0 people

The software here is a search form over a database of listings, and yes, an agent can build that in an afternoon. What it cannot build is the several thousand trucks that dealers actually bothered to upload, which is the entire product. A private clone launches with zero inventory and zero buyers, so it answers no queries and sells no trucks. The only honest personal build is a tracker that sits on top of listings you already found: watchlists, price history, diesel of a spreadsheet with better manners. Useful if you are shopping for one truck, worthless as a replacement.

the prompt
Build a local truck shopping tracker called RigWatch. Single user, runs on my laptop, no accounts, no cloud, no telemetry.

Stack, no substitutions: Node 20, TypeScript, Express, better-sqlite3, EJS templates, plain CSS. No React, no ORM, no Docker.

Data model in SQLite:
- vehicle: id, title, make, model, year, mileage_km, engine_power_hp, axle_config, euro_class, body_type, country, dealer_name, source_url, notes, status (watching | contacted | rejected | bought), created_at
- price_point: id, vehicle_id, amount_cents, currency, seen_on (date)
- alert_event: id, vehicle_id, kind (price_drop | price_rise | stale), message, created_at, seen (bool)

Features, all server rendered:
1. Add and edit a vehicle by hand, including pasting a source URL. Optional: if a URL is given, fetch the page server side and try to prefill title and price from Open Graph tags and JSON-LD only. If that fails, leave fields blank and say so. Respect robots.txt, honour a 5 second timeout, do not crawl beyond the single URL given.
2. Record a new price point for a vehicle at any time. Show a sparkline or a simple bar list of price history plus total change since first seen.
3. List view with filters: make, country, euro class, year range, mileage range, status. Sort by price, mileage, price per 1000 km.
4. Compare view: pick two to four vehicles, render a side by side table of every field plus a computed value score (price divided by remaining useful mileage, with the assumed end of life km configurable in .env).
5. A single command, npm run check, that re-fetches every vehicle with a source_url, records a new price_point when the parsed price differs, writes alert_events for changes and for anything untouched in 30 days, and prints a summary. No background scheduler, no email.
6. CSV import and export of vehicles so a spreadsheet stays the source of truth if I want.

Out of scope, do not build: messaging sellers, payments, user auth, public listing pages, scraping search result pages, translation, image hosting beyond storing one image URL string.

Config in .env: PORT, DB_PATH, DEFAULT_CURRENCY, END_OF_LIFE_KM. Commit a .env.example, never a .env.

Deliver: npm install then npm run dev serving on localhost, a seed script with 8 fake trucks, and a README with the three commands and a one paragraph note that this tracks listings found elsewhere and is not a marketplace.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

Dealers pay because that is where the buyers already look, and buyers show up because that is where the trucks are. Neither side is paying for the search UI, which is unremarkable, they are paying for the aggregation. Personal software cannot manufacture an audience of fleet buyers in Poland or Spain, so the value never transfers to a self-hosted copy.

what you lose

xThe inventory: thousands of vehicles from dealers across several countries

xThe buyer side, so nothing you list gets seen

xDealer vetting and the loose trust layer that comes with a known marketplace

xMultilingual reach across French, German, Dutch and Spanish speaking buyers

xCross referencing by make, axle configuration, euro emission class and body type on real data

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced Europe-Camions with one prompt"
questions
Can I vibecode Europe-Camions?

Not really. Europe-Camions's value is not the code: The moat is marketplace liquidity: years of dealer inventory on one side and cross border buyers on the other. See the honest breakdown above.

How much does Europe-Camions cost?

Europe-Camions's pricing is usage-based or varies by plan · Seller FAQ states two formulas: private sellers / low-volume sellers pay per published ad (unit rates shown on the site homepage, not readable to fetchers), professionals get volume forfaits arranged by phone. The CGV say the subscription price is invoiced per the quote issued by Via Mobilis and signed by the client, renewed monthly by tacit renewal. Credit-pack rates are only visible inside the My.Via-Mobilis account area..

What do I lose by replacing Europe-Camions?

Honestly: The inventory: thousands of vehicles from dealers across several countries; The buyer side, so nothing you list gets seen; Dealer vetting and the loose trust layer that comes with a known marketplace; Multilingual reach across French, German, Dutch and Spanish speaking buyers; Cross referencing by make, axle configuration, euro emission class and body type on real data. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to Europe-Camions?

No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.

Every week, more subscriptions die.

New verdicts, new prompts, the week's most-doomed apps.
One email. Unsubscribe in one click.

free forever · no scanner spam · the prompt stays on the site, the deaths come to you

$weekly: what got a verdict, what died.