━━ COMPARE · TESLANAV
TeslaNav proved the demand. Its shutdown taught us the architecture.
Ryan's TeslaNav put community alerts on the Tesla screen for thousands of Tesla drivers — until Waze blocked the public API and the project went dark. codriver runs on the same screen, but the data layer is platform-owned: drivers contribute, other feeds plug in, and no single upstream can pull the plug on the whole thing.
Side by side
What TeslaNav delivered while it ran, and what codriver does differently so it keeps running.
| ━━ COMPARED | TeslaNavSHUTDOWN · WAZE API BLOCKED | codriverOWNED DATA LAYER · LIVE |
|---|---|---|
| Project status | Shut down — Waze blocked API access | Active — Phase 3 live, contribution APIs next |
| In-Tesla MCU browser | Yes — same surface | Yes — same surface |
| Architecture | Read-only proxy of a single upstream | Platform-owned schema; upstream-agnostic |
| What happens when an upstream cuts access | Service stops (this is what happened) | Other feeds + community contributions keep it running |
| Driver contribution | None — view-only | In-app + report, drive-by confirmation, custom feeds |
| Camera positions | Via the upstream | OpenStreetMap-sourced, community-confirmed |
| Charger reliability | Not included | OpenChargeMap + driver reports |
| Account + favorites | None | Cross-subdomain account, favorites persist |
| Pricing | Was free, now offline | Free tier → $5 / €5 per month → $30 / €30 per year (50% off) |
━━ THE LESSON, MADE CONCRETE
What TeslaNav couldn't do — and codriver does on day one.
Three contribution paths feed one consensus pipeline. The point isn't novelty — it's that the network doesn't have a single point of failure.
Drivers report
Tap "+" on the Tesla screen. Position, heading, speed snap into the report automatically. Your data, your network.
Drivers confirm
Drive past a proposed pin in your forward cone (~80 m) and a non-blocking toast asks 👍 / 👎. Three confirms promote it.
Feeds plug in
Subscribe to public curated feeds (provincial traffic, power outages). Register your own private feed via API. If any one source goes dark, the rest keep working.
━━ QUESTIONS TESLANAV USERS ACTUALLY ASK
FAQ
Is codriver built on top of TeslaNav?
No. Different codebase, different architecture. TeslaNav was a server-side proxy that fetched Waze's API and projected the data into the Tesla browser. codriver is a contribution network — drivers report incidents in-car, drive-by confirmations promote or retire pins, and the schema, kind catalog and consensus engine are owned by the platform. Whatever third-party feed happens to populate it on a given day is replaceable; the architecture doesn't depend on any one of them.
Why did TeslaNav stop working?
TeslaNav's own page explains it: Waze blocked API access. That's the single-upstream architecture problem in one sentence — a project that depends on one source eventually breaks when that source changes the rules. The shutdown wasn't a failure of the product (the design was elegant and the user base was real), it was an inherent fragility in the pattern. codriver was built specifically to avoid it: the data layer is community-driven, any feed plugs in through a generic ingestion surface, and the platform keeps running if any individual feed stops.
I used TeslaNav and want something similar. How is codriver different to use?
Same place — opens in the Tesla 17-inch screen, no install, no jailbreak. Different muscle memory in two ways: (1) you can now tap a 'plus' button to report incidents yourself, not just consume them, and (2) when you drive past a pin someone else just reported, a non-blocking toast asks you to confirm or dispute it. Both are optional; you can use codriver purely as a consumer like you used TeslaNav. But the contribution is what keeps the data fresh now that there's no single Waze pipe to lean on.
Is codriver going to get shut down the same way?
The architecture is designed to make that specific failure mode impossible. The platform owns its schema, kind catalog and consensus pipeline. Any individual feed (curated public feed, third-party API, community contributions) can be cut off without taking the product down. The bootstrap feed currently seeding incident pins is one such feed — it could go away tomorrow and codriver keeps running on community + curated sources. That's the whole point.
How do I migrate my TeslaNav setup?
TeslaNav didn't have accounts or saved data — there's nothing to migrate. Open codriver.io on your phone, sign in (Google or magic link), and scan the QR code on your Tesla browser to pair the two. Takes about a minute. Your favorites going forward are tied to your codriver account.
Get the in-Tesla alerts back — without the single point of failure.
Free tier, no card, upgrade anytime.