Two products, two meters, two toggles
These are frequently discussed as one feature and billed as two. Vercel's pricing page lists Web Analytics at $3 per 100,000 events with 50,000 a month included on Hobby, and Speed Insights at $10 per project per month plus $0.65 per 10,000 events, with 10,000 events included on Hobby. They are enabled independently, per project, which means an accurate audit requires opening each project rather than checking one setting once.
The per-project base charge is the part that surprises people
Almost every other meter on the platform scales with usage, so a quiet project costs almost nothing. Speed Insights does not work that way: the $10 is per project per month before any events are counted. A team with one application sees a small line. A team running many projects, separate marketing sites, staging environments, small internal tools, a per-client deployment model, multiplies that base charge by the project count, and the total bears no relation to how much anyone actually reads the data.
Audit by listing projects, not by checking settings
The reliable method is to enumerate every project in the team and check both toggles on each. Doing it the other way round, remembering which projects you enabled it on, fails predictably, because these switches are easy to turn on during setup and invisible afterwards. Enabled telemetry produces no symptom other than a line on an invoice, which is precisely why it survives for months. When we did exactly this on our own fleet in August 2026, the count came back sixteen out of sixteen projects with both toggles on, a clean sweep nobody had chosen on purpose, on a team that writes cost guides for a living.
Ask who read it last month
The decision rule is simple and uncomfortable: name the person who opened the dashboard in the last month and the decision they made because of it. If both answers exist, keep it and consider the cost well spent, because performance data that changes behaviour is cheap at this price. If either answer is missing, turn it off. You can always re-enable it for a specific investigation, and re-enabling is a click.
The self-hosted alternative for always-on measurement
If you want analytics running permanently rather than during investigations, a self-hosted open-source analytics tool removes the per-event meter entirely in exchange for running it somewhere. Several mature options exist, they are privacy-friendly by design, and for a team already operating a server the marginal cost is close to zero. This is the standard answer for teams whose analytics need is continuous rather than occasional.
Reader comments
No account needed. Share what worked, what did not, and what you would add.
Add a quick note with the form below. Short, specific tips help the next reader most.