━━ COMPARE · TESLAWAZE
TeslaWaze was a window. codriver is a network.
TeslaWaze, the community-built Azurewebsite project, proxied a Waze data feed into the Tesla browser before it went stale. codriver runs in the same place — but drivers contribute, drive-by confirms tighten what they see, and the data layer is owned by the platform, not borrowed from any single upstream.
Side by side
What you got with TeslaWaze versus what you get when you pair codriver to your Tesla browser today.
| ━━ COMPARED | TeslaWazeDEPRECATED · 2017–2023 | codriver2026 · LIVE |
|---|---|---|
| Project status | Shut down — public Waze API blocked; site displays a shutdown notice | Actively shipping — Phase 3 live, contribution APIs next |
| In-Tesla MCU browser | Yes | Yes — Tesla is the only OEM that ships a browser usable while driving |
| Read-only or contribute | Read-only — drivers saw pins but couldn't report back | Both — in-app one-tap report + drive-by confirmation |
| Data layer | Single upstream — broke when the upstream changed | Upstream-agnostic — community + curated feeds, codriver-owned schema |
| Camera positions (speed / red-light) | Not included | OpenStreetMap-sourced, community-confirmed |
| Charger reliability + intel | Not included | OpenChargeMap + driver reports |
| Account + favorites | None | Cross-subdomain account, favorites persist |
| Anonymous by default | — | Yes. No ads. No surveillance. |
| Cost | Free, no support | Free tier → $5 / €5 per month → $30 / €30 per year (50% off) |
━━ HOW THE COMMUNITY KEEPS IT FRESH
Three ways drivers feed the map.
TeslaWaze never had a contribution path — drivers consumed, nobody confirmed. codriver runs the opposite playbook.
In-app "+"
Spotted something? Tap the plus, pick a kind (police, hazard, construction). Position + heading + speed snap to the report automatically.
Drive-by confirm
When you approach a proposed pin in your forward cone, a non-blocking toast asks 👍 or 👎. Three confirms promote it; disputes retire it.
Subscribable feeds
One-click subscribe to vetted public feeds — provincial traffic, power outages — or register your own private feed against a layer you own.
━━ QUESTIONS TESLAWAZE USERS ACTUALLY ASK
FAQ
Is codriver a fork of TeslaWaze?
No. Different codebase, different data layer, different team. TeslaWaze proxied a single upstream into the Tesla browser; codriver is a contribution network where drivers report incidents in-car, drive-by confirmations tighten accuracy, and the data layer is owned by codriver — independent of any single source.
Does codriver still depend on Waze for data?
Short answer: less and less. codriver's schema, kind catalog, and consensus math are all platform-owned. In the current beta, a Waze-derived bootstrap feed seeds incident pins while the community grows. As driver contributions and curated public feeds (Hydro-Québec outages, provincial 511 traffic, etc.) reach critical mass, the bootstrap feed is retired. The platform runs unchanged regardless of which third-party feeds happen to populate it on any given day.
Does it run in the same Tesla MCU browser as TeslaWaze did?
Yes. Built for the 17-inch landscape screen, no jailbreak, no install. Launches from a URL and updates instantly — no firmware wait. Tesla is currently the only OEM with a browser you can use while driving; Android Auto's Vivaldi browser is parked-only. Works in any Chromium browser on phone or laptop too.
Why did TeslaWaze stop working reliably?
It was a volunteer-run proxy of a single upstream's data, and the upstream changed shape under it. Community projects without a maintained data layer eventually drift. codriver was built specifically so that the platform owns its own taxonomy and ingestion surface — any individual feed can break without taking the product down.
How do I migrate my TeslaWaze setup?
There's nothing to migrate — TeslaWaze didn't have accounts or saved data. Open codriver.io on your phone, sign in, and pair your Tesla browser with the QR code. Takes about a minute.