The commercial model of a marketplace is also a product decision. It shapes what the interface needs to explain, how participants plan, which questions support teams receive, and how the relationship with the platform feels in everyday use.
Naka is exploring subscription access for drivers in daily, weekly, and monthly periods. A subscription describes access through a period of time, while a transaction-based charge is tied to an individual ride. Naka has not published its final fee structure, so this distinction should not be read as a claim about every other commercial term.
That is the starting idea—not a claim that every detail is solved.
What a period makes visible
A subscription describes platform access through a defined period. That gives the product something concrete to communicate.
Before choosing, a driver should be able to see the period, price, and applicable terms once they are final. The product should then make the selected period and current access status understandable.
Daily, weekly, and monthly options are intended to support different planning horizons. A driver may value short-term flexibility, organise work around a week, or prefer a longer period of access. Final terms may affect which option is suitable, so the product has to explain them consistently.
What a subscription does not mean
Platform access is not a promise of demand. It cannot guarantee that ride opportunities will be available at a particular time or place. It cannot guarantee income, profit, or a return after costs.
Driver outcomes depend on many factors beyond an access period: rider demand, availability, location, time, vehicle costs, personal choices, and wider operating conditions. Naka’s product and communication must make that distinction clear.
Practical details around access changes, interruptions, records, and support still need careful product and policy decisions. They will be published when the rules are final.
Design the system around the terms
Offering a subscription requires more than a payment screen. The driver product, marketplace, payment handling, and support tools need a consistent view of whether platform access is active.
The platform therefore needs clear state, careful payment handling, and records that a driver and authorised support team can understand. Naka is still designing these systems and has not published implementation details.
This is where commercial simplicity can create technical responsibility. If Naka says that an access period has a defined meaning, the platform has to preserve that meaning throughout the system.
Publish details when they are real
Naka has not announced subscription prices or complete commercial terms. We will not use invented figures to make the idea appear more finished than it is.
When terms are ready, our standard will be whether a driver can understand the offer before accepting it and can verify the resulting state afterward. We will also need to test whether the model behaves as intended under real marketplace conditions.
The reason to explore subscriptions is clarity. The responsibility is to carry that clarity from the headline into the product, systems, and operating practice behind it. Naka’s driver page keeps the current model, its limits, and the still-unannounced terms in one place.