The console
One console for Cybercab fleet operations.
Mission control for assets that drive themselves.
Not a dashboard of charts. The screens your day actually runs on: what is wrong with the fleet right now, who has been sent to fix it, what it cost, and whether the ride network’s numbers agree with your own.
Every job on one board
Tickets move through detection, transit, work, QA and closed — grouped by the kind of work, so a cleaning backlog never hides a car waiting on brakes.
Rules you can test before you trust
Say what should happen — light dust to the budget detailer, biohazard to a specialist, anything over your ceiling to your phone. Then replay last month against those rules and see what they would have cost before a single car moves.
Check the network’s math
Your dispatch log against their statement, line by line. When the ride counts disagree you can see it, query it, and keep the difference on the record instead of taking the number on faith.
Your bench, ranked
Stack your preferred vendors in order, decide whether the open marketplace can step in, and block anyone you will not work with. Per category, because your wash and your mechanic are not the same relationship.
The other end of every dispatch
Your rule becomes this: a ping on a vendor’s phone with the price, the distance and the time the work should take, and thirty seconds to accept. They see where your cars are staging, so the nearest one usually takes it.
Quotes above your ceiling come to you as a push instead, with approve, decline and rebid on the notification.
See the vendor side
What we watch
What the console watches, and what each signal turns into.
Labelled honestly. Some of this reads live telemetry today; some describes an input no manufacturer currently publishes.
Interior condition
The signal that decides whether the next rider gets in or complains. Tesla publishes no interior-condition field, so this comes from rider reports, the previous vendor’s photos and hub inspections — and from cabin sensing if a vehicle ever exposes it.
Tire pressure and rapid loss
These cars are heavy and make instant torque, so tread goes quickly. A slow leak becomes a scheduled mobile-tire job; a rapid loss becomes an immediate one.
State of charge and location
Charge against distance to the nearest working charger, so a car that is going to strand itself is caught while it can still drive.
Fault codes
Manufacturer fault codes routed by severity: some are a note on the vehicle record, some ground the car and open a ticket with a certified shop.
API connection health
An expired token or a dropped telemetry stream is itself an alert. A fleet you cannot see is a fleet you are not operating.
Rider reports
Complaints that arrive after the ride are traced back to whoever last had access to the car, which is what makes the reliability index answerable.
“Working in test” means the console reads it today from Tesla’s fleet API against simulated vehicles. It has never run against a customer fleet, because none exists yet.
Alerts
What reaches your phone, and what stays on the board.
An operations tool that treats everything as urgent gets muted within a week. Three tiers, and you decide what sits in each.
- Car stranded or unreachable
- Escalates on a ladder — push, then SMS, then a voice call — instead of waiting for the next telemetry poll.
- Collision or hard-impact event
- Pulls the car off the network, preserves the telemetry window around the event, and notifies you before the ride network does.
- Quote above your ceiling
- Arrives as a push with the estimate and the photos, and approve, decline and rebid on the notification itself.
- Nobody accepted the dispatch
- After the bench and the open marketplace have both been tried, the ranked options come to you rather than the job sitting silently.
- Photos failed QA
- The job reopens with the failing check named, and the vendor’s first-pass rate takes the hit.
- Settlement line does not reconcile
- A ride count that disagrees with your dispatch log is flagged for query rather than absorbed.
Reconciliation
Checking the revenue you do not control.
Ride revenue is the one number an operator cannot audit from the inside. Rather than print the network’s figure as fact, the console runs it against your own dispatch record.
01
Import the statement
The ride network’s settlement statement lands as a period you can open, with each vehicle and each line item intact.
02
Match against the dispatch log
Our own record of what each car did — on network, in service, off duty — is matched line by line against what you were paid for.
03
Surface the differences
Anything that does not match is listed with both numbers side by side, rather than reconciled away into a single total.
04
Raise and keep the record
A queried line keeps its evidence attached and stays on the record until it is resolved, so a pattern across periods is visible.
See the console against your own numbers.
The console runs today against Tesla’s fleet API in a test environment with simulated vehicles. Join the early-access list and we will walk you through it, tell you where your market sits in our launch order, and answer the questions we do not have public answers to yet.