JM is the reference: Turo-style rent + Uber-style driver ops on site.
Use this guide to stand up the same thing for any local community —
neighbors rent cars, list for local use, rideshare with insurance that allows it, VIN checks, AI help, payments.
Not software for sale. One lot per community on Cloudflare.
Full file guide: RJEC\src\car-portal\docs\COMMUNITY-SETUP-GUIDE.md
1. What you get
Mode
Local use
Rent
List by VIN → photos → price → renter books (neighbor or facility)
Driver / profit-share
Approved driver uses car on rideshare apps; revenue split
P2P helper (how to list, what to bring) — human still decides
2. Money — what to use
Recommended path Phase A — one facility (like JM): one Stripe account + Checkout. Phase B — many neighbors each own cars: Stripe Connect marketplace
(destination charges, platform fee, owners get paid out). Adyen — only if you outgrow Stripe or need special markets later.
Choice
Use when
Single Stripe
One business runs the lot and money
Stripe Connect
True P2P: many car owners, one community checkout
Adyen
Enterprise / multi-country later — not day one
Never put payment secrets in public Google Scripts. Secrets stay on Cloudflare only.
3. Cloudflare stack (same every time)
Part
Job
Worker + site
Lot, VIN, list, rent, drivers, owner desk
D1
Cars, people, bookings, statuses
R2
Photos
Workers AI
Chat help for owners & renters
Secrets
Stripe + owner key
Google Drive
Docs people already know; store links only
4. Repeat steps
A. Name the community
Name, owner email, domain, written insurance rules, state.