Alphabet's Sidewalk Labs Plans Digital City for Google Car, Internet
When Google launched a new company to “fix cities,” speculation swirled as to what, precisely, that company would do. One idea: What if it built its own city, a laboratory vision of a thoroughly connected, techno-utopia?
Context & Ripple Effects
Sidewalk Labs was created in 2015 as Alphabet's vehicle for 'fixing cities,' led by former NYC deputy mayor Daniel Doctoroff and funded by Google itself. This report is the first concrete answer to what that mandate meant: not just apps layered on existing cities, but a purpose-built digital city designed around Google's self-driving car and its connectivity stack.
The idea did not stay hypothetical — it matured into the Toronto waterfront master plan with Waterfront Toronto, complete with 'ubiquitous sensing,' before privacy opposition forced a scale-back. That arc makes this early proposal the origin point for both the ambition and the backlash.
First-order effects
- A Sidewalk-built city would make Alphabet the de facto operator of core urban infrastructure — streets sized for Google Car and connectivity baked into the fabric — rather than a vendor selling into cities run by others.
- Doctoroff's incubation model gets a physical testbed: instead of persuading existing municipalities to adopt urban tech, Sidewalk controls the deployment end-to-end.
Second-order effects
- The street-level data layer becomes the product: Sidewalk's later Coord spinout building APIs for tolls, parking, and curb space shows how a company that designs the streets also prices access to them, pressuring city governments to either open their own curb data or cede that layer to platform vendors.
- Other cities evaluating smart-city partnerships gain a reference case — and Waterfront Toronto's experience with 'ubiquitous sensing' becomes the cautionary template competitors and civic groups alike will cite.
Third-order effects
- If the build-your-own-city pattern holds, urban development splits between legacy municipalities negotiating with tech platforms and greenfield districts where the platform writes the rules — with the privacy-driven retreat from Toronto demonstrating that public consent over physical-world data is the binding constraint on which model wins.
- The longer-term question the Toronto fight surfaced: who governs sensor data collected in public space — the city, the operator, or residents — becomes a regulatory battleground wherever platform-operated districts are proposed.
The trend: Tech platforms are expanding from selling software and vehicles into operating physical urban infrastructure, with data-governance fights emerging as the main brake on that expansion.