OnBaseRide

The problem

Getting to and from an installation often means a long commute with no transit, and general rideshare apps can't tell who is a verified service member. Rides get shared informally, without verification or a fair way to split the cost.

Who it is for: Service members and their dependents who need rides to and from military installations.

What we built

• +Military verification through ID.me, exchanged on the server, so only verified people can request or offer rides
• +A ride lifecycle from request to payment, where the database allows only one valid step at a time
• +Drivers post commutes they already make, and verified riders take a seat for a share of the trip's cost
• +Prices from driving miles times the IRS mileage rate, set only on the server, with no platform fee
• +Stripe Connect payouts to drivers, reconciled by signed webhooks
• +Installations across all 50 states and DC, each state with its own carpool rules

Engineering quality

• +Email-confirmed sign-in, plus Google, GitHub and LinkedIn
• +Row-level security on every table and on photo storage, tested as each kind of person
• +A launch switch, enforced in three separate places, so nothing goes live before licensing is in place
• +Vercel BotID on registration, pricing, verification and payment routes
• +Automated axe accessibility tests to WCAG 2.2 AA, secret scanning, static analysis and security headers

Tech stack

• Next.js
• TypeScript
• Tailwind CSS
• Supabase
• PostgreSQL
• Stripe Connect
• ID.me
• Mapbox
• Vercel