Today Anvil is focused on the development loop: you see your own driver running on your own controller with full detail. Production monitoring would extend Anvil to cover the other side of the driver lifecycle — once your driver is in customers' homes, running on dealers' controllers, with no direct visibility on your end. The goal is to let you find out about a regression because Anvil surfaces it, not because a dealer calls you.

In production mode the shape of the data changes. Instead of every event with full payload in real time, you get aggregated views: crash-free rates, version distribution, top errors with occurrence and install counts, error timelines. Errors are grouped by fingerprint across thousands of installs, so one underlying bug shows up as one entry rather than thousands. Logs are sampled instead of streamed in full, with the option to capture full logs for a specific install if you're helping a dealer chase something down. A Releases view shows how each version of your driver is performing in the field, including rollout progress as newer versions replace older ones.

Because production data comes from controllers in customer homes, the model is privacy-first by design. Install IDs are hashed and not traceable to specific customers, controller IDs and customer information aren't collected at all, and dealers can disable telemetry per install if their customer requires it. A Development/Production toggle at the top of the project makes the mode you're in obvious, and the two modes have different navigation so the aggregate-focused production UI doesn't clutter your day-to-day debugging work.