Robotaxi Depot Network & Autonomous Fleet Infrastructure

Definition

What is the DockDuty Network?

The DockDuty Network is the set of physical depots DockDuty is developing for privately owned and fleet-owned autonomous vehicles, and the one owner platform that connects them. Each depot is designed to park, charge, clean, inspect and stage vehicles and to respond to incidents, under the same procedures in every market. Orlando is the first planned depot, Node One. Markets after it depend on owner demand, vehicle availability, sites, power and local approvals.

From one depot to a network

An autonomous vehicle is not buying parking. It is joining an operation.

Five steps, from the first stall to the long-term vision. Each one says what exists today and what does not.

01 · One depot

Start local.

A depot is the physical operating layer that keeps an autonomous vehicle available: somewhere to arrive, charge, get cleaned and inspected, and wait for the next dispatch. A driverless car still needs all of that done by someone.

Node One, in Orlando, is where DockDuty’s loop gets built and tested. In development
02 · Several depots

Standardize the operation.

The second depot should not be a new invention. The plan is to write the operating procedure once (intake, charging windows, cleaning checklists, inspection points, incident escalation) and record every step in the same software, so each depot runs the same loop and reports the same way.

Miami and Tampa Bay are next on the published roadmap, with no site, lease or date. Designed for more than one site; not proven at any site until one is operating. Planned
03 · One network

Connect the fleet.

An owner with vehicles in several markets should see them in one place: one dashboard, one statement format, one set of standards and one escalation path, whichever depot the car sleeps in.

The owner dashboard is live today, with a public demo. Live Running it across several depots would begin when a second depot opens. Planned
04 · National infrastructure

Every new autonomous market needs an operating layer.

Wherever driverless service opens, the same physical needs follow: parking, power, charging, cleaning, inspection, maintenance, staging, incident response and people on the ground. None of it can be done from a head office. It has to exist locally, in every market.

That repeatable local need is the infrastructure thesis. Owners can already reserve and name 21 metros; the hollow rings are that demand, not depots. Demand, not depots
05 · Long-term vision

Autonomous mobility will not stop at state lines. Neither should its operating infrastructure.

If privately owned autonomous fleets reach other countries, the model is designed to travel with them: a written operating standard, one software platform and a repeatable site specification.

That is a vision, not a plan. DockDuty has no market outside the United States planned today. Vision

The network map

Where the network stands, market by market.

Every market below is in exactly one state. Demand is drawn as demand, never as a depot.

OperatingNo market yet. Reached only when a depot opens.
In developmentSite selection and planning underway. No lease signed, nothing under construction. Orlando only.
Next on roadmapNamed on the published roadmap after Orlando: Miami first, Tampa close behind. No site, lease or date.
Demand openOwners can reserve and name it. Not a depot project.
Future networkConceptual. Not drawn as locations.

Gold halos: stalls reserved naming that market. Gold lines: roadmap order from Orlando, not built connections.

Every market, in one table

Reservation snapshot, September 22, 2026

Market	Status	Stalls reserved	Where things stand	Links
Orlando, FL	In development	77	Node One. Driverless Teslas have carried paying passengers in Orlando since July 21, 2026.	Market page Reserve
Miami, FL	Next on roadmap	2	Named next on the roadmap. Waymo has run driverless here since January 22, 2026 and Tesla unsupervised since July 3, 2026.	Market page Reserve
Tampa Bay, FL	Next on roadmap	1	Named on the roadmap after Miami, possibly in parallel.	Market page Reserve
Jacksonville, FL	Demand open	0	Florida’s autonomous-vehicle law already applies statewide.	Market page Reserve
Fort Lauderdale, FL	Demand open	0	Driverless service already runs in Miami, about 30 miles south.	Market page Reserve
Fort Myers, FL	Demand open	1	Southwest Florida, between the Tampa Bay and Miami markets.	Market page Reserve
Atlanta, GA	Demand open	0	Waymo has run driverless here since 2025.	Market page Reserve
Nashville, TN	Demand open	0	Waymo open to every rider since June 25, 2026.	Market page Reserve
Austin, TX	Demand open	0	Tesla robotaxis have run here since June 2025.	Market page Reserve
Dallas, TX	Demand open	0	Tesla and Waymo both run driverless today.	Market page Reserve
Houston, TX	Demand open	0	Tesla and Waymo both run driverless today.	Market page Reserve
San Antonio, TX	Demand open	0	Waymo runs driverless here by rolling invitation.	Market page Reserve
Phoenix, AZ	Demand open	10	Waymo’s longest-running market; Tesla preparation underway.	Market page Reserve
Las Vegas, NV	Demand open	0	Zoox has charged fares here since August 10, 2026.	Market page Reserve
Los Angeles, CA	Demand open	1	Waymo runs driverless today.	Market page Reserve
San Diego, CA	Demand open	0	Waymo open to riders by invitation since September 1, 2026.	Market page Reserve
Bay Area, CA	Demand open	0	Tesla rides run with safety drivers today.	Market page Reserve
Denver, CO	Demand open	0	Waymo open to riders by invitation since September 1, 2026.	Market page Reserve
Detroit, MI	Demand open	0	Michigan has allowed driverless operation since 2016.	Market page Reserve
Washington, DC	Demand open	3	Waymo is testing; the Council bill as drafted allows no network before 2028.	Market page Reserve
New York, NY	Demand open	0	No state driverless law yet. A reservation holds a place in line.	Market page Reserve

Stalls reserved: refundable reservations (founding and Priority Owner), grouped by the market each buyer named. A reservation is a deposit and a place in line, not a vehicle on site. Counts load live from the public order book API. The notes on driverless service summarize the market pages and the US robotaxi map, where every date carries its source.

Owner demand

The network is being pulled by owners.

Every reservation names a market. Owners are already naming markets DockDuty has not committed to, which is the signal a network is built on.

95stalls reserved

7markets named by buyers

Demand is not a depot.

Reservation snapshot, September 22, 2026
Only Orlando has depot work underway. A reservation is a refundable deposit and a place in line, whatever market it names. Owners have also registered interest in about 14 metros through the site’s forms.

Orlando, FL77
Phoenix, AZ10
Washington, DC3
Miami, FL2
Fort Myers, FL1
Los Angeles, CA1
Tampa Bay, FL1

The first node

Node One: Orlando

Where the network starts, not where it ends. Orlando is the first planned physical depot and the place the operating standard gets written and tested. The software is already live; the physical depot is the next step.

Owner platformLive
Site selectionUnderway
LeaseNot signed
Permits and powerNot yet
Build-outNot yet
OpeningTargeted Q4 2026

50 / 50Founding stalls reserved network-wide before any depot opened. The founding book closed September 5, 2026.Order book

13Stalls in the largest single order, from DockDuty’s reservation records.

45Priority Owner stalls reserved network-wide since September 6, 2026. Snapshot, Sep 22Order book

LiveOwner platform and Stripe payments and refunds; Tesla Fleet API telemetry tested on Tesla vehicles. The public demo runs a simulated fleet.Demo, no login

No depot is operating. Site selection is underway and no depot lease has been signed. Opening is targeted for Q4 2026, a target rather than a commitment. Nothing is parked, charged or dispatched by DockDuty until the depot opens. Reservations are organized in 50-vehicle depot books: the founding book is closed, new Orlando reservations go into the Orlando Depot #2 book for a second planned Orlando depot, and depots are planned to open in reservation order. Everything about the Orlando depot · the live order book

Why the network matters

One depot solves a local problem. A network creates infrastructure.

What a single depot offers against what the DockDuty Network is designed to offer. Each network line is tagged with its status today.

Capability

Individual depot

DockDuty Network

Parking, charging, cleaning

One site, its own way

The same site specification in every market Planned

Operating procedures

Local habits

One written standard, applied at every depot Planned

Software

Whatever the site uses

One owner platform Live

Owner visibility

One site at a time

One dashboard across every depot a fleet uses, from the second depot on Planned

Reporting

A format per vendor

One trip and charging statement format for every vehicle Live

Operating data

Stays local

Benchmarked across sites Planned

Expansion

Start over each time

A repeatable site playbook Planned

Support

Local staff only

Local teams plus network-level support Planned

For owners

Imagine owning 12 autonomous vehicles in three cities.

Without a network

3vendors
3reporting systems
3operating standards
3escalation processes

With the DockDuty Network Planned

1operating relationship
1dashboard
1set of standards
1network

This is the intended network architecture, not a service available today. DockDuty is developing one depot, in Orlando. Reservations can name any of 21 metros, and running cars in three cities needs a depot open in each of them.

Network effects

The value compounds with every node.

What a larger network could give owners and the company. None of it exists yet. It needs more than one depot operating.

01Sharper proceduresEvery site’s lessons improve the one standard all sites follow.

02BenchmarksEach depot measured against the others on turnaround, uptime and cost.

03PurchasingChargers, equipment and supplies bought for many sites instead of one.

04TrainingOne curriculum for every depot team.

05Faster sitesA playbook for finding, powering, permitting and building the next depot.

06CoverageMore cities where an owner can place a vehicle.

07Operating historyData across markets instead of one.

08Software leverageEvery improvement ships to every depot and every owner at once.

How it scales · Architecture

DockDuty sits between owning the asset and running it.

The owner holds title and keeps the earnings. The ride network sends the rides. Everything in between (the physical operation and the software that reports on it) is the layer DockDuty builds.

1Vehicle ownersOwnerIndividuals, LLCs and fleets. Hold title, keep the earnings, can live anywhere.
2DockDuty owner platformLiveReservations, the dashboard, telemetry, statements and documents.
3DockDuty NetworkPlannedThe operating standard, reporting and support shared by every depot. Starts at Node One.
4DockDuty depotsIn developmentPark, charge, clean, inspect, stage, respond. Node One is in site selection; none is operating.
5VehiclesOwner’s assetCharged, clean and inspected between rides, once a depot is operating.
6Ride networksThird partySend the rides. None accepts privately owned autonomous vehicles today; Tesla has described an owner program whose terms are unpublished.

DockDuty is independent. It does not sell or allocate vehicles, and a ride network’s own terms govern whether an owner’s vehicle may join it.

For fleets

Built to scale from one car to a fleet across markets.

Depots are planned in blocks of 50 vehicles that open one after another as each fills, so there is no cap on fleet size. The same standard is meant to apply whether a buyer brings one car or a hundred. Running vehicles in several markets needs a depot open in each; today only Orlando has depot work underway.

Fleet owners

Several vehicles, one operating partner, one monthly statement.

Investment groups

Vehicles held as assets, with reporting built for owners who never visit the depot.

Rental and mobility operators

Depot capacity and daily operations without building your own site.

Corporate fleets

Autonomous vehicles run to a written standard, with a clear escalation path.

Owners in more than one city

Vehicles where the rides are, managed from one account.

Operators with a use case

Hotel, campus, event and airport programs.

Talk to DockDuty about your fleet

How the network is planned to grow

Software, then Node One, then the network.

Milestones, not dates. Only Orlando carries a target, and it is a target.

Phase 1
Platform
Live
Owner dashboard, reservations, telemetry, payments and refunds.
Phase 2
Orlando depot
In development
Node One. Targeted for Q4 2026. No lease signed yet.
Phase 3
Florida network
Planned
Miami named next, Tampa close behind, once Orlando is mostly reserved and operating. No site or date.
Phase 4
Multi-state network
Long-term
Follows where driverless service and owner demand open next.
Phase 5
International
Vision
Only if privately owned autonomous fleets go abroad. Nothing is planned.

For investors: capital is for the network, not Node One. The founders are self-funding Orlando. Outside capital is for location two onward, after pilot proof, with size and terms set from actuals. Nothing on this page is an offer to sell securities.

Request the investor overview

How the network could scale

A network does not mean owning every parcel.

Potential shapes for a DockDuty site. No model is final and no partner is signed; the point is that the operating standard, not the real estate, is what makes a depot a DockDuty depot.

DockDuty-operated depots

DockDuty runs the site and the team directly. The Orlando plan.

Partner facilities

Existing properties run to the DockDuty standard and on DockDuty software.

Real estate partnerships

Landlords and developers provide the site; DockDuty provides the operation.

Charging and power partners

Power is the hard constraint for a depot. Partners who can deliver it matter most.

Have a site that could support a DockDuty depot?

For industrial landlords, commercial real estate owners, parking facilities, EV charging operators, developers and landowners. Four answers to start; space for vehicles and power that can be scaled matter most. A founder reviews every submission.

Received. A founder will review the site.

Nothing is committed on either side by sending it. If you have two more minutes, these details speed up the review. All optional.

Signal demand

Bring DockDuty to your market.

Tell us where you plan to run autonomous vehicles, in the US or anywhere else. Every answer goes into the demand data DockDuty uses when it chooses markets after Orlando.

Under a minute: city, vehicles, owner or fleet, email.
Any city, including ones not on the map.
Want a place in line now? Reserve a stall: $450, refundable until your vehicle is onboarded.

Your market is counted.

It is now part of the demand data behind DockDuty’s next markets. Adding your market does not reserve a stall or commit DockDuty to a location. A market outside the United States is recorded for the long-term vision only; none is planned.

One optional question: when do you expect to run vehicles there?

Reserve a stall if you want a place in line.

Questions

The network, answered directly.

Does DockDuty operate any depots today?

No. As of September 22, 2026, no DockDuty depot is operating, and no customer vehicle is on a DockDuty site or earning through DockDuty. The owner platform, reservations and payments are live. Orlando, Node One, is in site selection with no lease signed, and its opening is targeted for Q4 2026.

The current state of the Orlando depot is on the Orlando page, and every reservation is counted in the order book.

Why do robotaxis need a depot network?

A driverless vehicle still needs physical infrastructure for charging, cleaning, inspection, staging and incident response, close to where its rides are. One depot serves one metro. An owner or fleet with vehicles in several metros needs the same service in each, and a depot network is how that service stays consistent from city to city.

Where driverless service runs today, metro by metro, is on the US robotaxi map.

What does an autonomous vehicle depot do?

An autonomous vehicle depot keeps vehicles ready to work: parking between rides, DC charging, interior cleaning, inspection, staging for dispatch, incident response and coordination of maintenance. It is the physical operating layer between owning an autonomous vehicle and having it earn on a ride network.

The Cybercab depot guide covers what a stall includes, and the robotaxi depot database lists publicly documented US facilities, one source per row.

Can one company operate autonomous vehicles across multiple cities?

Yes. Waymo and Tesla already run robotaxi service in several metros. What does not exist yet is an independent operator running vehicles owned by individuals and independent fleets, rather than by the ride network, across cities under one standard. That is what the DockDuty Network is designed to become. Today DockDuty is developing its first depot, in Orlando.

How is a depot network different from fleet management software?

Fleet management software tracks vehicles; a depot network also does the physical work. Software cannot plug a vehicle in, clean it or recover it after an incident. DockDuty builds both: the owner platform is live today, and the first depot, in Orlando, is in site selection.

What DockDuty handles day to day is on the fleet management page; fleets and operators can talk to a founder.

Where will DockDuty open next?

No location after Orlando is confirmed as of September 22, 2026. Miami is named next on DockDuty’s published roadmap and Tampa Bay after it; neither has a site, a lease or a date. The other 18 metros on this page are open for owner reservations. A reservation records demand; it is not a commitment to open there.

Each market’s status is in the market table; see also Miami and Tampa Bay.

You buy the cars. We run them, to one standard, in every market we reach.

Node One is Orlando. The network is the company.

Reserve a stall Open the owner dashboard demo