The real docs, published
These pages are rendered at build time from docs/ in the product repo — the same files that ship in the source zip. What you read here is what you get.
Getting started
From git clone to a booked ride: prerequisites, environment, seeding, first admin — then the production Docker stack.
Using the product
Manuals for the three audiences: riders booking and paying, operators running money and zones, drivers going online.
Reference
API surface, the four e-invoicing engines and their credentials, white-label branding assets, the test strategy.
- API Docs
- Government E-Invoicing — Live Wiring & Credentials
- White-labelling: making the platform yours
- In-ride audio recording — design note and deliberate deferral
- Testing — every layer, how to run it, and what each one proves
- Account deletion — API contract
- Full codebase audit — 5 September 2026
- Country gaps — what RideKit is missing, market by market
- Africa deep-dive appendix — Kenya, South Africa, Nigeria, Ghana, Uganda, Tanzania
- CodeCanyon listing — RideKit
- Google Play — the RideKit demo apps
- Capture set — 2026-09-05
- RESULTS
- Video assets
- Fleet partner guide
- Polish audit — how RideKit feels
- End-to-end test run — 5 September 2026
- End-to-end run — 2026-09-07
- Driver tips
- Your public website
Help
When something misbehaves: symptoms, causes, and the ledger's deliberate rejections explained.
Also rendered from the repo: the changelog. Internal audit artifacts (superseded status reports, gap reports) are deliberately not published here but remain part of the repo's history.