Health, home and travel decision
trainquille.fr
A capable technical user can reproduce a useful subset (search + map + simple découpage) using public APIs and the cited prior-art, but the full polished product with continuous crawling, reliability, and any privileged data access is larger and operationally heavier than a one-person weekend project.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off80 h to build
$50/mo6 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
- User enters origin/date or destination/date → query timetable/availability source → compute matching trips (including reverse and split-leg alternatives) → show results on an interactive map and list; allow exploring alternatives (nearby stations, BlaBlaCar).
What it still won’t have
- Polish and UX of the commercial site (maps, search refinements, premium features)
- Any official data-sharing agreement or privileged SNCF data access
- Scale, monitoring, and reliability at production traffic
- Built-in premium account and billing/support workflows
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
trainquille.fr 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
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
Build a minimal self-hosted Trainquille-like service: use Node.js + Express for the backend, Postgres for storage, Redis for caching, a background worker (BullMQ) to prefetch popular station availability, and React + Leaflet for the frontend. Core features in scope: (1) query live train timetables/availability via public SNCF/transport APIs or HTML scraping module, (2) classic origin→dest search, reverse-search mode, (3) itinerary découpage that splits a trip into free segments and proposes nearby stations, (4) map view showing available seats, (5) optional BlaBlaCar link suggestions, (6) simple user auth (email) and basic caching. Out of scope: paid subscriptions/billing, analytics dashboards, mobile apps, and any negotiated official SNCF data agreements. Include retries, rate-limit handling, error logging, unit and integration tests, and Docker manifests for deployment.
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score59
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.
- official productTrainquille product page — map and availability
- official productTrainquille — search modes mentioned
- official productTrainquille — découpage and BlaBlaCar mention
Integrity checks
What held up, and what did not.
