XoomPark is an enablement layer for AV fleet-ops partners (firms like Moove, Avis, or Transdev) to source, qualify, reserve, and audit off-depot ground-service capacity. It coordinates sites, not vehicles, and does not replace the operator.
Fleet-ops partners use XoomPark to source, qualify, reserve, and audit off-depot ground-service capacity that runs under their own standard work. XoomPark handles site discovery, qualification, access rules, reservation and session records, exception handling, SLA tracking, and evidence capture. The operator still runs the vehicles, the people, and the service. XoomPark is the coordination and audit layer underneath distributed private-site capacity, not a competitor to the operator.
| If you are a fleet-ops partner, XoomPark gives you | What it is not |
|---|---|
| A way to find and qualify off-depot ground-service sites in a new city | A consumer parking app or parking marketplace |
| Reservation and session records for distributed nodes | A dispatch or routing system that controls your vehicles |
| SLA tracking and evidence that a session happened correctly | A maintenance provider, charger owner, or autonomy company |
| An audit trail your client and your finance team can both trust | A replacement for your operations team or standard work |
What does it mean for XoomPark to be an enablement layer for fleet-ops partners?
XoomPark sits underneath the operator, not in front of them. A fleet-ops partner is the firm contracted to run ground operations for an autonomous fleet: staging, overnight storage, cleaning, inspection, recovery holding, and service coordination between trips. XoomPark gives that partner the records and coordination to extend those jobs beyond their own depot, onto distributed private-site capacity, without changing how the partner already works.
The split is deliberate. The property defines permission: where a vehicle is allowed to go and what it is allowed to do there. The fleet validates capability: whether its vehicle can actually operate at that site. XoomPark coordinates reservation, access, workflow, SLA, evidence, and audit across the sites. The operator keeps the fleet relationship and the service quality. XoomPark keeps the proof.
Why off-depot capacity is the constraint for AV operations partners
Depots will exist, but depots alone do not solve distributed city operations. A robotaxi fleet does not idle politely next to its depot all day. Vehicles need to stage near demand, hold during a service exception, queue near charging, and reset between trips across a wide service area. A single depot footprint cannot absorb that geographic spread, and acquiring more depot real estate in a dense city is slow and expensive.
For a fleet-ops partner, this shows up as a capacity-and-evidence problem at the same time. The partner needs more ground-service locations than it can own, and it needs to prove to its fleet client that every off-site session met SLA. Robotaxi service areas now span entire metros — Waymo runs commercial service across ten US markets including city-wide coverage in Phoenix, San Francisco, Los Angeles, and Austin (TechCrunch, Mar 27, 2026) — far more geography than a single depot can cover near demand. Without a coordination layer, off-depot capacity is a spreadsheet of informal arrangements with no audit trail. That is the gap XoomPark fills.
Who this is for
This page is written for the people who run AV ground operations as a service: fleet-management firms, vehicle-finance and fleet operators, mobility-operations companies, and local ground-ops partners. Industry examples of this category include Moove, Avis Budget Group, Transdev, and Uber's fleet partners. Naming them describes the ecosystem. It does not imply any of them uses XoomPark.
A fleet-ops partner is the right reader if it already operates ground services for an autonomous fleet and is hitting the limits of its own depot footprint. The partner that benefits most has a fleet client demanding SLA evidence, a service area larger than one site can cover, and a finance function that needs clean billing records for every off-site session.
The source, qualify, reserve, audit loop
XoomPark runs as a four-stage loop that maps onto a fleet-ops partner's existing standard work. Records are the deliverable, because records are what a fleet client and a finance team both require.
| Stage | What XoomPark does | What the fleet-ops partner still owns |
|---|---|---|
| Source | Site discovery across private lots, garages, and underused commercial land | Deciding which markets and zones to expand into |
| Qualify | Site qualification, access rules, AV-readiness scoring | Validating that the fleet's vehicles can operate there |
| Reserve | Reservation record, check-in / check-out workflow, exception handling | Scheduling vehicles and dispatching ground crew |
| Audit | SLA tracking, evidence capture, billing and audit records | Service quality and the client relationship |
Example workflow: a partner extends ground operations into a new city
A fleet-ops partner wins a contract to run ground operations for a robotaxi fleet expanding into a new metro. The fleet client requires staging within set distances of demand zones, overnight storage capacity, and recovery holding for vehicles pulled out of service. The partner has one depot site and a 90-day ramp.
Instead of acquiring four more depots, the partner uses XoomPark to source candidate private sites across the demand zones, qualify each against the fleet's capability and access requirements, and reserve a distributed set of nodes for staging, overnight storage, and recovery holding. Each reservation becomes a session record. When a vehicle checks into a node, checks out, or hits an exception, XoomPark captures the evidence. At month-end, the partner hands its fleet client an audit trail showing every off-depot session and its SLA status, and hands its own finance team clean billing records. (The 90-day ramp here is an illustrative scenario; actual timelines depend on the metro, the fleet's requirements, and site availability.)
Original analysis: build-vs-coordinate math for a partner entering a new city
Frame the requirement as a coverage target: a set of ground-service jobs (staging, overnight storage, charging-adjacent queueing, recovery holding) that must be reachable across a metro's demand zones. The build path satisfies coverage by acquiring or leasing sites the partner controls outright. The coordinate path satisfies the same coverage by qualifying and reserving existing private-site capacity it does not own.
The build path front-loads capital and time. A purpose-built AV depot is a large, slow, fixed commitment: Uber's planned Houston robotaxi depot is a 50,000-square-foot facility on a multiyear lease with 40 fast chargers and 15 maintenance bays, drawing over 4 megawatts of power, with groundbreaking slated for early 2027 and service launching mid-2027 (Transport Topics / Yahoo Finance, 2026) — roughly a year of lead time before the first vehicle is served. A site sized for peak also sits underused off-peak, but the lease is paid every day. The coordinate path converts that fixed cost into a variable, per-session cost and compresses the timeline, because qualifying an existing private site is faster than building a new one. The trade-off is control: an owned site is always available; a reserved node depends on the coordination layer holding the reservation, access, and evidence reliably.
Our decomposition surfaces four cost categories a partner should compare directly, rather than comparing only the headline lease price.
| Cost category | Build (own every site) | Coordinate (reserve distributed nodes) |
|---|---|---|
| Capital and lease | High fixed cost, paid regardless of utilization | Variable, per-session; no idle-asset carry |
| Time to coverage | Months: acquisition, build-out, permitting | Faster: qualify and reserve existing sites |
| Utilization risk | Borne by the partner on every owned site | Distributed across many third-party sites |
| Audit and SLA evidence | Built per-site, often manually | Standardized by the coordination layer |
The conclusion from the model is not "always coordinate." It is that the two paths optimize for different things. Build wins where a site must be guaranteed-available and high-throughput every day. Coordinate wins where coverage is wide, demand is uneven, and the partner needs to move fast without sinking capital into real estate it may not fully use. Most partners entering a new city will run a blend: own a small core, coordinate the long tail.
What XoomPark does and does not do for fleet-ops partners
XoomPark is intentionally narrow. It is the records-and-coordination layer, and it stays out of the operator's lane on purpose. That boundary is what makes it an enablement layer rather than a competitor.
| XoomPark does | XoomPark does not |
|---|---|
| Site discovery and qualification for off-depot capacity | Run, dispatch, or route your vehicles |
| Private-site access rules and reservation records | Own chargers or operate a charging network |
| Check-in / check-out workflow and exception handling | Perform vehicle maintenance or cleaning labor |
| SLA tracking, evidence capture, billing and audit records | Certify AV safety or build HD maps |
| Coordination across a distributed ground-service network | Replace your operations team or your client relationship |
Not for you
XoomPark is the wrong fit for some operators, and it is worth being direct about that. If you run a single fixed depot, never operate off-site, and your entire fleet stages and resets in one location you control, you do not need a distributed node network yet. The coordination and audit layer earns its keep when capacity is spread across sites you do not own. One depot, one footprint, no off-site sessions means there is nothing for XoomPark to coordinate.
You also do not need XoomPark if you are looking for a dispatch system, a charging network, a maintenance vendor, or an autonomy stack. XoomPark does none of those. If your gap is vehicle routing, charging hardware, or safety certification, XoomPark is not the layer that closes it.
Frequently asked questions
How can fleet-ops partners use XoomPark?
Fleet-ops partners use XoomPark to source, qualify, reserve, and audit off-depot ground-service capacity that runs under their own standard work. XoomPark handles site discovery, access rules, reservation and session records, SLA tracking, and evidence capture. The partner keeps the fleet relationship, the dispatch, and the service quality.
Does XoomPark replace fleet operators?
No. XoomPark does not run, dispatch, or route vehicles, and it does not replace an operator's team or standard work. It is the coordination and audit layer for distributed private-site capacity. Operators would use it to extend their ground operations off-depot, not to outsource them.
Why are depots not enough for robotaxi fleets?
A depot is one fixed location, but robotaxi fleets operate across a wide service area and need to stage, queue, hold, and reset near demand throughout the day. Acquiring enough depot real estate to cover a metro is slow and capital-heavy. Distributed off-depot nodes fill the geographic gap a single depot cannot.
Is XoomPark just an AV depot operations support tool?
XoomPark supports depot operations by extending them off-depot, but it is narrower than a full ops tool. It does not perform maintenance, run dispatch, or own charging. It provides the reservation, access, SLA, and evidence records that let a fleet-ops partner trust and bill for ground-service sessions it does not own.