Know who's moving, where they're going, and what comes next.
Official-source import · checked Oct 15, 2026. Partial U.S. multi-category coverage, not a live feed. Operator-reported status is attributed. Old testing evidence stays stale; unknown launch dates and permits stay unknown.
◎—Across tracked markets
↗—Recent operator-reported paid service
⌁—Safety-driver & driverless testing
ϟ—Announcement & mapping signals
The deployment landscape
Explore sourced markets · select a pin for intelligence
U.S. state boundaries · city centers, not service areas · drag to pan
Market intelligence
Click a company to inspect evidence
Company / market
Stage
Commercial activity
Launch proximity
Confidence
Source checked
Follow
No matching deployments. Try a broader search or reset your filters.
Weak signals, worth watching
Filtered by the controls above
Your watchlist
Follow companies, states, or cities. Saved only in this browser; no background alerts.
Matching activity in this dataset
Includes stage transitions and early signals for followed entities. Global dashboard filters do not apply.
Activity change log
Sourced tracker observations, newest first. Import observations are not launch dates.
Evidence and limitations
Selected U.S. passenger, freight, delivery, transit and technology markets plus a separately labeled DockDuty infrastructure plan. DockDuty is not counted as an operating ride service; reservations are not deployed vehicles or revenue. Infrastructure records are excluded from launch predictions. Researched and imported October 15, 2026; not exhaustive. Freight, delivery, transit and technology records are separately categorized. Permit-only entries do not establish activity. State-level records remain in lists but have no invented city pin. Current activity and revenue may be unknown; fares do not establish audited revenue. No real-time feed or automatic monitoring.
Dates
First observed means first tracker import, not first company activity. Source last checked is the review date. Evidence freshness uses the source update/publication date, or review date for an undated current availability page. Zoox's March 2026 revision has no exact day; March 1 is a conservative anchor. Old reports do not become fresh when re-read. Unknown announcement dates remain unknown. History records observations, not inferred launch dates.
Service and confidence
Paid service denotes reported commercial access (including non-passenger freight/delivery); it does not independently establish realized provider revenue, driverless maturity, or profitability. Current revenue uses explicit evidence where supplied and is unknown when evidence is stale. Free rider fares do not imply absence of operator contract revenue. Public pilot includes limited free public driverless service. Stage does not independently establish vehicle-level supervision. Announced is the minimum supported stage from an upcoming-market listing, not proof testing is absent. Historical testing may have progressed. Permits are not inferred from service availability.
Editorial confidence is not a probability: clear current operator pages 80–85; intent listings 70; historical, phase-ambiguous testing descriptions 65. High ≥80, Medium 60–79, Low below 60. Independent corroboration is not implied.
Freshness and launch rules
Recent badges require evidence no older than 45 days against the computer clock. Public pilot → Near; Driverless testing → Approaching; Safety-driver testing → Developing; Mapping/Announced → Early. Over 45 days downgrades a tier; over 90 days or confidence below 50 → Uncertain. Suspended/Exited are excluded. These tiers are not dates or probabilities.
Coverage gaps
Coverage is partial, not an exhaustive U.S. inventory. Research exclusions and unresolved providers distinguish supplier activity and unnamed deployment plans from confirmed company–location operations. Integration notes document mappings and low-confidence entries.
Local updates
Export JSON preserves the full record schema and evidence. Import JSON validates and replaces the browser dataset, but does not verify submitted claims. Overrides and watchlists use localStorage, not the HTML on disk. Bundled data restores the initial researched import. A future DataProvider adapter can consume a local API. No background updates, account, telemetry, or cross-device sync.