━━ COMPARE · WAZE IN YOUR TESLA
Waze on your phone is fine. codriver is what you want in your Tesla.
Tesla doesn't run a native Waze app on the MCU — people mount a phone, glance down, deal with the cable. codriver is built for the Tesla browser itself: same kind of community-powered traffic and alerts, running on the 17-inch screen, owned by drivers instead of an ad network. (Waze is a Google company — that's where its data layer lives.)
Side by side
Both community-driven. The split is where they run, who owns the data layer, and what they're optimized for.
| ━━ COMPARED | Waze on phonePHONE-MOUNT · GOOGLE | codriverTESLA MCU · COMMUNITY-OWNED |
|---|---|---|
| Where it runs | Phone — needs a mount over your Tesla's screen | Inside the Tesla MCU browser — no phone, no mount |
| Community contribution | Yes — Waze invented this category | Yes — in-app +, drive-by confirm, subscribable feeds |
| Account + data ownership | Google account; your driving data flows to Google | Anonymous by default; no ads, no surveillance |
| Speed cameras (fixed + average-speed + red-light) | Yes — fixed + red-light | All three types · OSM-sourced, community-confirmed |
| Charger reliability + intel (EV-native) | Not really — generic POIs at best | OpenChargeMap + driver reports + reliability scores |
| Pace-note voice (calm, distance-first) | — | No emoji, no nagging, distances over encouragement |
| Routing (turn-by-turn) | Yes | Not the goal — runs alongside Tesla's nav |
| Cost | Free with ads | Free tier, then $5 / €5 per month — no ads |
━━ HOW THE COMMUNITY KEEPS IT FRESH
The same idea — community spotting and confirming — owned by the community.
Three contribution paths feed one consensus pipeline. None of them require a phone in your hand. None of them route through an ad network.
In-app "+" on the Tesla screen
One tap — pick a kind, the report carries your position, heading and speed automatically. No typing on the in-car soft-keyboard.
Drive-by confirmation
Approaching a proposed pin in your forward cone (~80 m), a non-blocking toast asks 👍 / 👎. Same pattern Waze drivers already know.
Subscribable public feeds
Provincial 511 traffic, power outages, road-closure feeds — one click in Settings. Register your own private feed if you want a layer only you see.
━━ FAQ
Tesla owners ask
Is codriver affiliated with Waze?
No. codriver is an independent project, community-owned, not endorsed by, partnered with, or owned by Waze or Google. Waze is a Google product; codriver is a separate platform that runs in the Tesla MCU browser.
Can I run Waze on my Tesla's screen?
Not really. Tesla doesn't run a native Waze app on the MCU. People generally use Waze on their phone in a mount over the Tesla screen — which works but takes over the dashboard. codriver is built for the Tesla browser itself: open codriver.io in the in-car browser, pair it once with your phone, and you get community-driven traffic and alerts on the Tesla screen with nothing extra to mount.
Does codriver do turn-by-turn routing?
Not as the primary use case. Tesla's built-in nav handles routing — codriver overlays the live road context (community alerts, cameras, chargers) that Tesla's nav doesn't surface. The two run alongside each other in the same browser.
Why not just use my phone?
You can. The pitch for codriver is specifically about not having a phone in the way: it runs natively in the 17-inch screen, no mount, no Bluetooth flake, no glance-down. If a phone mount is fine for you, that's fine — different ergonomics.
How does the community data layer compare?
Both are community-driven. The difference is ownership: codriver's schema, kind catalog, and consensus math are platform-owned and pluggable — anyone can register a public or private external feed, and the platform isn't dependent on any single upstream. Whoever owns the network owns its future direction.