// NIJITECH PRODUCT · MOBILITY
cep taxi
A mobility platform in your pocket — instant matching, live tracking.
cep taxi runs location-based passenger–driver matching on niji core. It finds the nearest driver within seconds, draws the route, tracks the trip live and completes contactless payment.
cep taxi is a location-based mobility platform. It matches a passenger with the nearest driver within seconds, draws the route, tracks the trip live and completes contactless payment. The user is shown how the fare is calculated; data is processed on-premise or in the cloud.
Live city & matching map — the demo where the product proves itself
Match
Live status
- Request created · from location+0.0 s
- Nearest driver found+2.4 s
- Route drawn · live tracking on+3.1 s
- En route · arrival in about 6 min+3.6 s
01 — HOW IT WORKS
The niji core pipeline: request, match, ride, pay.
Request
You create a request from your location with one tap; destination and route are drawn immediately.
Every one of these steps runs on the same backbone: the niji core pipeline →
Match
niji core finds the nearest available driver and matches you in <3 s .
Ride
The route is drawn, the car is tracked live on the map and the ETA updates in real time.
Pay
Payment completes automatically and contactlessly at the end of the trip, and the receipt is explainable.
02 — FEATURES
From request to arrival, in one flow.
Instant matching
Location-based search finds the nearest available driver within seconds.
Live location tracking
The car’s position and route update on the map in real time.
Contactless payment
Payment completes automatically and contactlessly at the end of the trip.
ETA & route
Arrival time and route are calculated dynamically against traffic conditions.
Driver rating & safety
Verified drivers, two-way ratings and trip sharing.
Multi-city
One account, an uninterrupted riding experience across several cities.
Enterprise / fleet
Company accounts, fleet management and central billing.
Explainable pricing
Every fare component is transparent: distance, duration and multipliers appear on the receipt.
Data processing region
Location and trip data are processed on-premise or in the cloud; in cloud use, processing takes place in the US and EU regions.
03 — TRUST & COMPLIANCE
The enterprise trust layer, on by default.
Measurement summary
FREQUENTLY ASKED QUESTIONS
What people ask about cep taxi.
How are passengers and drivers matched?
cep taxi uses location data to find the nearest available driver within seconds. The matching runs on niji core, weighing distance, estimated arrival time and driver availability together.
How is the fare calculated?
Pricing is explainable: the user is shown which components the fare is made of (distance, duration, conditions). An estimated amount and the route are presented before the trip.
How does payment work?
Payment is contactless and automatic; it completes through the saved method when the trip ends. There is no cash handling and no in-car payment step.
How is driver safety ensured?
Drivers go through rating and safety verification. Live location tracking runs throughout the trip, so the route and progress stay visible to both sides.
Is enterprise or fleet use possible?
Yes, cep taxi supports enterprise and fleet mode. Companies can manage employee transport from one place, with trips and spending collected under a corporate account.
Does cep taxi work in more than one city?
Yes, the platform is designed for multi-city support. Each city is managed with its own driver pool and matching parameters.
What records are consulted in a post-trip dispute?
The route, the trip duration and the components that make up the fare are all recorded. Most disputes arise from not knowing how a fare was reached; when the components are visible from the start, there is little left to argue about.
How long is trip data retained?
The retention period for location and trip records is defined at setup rather than fixed as a product default. Location is personal data and the most sensitive kind an app of this sort holds, so the period and the access rights are agreed up front.
Why does mobility need a matching engine of its own?
The matching decision is made within seconds on continuously changing location data, and a wrong decision has a concrete cost: a waiting passenger, a driver returning empty. That is why mobility matching does not run on general-purpose queueing logic but on its own engine built on niji core.
For more, see the general FAQ · for terminology, the glossary
04 — GET STARTED
Let us launch cep taxi in your city.
Let us connect cep taxi to your city’s mobility flow and see your first matches within days.
Talk to the team →