Passenger app
- Request and track a ride
- Fare and payment method
- Receipt, rating, and support
A simple path from business license and working software to INSA, MInT, transport permission, Telebirr, and legal launch.

Primary source
How to Start a Ride Hailing App in Ethiopia · Updated 12 August 2026
The launch roadmap
Complete the business, software, inspection, permission, and service-onboarding work as one connected process.
Register the company, TIN, commercial registration, and the correct transport activity before the full build.
Confirm field 71113 and vehicle libre requirements.
Prepare passenger and driver apps plus dispatch, admin, support, finance, safety, and reporting tools.
Include hosting, domain, database, APIs, and test accounts.
Create the logo, keep editable files, document source-code ownership, and prepare copyright evidence.
Copyright and trademark are separate protections.
Submit the mobile, web/admin, API, architecture, hosting, and role-based test scope for inspection.
Use separate mobile, web, and API documentation.
Fix assessment findings, provide closure evidence, and retain the final certificate and report.
Later approvals may request the INSA result.
Bring the company records, app description, server information, INSA result, and working demo evidence.
Ask for the current ride-hailing platform process.
Prepare the license, vehicle evidence, hosting information, INSA result, and any requested MInT evidence.
Verify the responsible office before travelling.
Request payment, SMS/OTP, and call-center services after the required company and approval documents are ready.
Prepare the company stamp, letter, and bank account.
Launch only after approvals, production testing, driver checks, support, safety, and reconciliation are ready.
Start with one controlled service area.
What must be built
Passengers and drivers see the apps. Your team needs the operating system behind every trip.



Keep one evidence folder
Exact requirements can change. Use these as preparation categories, then confirm the current checklist with each institution.
Important: This is practical technical guidance, not legal advice. Verify current procedures, forms, locations, and fees before acting.
Ride-hailing software company in Ethiopia
The strongest claim is working evidence: product experience, approval readiness, and a live platform reference.
Explore ride-hailing developmentThe source article records experience across Peace Ride, Enova Super App, and Gadaa Taxi—not only a demo concept.
Peace Ride is presented as live, INSA-approved, Telebirr-integrated, and operating on AWS.
DreamTech's CTO previously worked on ride-hailing systems at Feres and RIDE before founding the company.
The same team can align apps, admin tools, documentation, inspection readiness, payments, and launch support.
Common questions
No. You also need dispatch, admin, support, finance, safety, driver verification, hosting, APIs, records, and the approvals that apply to your operating model.
The DreamTech article identifies field 71113, Land transport and related services. Confirm the current wording and evidence with the responsible office before filing.
No. INSA inspects digital-system security. The responsible transport authority handles transport permission.
Yes, when approved for the operation. The system should record the method, prevent duplicate collection, issue receipts, and reconcile cash and digital payments separately.
Use a controlled service area, verified drivers, staffed support, tested payments, clear safety procedures, and daily review of trips, cancellations, complaints, and settlement exceptions.
Have a city, driver model, or launch date in mind?