Booking a ride
The full request flow, from pickup to completion.
How Kispeedy works21 questions about booking, accounts, driver applications, payments, privacy and the launch — answered for the current pilot build, including what it does not do yet.
Straight answers
Filter by topic or search for a word. Every answer describes this build, not a future version of it.
Join the passenger waitlist on the Download page. We will use those details to invite you when the Android and iOS builds are ready. Store links will only appear here once they point to published apps.
Use the driver and rider waitlist on the Drive with us page. Tell us your vehicle category — boda boda, car or tuk-tuk — and we will contact you when driver onboarding opens.
Yes — only about the launch, onboarding or a related update. We do not sell waitlist details, and you can ask us to remove your entry at any time through the contact page.
A production date is not announced yet. The waitlist is the honest place to start: we would rather invite people when the build is ready than publish a date the product cannot keep.
Not yet — this phase is a public pilot. Booking, driver dispatch, applications and payments are simulated in a shared demo state, and everything simulated is labelled. Launch comes later, one service at a time.
kispeedy is designed for Homa Bay, Kenya first — the town centre and its recognisable landmarks, with surrounding routes planned as coverage grows.
In the demo, estimates use clearly defined illustrative base-plus-distance values and, when a routing provider is reachable, the actual road distance. They are never presented as a production tariff.
The map uses real OpenStreetMap tiles. When the routing service is reachable it draws the actual road route with its distance and time. When it is not, the app says so honestly and keeps location selection working — it never draws an invented road.
Your browser provides the position after you grant permission. The app never substitutes a fixed point for your location, and it explains clearly when permission is denied or location is unavailable.
Create an account to get started. Sign-up requires email verification.
Yes. Open the passenger or driver app in your browser. Your data stays with your account.
No. Demo state lives in one browser, with a cross-tab channel inside it. Real shared, cross-device realtime dispatch is part of the production backend phase — this demo never pretends otherwise.
Demo profiles, trips and preferences survive a refresh in the same browser. The reset link in the website footer clears the demo data and returns the fictional seed accounts.
The guided application collects identity, licence, vehicle and insurance details. In this phase review is simulated. Before launch, Kenyan document requirements are confirmed per vehicle category and reviewed by people through a secure workflow.
No. Upload previews stay in your browser and are never sent to a server. We never ask for genuine identity documents in a demo — use fictional examples only.
In production, after a person reviews the records. In this demonstration, an “approved in demo data” state exists only so the workspace can be explored and is clearly marked as simulated.
No. Earnings are never guaranteed and no income estimate is published. Any amount in the driver demo is synthetic and calculated only from completed demo trips.
Never. Payment states are simulated records labelled as such — no M-Pesa, card or cash transaction occurs.
Yes, in the demo. Notifications are generated only for events that actually happened in the demo state — requests, acceptance, arrival, completion and simulated payment records.
Demo profiles stay in your browser and can be reset from the footer at any time. Waitlist details are handled only for launch updates. Read the privacy draft for how personal data will be handled in production.
A production date is not announced on this page. Join the waitlist and announcements will be made when verified — not before.
Still need help?
The full request flow, from pickup to completion.
How Kispeedy worksWhat the estimate includes and why nothing is charged yet.
Fare explanationDriver review, vehicle identification and reporting.
Safety and trustRequirements, documents and the partner waitlist.
Driver onboarding