aiTAXI
Scope and pricingAbout usContact
aiTAXI—Start with a ride request

Planned AI dispatch.
For fleets, with an operator in control.

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.

Request early access
See the planned workflow
Start with one fleet task and a written pilot scope.
Illustrative ride request
RequestPickup and passenger need
Illustrative fleet fit
FleetFit, charge and status
Illustrative route plan
RoutePrepared for review
Operator decision
DecisionOperator confirms next step
aiTAXI operator review workspace
aiTAXI
Fleet management (planned)
From request to an operator-reviewed decision ⤴
Pre-launch workflow support

The operator makes the final decision.

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

Operator controlHuman confirmation

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

What the pilot must clarify
RRequestRequest
FFleetFleet
RRouteRoute
OOperatorOperator
PPartnerPartner
SSafetySafety
SStatusStatus
RReviewReview
PPilotPilot
DDataData
BBoundaryBoundary
Request
Defined taskPickup, destination and passenger requirement are written before the pilot.
Fleet
Fit contextCharge, distance and vehicle compatibility remain planned logic.
Route
Visible planThe operator sees a prepared route and status context.
Control
Operator confirmationThe operator makes the final choice.
aiTAXI · aiNOW

FLEET. CONTEXT. OPERATOR.

Planned operations, with human control.

Tbilisi / aiNOW team

Which fleet task needs a clearer decision?

The product is planned around visible operator work, not a live taxi service.

REQUEST

Start with the request and fleet rules

The planned workflow prepares a recommendation; a real operator remains responsible for approval.

Describe a pilot task

What we clarify

  • What the passenger request contains.
  • Which vehicle constraints matter.
  • What data the pilot fleet can provide.
  • Who confirms the assignment.

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.

Which fleet workflow should a pilot examine?

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.

Request and dispatch

Prepare a vehicle recommendation for operator confirmation.

Request and dispatch
Ride-request workflowDefine incoming request and pickup rules first.
Request intakeAgree which request information the pilot receives.

Fleet status and charging

Bring planned vehicle and depot signals into a reviewable flow.

Fleet status and charging
Fleet and depot workflowFleet and depot scope is agreed in writing.
Dispatch ruleAssignment follows only the agreed operating process.
Capacity scopeConfirm request and channel capacity in writing.

Operator and safety review

Keep difficult cases, approvals and incident context visible.

Operator and safety review
Route reviewReview route and city data within the agreed scope.
Operator approvalDefine where an operator must be involved.
Partner boundarySeparate partner and provider responsibility.
Safety reviewSafety questions stay with human review.

Hybrid fleet planning

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

Hybrid fleet planning
Fleet statusStatus fields follow the written pilot scope.
Pilot scopeAgree pilot volume and timing before starting.
Integration boundaryDo not treat integration as an active fleet without confirmation.
Fleet context changes by operator

The pilot starts with the fleet you actually have

Zones, vehicles, rules, data and human responsibility vary, so aiTAXI remains a written prelaunch scope until a suitable partner and safety review exist.

Passenger needs

Accessible passenger requests

A pilot can test how accessibility requirements become fleet-fit criteria.

Passenger requirements are explicit.
Vehicle compatibility is checked before approval.
The operator keeps final responsibility.
No completed ride or ETA is claimed.
Describe an accessibility workflow
Demand planning

Demand peaks and depot work

Operators can examine how charging, cleaning and maintenance fit around demand.

Peak periods are planning inputs.
Depot tasks remain a pilot scope.
Vehicle readiness is not live data here.
Any connection needs partner approval.
Describe a depot workflow
Fleet zones

Zones and mixed fleets

A future pilot may compare zones, request patterns and human-driven or autonomous vehicles.

Zones are defined before testing.
The queue remains operator-reviewed.
Vehicle partner scope is explicit.
No regional rollout is promised.
Describe a zone workflow
Delivery operations

Delivery and fleet fit

Delivery requirements can become a planned vehicle-fit and operator-review workflow.

Delivery constraints are written.
Fleet data is connected only with permission.
The recommendation is not a booking confirmation.
Written pilot terms come first.
Describe a delivery workflow
Vehicle operations

Vehicle condition and service

Charge, sensor and service signals can be mapped into a planned operator view.

Signals and thresholds are defined.
Service actions remain human-supervised.
No real-time telemetry is implied.
Safety review is separate.
Describe a vehicle-status workflow
Governance

Safety and incident review

Fleet operations need a clear record of decisions, sources and responsibility.

Incident sources are named.
The operator role is explicit.
The record is planned, not a production report.
Legal and safety review remains required.
Describe a review workflow

From fleet question to written pilot scope

We define the request, fleet fit, data boundary, operator responsibility and review criteria before implementation.

1
Describe the fleet task

Choose one request, dispatch, status, depot or incident workflow to examine.

2
Map data and operator control

Identify vehicle/fleet inputs, partner access and the decision the operator must confirm.

3
Write and review the pilot

Agree scope, price and safety conditions in writing before any implementation decision.

Pre-launch operations with control

The operator remains responsible

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.

Describe a pilot workflow

Start with a ride request

Pickup, destination and passenger requirements are the input to a planned workflow.

Boundary 01● Operator approval

Check fleet fit

Distance, charge, accessibility and compatibility are illustrative pilot logic until connected.

Boundary 02● Operator approval

Prepare a visible route

The route and expected arrival are planned information for review, not a live ETA guarantee.

Boundary 03● Operator approval

Keep a human in control

The operator confirms assignments and handles difficult cases.

Boundary 04● Operator approval

Separate partner connections

Maps, fleet, charging and telemetry require a written scope and approved access.

Boundary 05● Operator approval

Review safety before use

Any real-world pilot needs separate legal, safety and partner approval.

Boundary 06● Operator approval
Our role

A planned fleet layer, not a live taxi service

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.

Andro Kasparov · CEO
Andro Kasparov
Co-founder·CEO
Tornike Epitashvili · CTO
Tornike Epitashvili
Co-founder·CTO
Tbilisi, GeorgiaaiNOW · 2026
[Pre-launch fleet answers]

Questions about aiTAXI

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.

It is planned to prepare dispatch and fleet context for taxi companies and mixed or autonomous fleets, with a human operator keeping final approval.

No. The page is an interest and pilot-scope preview, not a live booking service.

One fleet workflow, such as a request, vehicle fit, operator review, status or incident record, plus written data and safety conditions.

The planned workflow can prepare a recommendation, but a real operator remains responsible for the decision.

No live location, current fleet capacity or guaranteed ETA is claimed in this preview. Any connection requires a separate partner scope.

It is planned for autonomous and mixed fleet workflows, but aiNOW does not build or sell autonomous vehicles and no vehicle partner is implied.

A sample request, fleet and vehicle rules, available status signals, partner access conditions and the operator review boundary.

Depot, charging, cleaning and maintenance workflows are planned scope to examine, not live operational results.

No. Safety review, partner review and human approval remain required before any real-world use.

Pricing is unknown. Setup and ongoing terms are written after the pilot task, data boundary and safety conditions are understood.

No current booking tariffs, driver earnings, completed rides or production capacity are published by this preview.

Taxi companies and fleet operators exploring a supervised dispatch or fleet-operations pilot.

A fit review and written pilot scope. Implementation depends on partner, legal, safety and data approvals.

Describe your fleet, one workflow and the operator decision you want to examine. This preview records interest; it does not create a ride or fleet action.

Still have a fleet question?
Describe a pilot task

Who aiTAXI is for

Taxi companies and fleet operators exploring a supervised dispatch or fleet-operations pilot.

  • You can describe one fleet workflow to examine.
  • You have an operator who keeps final approval.
  • You can identify available fleet/vehicle data and a partner boundary.
  • The product is still being prepared; terms and pricing are agreed in writing.

aiTAXI is not ready for...

A live booking service, a production fleet, guaranteed ETAs, current ride tariffs or autonomous operation without separate partners and safety approval.

Not sure which fleet task to scope? Start with one request or operator decision.

Request an aiTAXI pilot discussion

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.

We will write to you on WhatsApp, not call you separately.
Email us
aiTAXI is pre-launch and does not run a live fleet. Pricing is unknown until a written pilot scope is reviewed. Real-world use requires partner, legal and safety approval.
aiTAXI

aiTAXI by aiNOW

Research and planning for an AI taxi-fleet dispatcher. The product is not live yet.

Request early access

Products

  • aiCHATS
  • aiCALL
  • aiCONTENT
  • aiADS
  • aiMUSIC
  • aiSTAFF
  • aiBRAIN
  • aiOFFICE
  • aiDOCS
  • aiWEB
  • aiAPP
  • vibeCODING
  • aiVISION
  • aiRADAR
  • aiAUDIT
  • aiJURIST
  • aiTAXI (planned)

Industries

  • Taxi operators
  • Mixed fleets
  • Autonomous fleet planning
  • Depot operations
  • Safety review
  • Pilot terms

Resources

  • Blog
  • How we start
  • Questions and answers
  • Send a task
  • Email us

Legal and security

  • Privacy
  • Terms of service
  • [email protected]
  • Tbilisi, Georgia
შპს ეი აი ნაუ © 2026. All rights reserved.
[email protected]Back to top ↑