The DockDuty Network

One depot is a location. A network is infrastructure.

DockDuty is building a network of standardized physical depots for privately owned and fleet-owned autonomous vehicles, connected by one owner platform that is already live. Orlando is our lead market, with a depot targeted for Q4 2026 and locations in several more metros planned at the same time.

Illustration: the planned DockDuty depot in Orlando with lines to the metros where owners can reserve today, and beyond the United States as a long-term vision. The same information is in the market table on this page. Orlando
Lead market   Depot planned   Demand open
Thin lines: metros open for owner reservations (demand, not built connections). Dashed: long-term vision. No DockDuty depot is operating yet.

0 depots operating today. Orlando is our lead market, and its opening is targeted for Q4 2026.

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 lead market; the Orlando depot is targeted for Q4 2026. Other markets 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. The longer case for why autonomous fleets need this layer at all is on why DockDuty exists.

  1. 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.

    Orlando is where DockDuty’s loop gets built and tested. Lead market

  2. 02 · Several depots

    Standardize the operation.

    Another 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.

    More metros are planned at the same time, with no site, lease or date. Designed for more than one site; not proven at any site until one is operating. Planned

  3. 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

  4. 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 thin rings are that demand, not depots. Demand, not depots

  5. 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.
  • Lead marketNo lease signed, nothing under construction. Orlando only.
  • Depot plannedWe’re planning a depot here. No site, lease or opening date yet. Reservations are open.
  • Demand openOwners can reserve and name it. Not a depot project.
  • Future networkConceptual. Not drawn as locations.
Gold halos: stalls reserved naming that market.

Every market, in one table

Reservation snapshot,
MarketStatusStalls reservedWhere things standLinks
Orlando, FLLead market121Planned depot. Driverless Teslas have carried paying passengers in Orlando since July 21, 2026.
Miami, FLDepot planned3Waymo has carried public riders here since January 22, 2026 and opened to everyone on April 15, 2026; Tesla has run unsupervised since July 3, 2026.
Tampa Bay, FLDepot planned2Tesla has run driverless here since July 21, 2026, and Waymo by invitation since September 1, 2026.
Jacksonville, FLDemand open0Florida’s autonomous-vehicle law already applies statewide.
Fort Lauderdale, FLDemand open2Driverless service already runs in Miami, about 30 miles south.
Fort Myers, FLDemand open1Southwest Florida, between the Tampa Bay and Miami markets.
Atlanta, GADemand open0Waymo has run driverless here since 2025.
Nashville, TNDemand open0Waymo open to every rider since June 25, 2026.
Austin, TXDemand open0Tesla robotaxis have run here since June 2025.
Dallas, TXDemand open0Tesla and Waymo both run driverless today.
Houston, TXDemand open0Tesla and Waymo both run driverless today.
San Antonio, TXDemand open0Waymo runs driverless here by rolling invitation.
Phoenix, AZDemand open10Waymo’s longest-running market; Tesla preparation underway.
Las Vegas, NVDemand open0Zoox has charged fares here since August 10, 2026.
Los Angeles, CADemand open1Waymo runs driverless today.
San Diego, CADemand open0Waymo open to riders by invitation since September 1, 2026.
Bay Area, CADemand open0Tesla rides run with safety drivers today.
Denver, CODemand open0Waymo open to riders by invitation since September 1, 2026.
Detroit, MIDemand open0Michigan has allowed driverless operation since 2016.
Washington, DCDemand open3Waymo is testing; the Council bill as drafted allows no network before 2028.
New York, NYDemand open0No state driverless law yet. A reservation holds a place in line.

Stalls reserved: refundable reservations (founding and Priority), 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.

143stalls reserved
8markets named by buyers

Demand is not a depot.

Reservation snapshot,
Orlando is the lead market, and no site lease is signed there yet. A reservation is a refundable deposit and a place in line, whatever market it names. Full dataset: owner demand by metro (CSV and JSON).

  1. Orlando, FL121
  2. Phoenix, AZ10
  3. Miami, FL3
  4. Washington, DC3
  5. Fort Lauderdale, FL2
  6. Tampa Bay, FL2
  7. Fort Myers, FL1
  8. Los Angeles, CA1
The lead market

Orlando

Where the network starts, not where it ends. Orlando, our lead market, is the place the operating standard gets written and tested. The software is already live; a physical depot comes after a site lease is signed.

  1. Owner platformLive
  2. SiteNot secured yet
  3. LeaseNot signed
  4. Permits and powerNot yet
  5. Build-outNot yet
  6. OpeningTargeted Q4 2026
50Founding stalls, closed Sep 5, 2026, all reserved network-wide before any depot opened.Order book
20Stalls in the largest single order, from DockDuty’s reservation records.
93Priority stalls reserved network-wide since September 6, 2026. Snapshot, Order 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, 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. The founding stalls closed Sep 5, 2026, and Priority stall reservations are open in every metro we list. 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. Orlando is the lead market, and no DockDuty depot is operating yet. 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 each 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.

  1. 1Vehicle ownersOwnerIndividuals, LLCs and fleets. Hold title, keep the earnings, can live anywhere.
  2. 2DockDuty owner platformLiveReservations, the dashboard, telemetry, statements and documents.
  3. 3DockDuty NetworkPlannedThe operating standard, reporting and support shared by every depot. Starts in Orlando.
  4. 4DockDuty depotsLead marketPark, charge, clean, inspect, stage, respond. No site lease is signed for the Orlando depot; none is operating.
  5. 5VehiclesOwner’s assetCharged, clean and inspected between rides, once a depot is operating.
  6. 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.

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 Orlando is the lead market, and no site lease is signed there yet.

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.

How the network is planned to grow

Software, then Orlando, then the network.

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

  1. Phase 1

    Platform

    Live

    Owner dashboard, reservations, telemetry, payments and refunds.

  2. Phase 2

    Orlando depot

    Lead market

    Planned depot. Targeted for Q4 2026. No lease signed yet.

  3. Phase 3

    More metros

    Planned

    More metros planned at the same time. No site, lease or date.

  4. Phase 4

    Multi-state network

    Long-term

    Follows where driverless service and owner demand open.

  5. Phase 5

    International

    Vision

    Only if privately owned autonomous fleets go abroad. Nothing is planned.

For investors: capital is for building the network. Size and terms are set from actuals, not from a spreadsheet. 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.

Under a minute. Used only to evaluate the site and reply to you. Privacy.

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 new markets.

  • 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.
You are

No payment. No commitment. This helps DockDuty measure owner demand. We will email you about DockDuty and your market; unsubscribe any time. Privacy.

Your market is counted.

It is now part of the demand data behind DockDuty’s planning. 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 client vehicle is on a DockDuty site or earning through DockDuty. The owner platform, reservations and payments are live. Orlando is our lead market and where most reservations are; no site lease is signed for our planned depot there, and its opening is targeted for Q4 2026, with locations in several more metros planned at the same time.

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 Orlando is DockDuty’s lead market.

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 Orlando depot is planned, with no site lease signed yet.

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

Where else is DockDuty planning depots?

No location other than Orlando is confirmed as of September 22, 2026. DockDuty is planning locations in several more metros at the same time, including depots in Miami and Tampa Bay; none has a site, a lease or a date. The other 18 metros we list are Demand open: reservations are open, and no depot is planned there yet. A reservation records demand; it is not a commitment to open there.

Each market’s status is in the market table.

Your Cybercab fleet, fully run, to one standard, in every market we reach.

Orlando is the lead market. The network is the company.