aiTAXI is a pre-launch platform for taxi companies and mixed fleets. It receives a ride request, checks fleet fit and prepares a visible decision for an operator; it does not run a real fleet today.




We define the request, fleet rules and partner data first. The operator then sees the prepared context and makes the final choice.

The platform prepares context; we do not claim a live fleet or an automated safety decision.






Planned operations, with human control.
Tbilisi / aiNOW teamThe product is planned around visible operator work, not a live taxi service.
REQUEST
The planned workflow prepares a recommendation; a real operator remains responsible for approval.
What we clarify
First step
Describe one ride request, the vehicle constraints and who confirms the decision.
What we need from you
A sample request, fleet rules and pilot access conditions.
Start with a ride request, vehicle fit, operator review and written pre-launch pilot terms. No current booking tariff or live fleet capacity is claimed.
Prepare a vehicle recommendation for operator confirmation.

Bring planned vehicle and depot signals into a reviewable flow.

Keep difficult cases, approvals and incident context visible.

Map a future connection to a mixed or autonomous fleet partner.

Zones, vehicles, rules, data and human responsibility vary, so aiTAXI remains a written prelaunch scope until a suitable partner and safety review exist.
A pilot can test how accessibility requirements become fleet-fit criteria.
Operators can examine how charging, cleaning and maintenance fit around demand.
A future pilot may compare zones, request patterns and human-driven or autonomous vehicles.
Delivery requirements can become a planned vehicle-fit and operator-review workflow.
Charge, sensor and service signals can be mapped into a planned operator view.
Fleet operations need a clear record of decisions, sources and responsibility.
We define the request, fleet fit, data boundary, operator responsibility and review criteria before implementation.
Choose one request, dispatch, status, depot or incident workflow to examine.
Identify vehicle/fleet inputs, partner access and the decision the operator must confirm.
Agree scope, price and safety conditions in writing before any implementation decision.
aiTAXI is planned to prepare context for a fleet decision. It does not operate a live fleet, choose a driverless vehicle without approval, or replace safety and partner review.
Pickup, destination and passenger requirements are the input to a planned workflow.
Distance, charge, accessibility and compatibility are illustrative pilot logic until connected.
The route and expected arrival are planned information for review, not a live ETA guarantee.
The operator confirms assignments and handles difficult cases.
Maps, fleet, charging and telemetry require a written scope and approved access.
Any real-world pilot needs separate legal, safety and partner approval.
We are aiNOW, a Tbilisi team researching AI systems for real operating work.
aiTAXI is pre-launch: we clarify the fleet task, partner boundary and operator review before a written pilot scope.
We do not claim a working fleet, completed rides, driver earnings or current booking prices.
Direct answers about the planned workflow, operator control, scope and unknown pricing.
No. aiTAXI is pre-launch and does not currently operate a production fleet or accept real bookings.
No. The page is an interest and pilot-scope preview, not a live booking service.
The planned workflow can prepare a recommendation, but a real operator remains responsible for the decision.
Taxi companies and fleet operators exploring a supervised dispatch or fleet-operations pilot.
Describe your fleet, one workflow and the operator decision you want to examine. We will review fit and provide written scope and terms before any implementation decision.