Powered by RashiEvery ride,verified.
RidePerk combines AI-powered fleet verification with real-time in-ride safety monitoring — giving operators complete visibility into their fleet, and riders always-on protection throughout every journey.
Built for the full ride lifecycle.
Fleet safety and in-ride protection, in one platform.
Live fleet verification
Drivers submit a live video walkthrough and document photos via a one-time link. No gallery uploads — all media is captured in real time to prevent staged or manipulated submissions.
Document fraud detection
VIN, license plate, registration, and ownership data are cross-checked automatically. AI flags manipulated images, mismatched documents, and branding non-compliance.
Real-time in-ride monitoring
Detects raised voices, threats, harassment cues, and behavioral escalation patterns while the trip is active — passively, without requiring rider action.
Graduated safety response
Starts with a discreet rider check-in, then escalates to encrypted incident capture and pre-registered emergency contact alerts based on assessed risk level.
From fleet check
to protected ride.
1inspection.start({2 driver_id: 'drv_001',3 trigger: 'scheduled_audit',4 media: ['live_video', 'vin_photo',5 'license', 'registration']6})
Two gaps riders face
every time they board.
Most ride-hailing safety tools address only one problem: in-ride incidents. But the vulnerability starts before the ride — with unverified vehicles, falsified documents, and unchecked driver compliance. RidePerk is built to close both gaps.
Source: U.S. GAO report GAO-24-106742 (published Feb 2024).
What we're
building toward.
These are alpha-stage commitments, not reported achievements.
Two safety layers.
One connected platform.
RidePerk connects AI-powered vehicle verification, real-time audio analysis, and operator-grade fleet intelligence in one complete safety platform.
Privacy is
part of safety.
RidePerk is designed for explicit consent, limited retention, and practical controls that keep users informed and in control.
On-device processing where possible
Audio understanding is designed to run on-device when hardware and model constraints allow it.
Opt-in per trip
Riders explicitly choose monitoring per trip or enable always-on mode in app settings.
Encrypted flagged incidents
When incidents are flagged, retained audio and GPS context are encrypted in transit and storage.
Auto-deletion defaults
Retention windows are configurable, with a default 7-day policy for flagged incidents.
Built for ride-hailing
operators and partners.
RidePerk is built as a platform for ride-hailing operators — fleet compliance monitoring, in-ride safety intelligence, and partner APIs as pilots expand.
Fleet verification API
Schedule or trigger driver inspections, receive PASS / FLAG / FAIL verdicts, and route flagged cases to your review team.
In-ride safety hooks
Subscribe to real-time distress events and graduated response triggers for live trip monitoring.
Operator dashboard
Fleet-wide compliance view, inspection history, and incident tracking in one interface.
Privacy-first by default
Configurable retention windows, encrypted incident storage, and per-trip consent controls.
inspection.trigger({driver_id: 'drv_001',trigger: 'random_audit',notify_via: 'sms'})// driver receives one-time link
Illustrative — actual SDK shape may differ.
Common questions from riders, operators, and partners.
How does RidePerk's fleet verification work?
Operators schedule or trigger driver inspections. Drivers receive a one-time SMS link and capture a live video walkthrough alongside document photos. AI cross-verifies VIN, plates, ownership, and branding compliance — returning PASS, FLAG, or FAIL. No pre-recorded material is accepted.
Does vehicle verification happen before every single ride?
No. Fleet verification is an operator-side compliance tool — used during driver onboarding, on scheduled audit cycles, or triggered after a complaint or incident. It is designed for fleet quality control at scale, not as a per-ride gate.
How does RidePerk protect privacy?
Both services use explicit consent and minimal data retention. Vehicle inspection media is stored only for the verification window. In-ride audio is only retained when an incident is flagged, encrypted in transit and storage, and auto-deleted after 7 days by default.
Is RidePerk available publicly today?
Not yet. Both services are in closed alpha, and open beta access will follow after safety and reliability validation milestones are met.
Help shape safer
rides from day one.
RidePerk is in closed alpha. Join the waitlist to get early access, influence product direction, and participate in pilot validation.
Beta launch target: Q4 2026