Naka platform
Riders, the Naka platform, and drivers.
Naka is building a ride-hailing platform to coordinate between riders requesting transportation and drivers providing it. The product is currently under development.
How it works
A simple model for a coordinated marketplace.
A rider requests transportation. The Naka platform is being designed to coordinate that request with driver availability. A driver can then receive a ride opportunity through the platform.
- 01
Rider requests transportation
- 02
Naka ride-hailing platform
- 03
Driver receives a ride opportunity
Two products
Designed from both sides of the marketplace.
For riders
A clear path from request to arrival.
The rider product is being designed to make requesting, understanding, and completing a ride feel direct—supported by clear information and access to help.
For drivers
Tools for the practical work of driving.
The driver platform is being shaped around access, ride opportunities, trip information, account visibility, safety, and support.
Marketplace
The work between request and ride.
Ride-hailing involves changing demand, driver availability, location, timing, and journey state. Naka is designing marketplace systems to coordinate those inputs while keeping riders and drivers informed.
- 01
Understand demand
Receive a rider request with the location and journey information needed by the platform.
- 02
Find a useful match
Evaluate available drivers and present an appropriate ride opportunity.
- 03
Coordinate the ride
Keep rider, driver, and platform state aligned as the journey progresses.
- 04
Complete and support
Handle the end of the ride, its payment state, records, and any support needs.
Subscriptions
Driver access described by a period of time.
Naka is developing daily, weekly, and monthly subscription options for drivers accessing the platform. Exact prices, fees, and complete commercial terms are not yet public.
Daily
The shortest of Naka’s planned platform-access periods.
Weekly
A planned platform-access period organised by week.
Monthly
A planned platform-access period organised by month.
Technology & safety
Infrastructure is part of the product.
Building a ride-hailing platform involves marketplace coordination, location-aware systems, ride matching, real-time communication, payments, identity, notifications, reliability, safety, backend infrastructure, and observability. These are areas of Naka’s product and engineering work, not claims that every system is already complete.
- 01
Reliable by design
Plan for system health, operational visibility, and graceful recovery as core product concerns.
- 02
Safety in context
Consider identity, ride state, communication, data handling, and support together—not as isolated features.
- 03
Secure foundations
Limit access, protect data, and design infrastructure with clear operational boundaries.
See the platform from both sides.
Read the Naka journal for product thinking, engineering notes, and company updates.