BoilerplateHub

Umami vs Vercel Analytics

Umami and Vercel Analytics both answer the same question: how do you know what users actually do? Open source privacy-focused analytics you can self-host on your own database, or use as a hosted service. Page-view and Core Web Vitals data collected by the host you are already deploying to, with no setup. The real split is ownership: Umami runs inside your project and leaves the operational work with you, while Vercel Analytics runs the hard parts as a service and takes a dependency in exchange.

Verdict

The real split is ownership: Umami runs inside your project and leaves the operational work with you, while Vercel Analytics runs the hard parts as a service and takes a dependency in exchange.

Pick Umami if

  • Self-hosting means the raw analytics data sits in a database you already run.
  • Stores into Postgres or MySQL, so you can query it with plain SQL.
  • No licence cost at all when you supply the hosting yourself.

Pick Vercel Analytics if

  • Enabling it is a toggle plus one component, with nothing else to configure.
  • Real user Core Web Vitals come from the same platform serving the pages.
  • Data appears next to deployments, so a regression is easy to attribute.
Comparison Umami Vercel Analytics
Pricing shape Free if you self-host on your own infrastructure, with a paid cloud plan by event volume. Included in limited form on Vercel plans, with additional event volume billed as usage.
Frameworks Next.js, SvelteKit, Nuxt, Laravel, Django, Rails Next.js, SvelteKit, Nuxt
In one line Open source privacy-focused analytics you can self-host on your own database, or use as a hosted service. Page-view and Core Web Vitals data collected by the host you are already deploying to, with no setup.

Pricing described qualitatively because published plans change often. Checked 2026-08-23. Confirm current terms on Umami and Vercel Analytics.

Umami

Strengths

  • Self-hosting means the raw analytics data sits in a database you already run.
  • Stores into Postgres or MySQL, so you can query it with plain SQL.
  • No licence cost at all when you supply the hosting yourself.
  • Multi-site and team support without paying per additional property.

Tradeoffs

  • Self-hosting means you own uptime, upgrades and database growth forever.
  • Analytics traffic writes to a database you must size and prune yourself.
  • Feature set trails commercial tools, especially around alerting and reporting.
  • Community support only, so an obscure bug can stall you.

Vercel Analytics

Strengths

  • Enabling it is a toggle plus one component, with nothing else to configure.
  • Real user Core Web Vitals come from the same platform serving the pages.
  • Data appears next to deployments, so a regression is easy to attribute.
  • No third-party domain, so ad blockers interfere less than with external scripts.

Tradeoffs

  • Only useful while you host on Vercel, so it cannot outlive that choice.
  • Reporting is basic next to any dedicated analytics product.
  • Event pricing on top of hosting makes it costly at real traffic volumes.
  • No historical export path if you later move to another provider.

Frequently asked questions

Is Umami or Vercel Analytics better?

Neither is better in the abstract. The real split is ownership: Umami runs inside your project and leaves the operational work with you, while Vercel Analytics runs the hard parts as a service and takes a dependency in exchange. The wrong choice here is usually recoverable, so weight speed of decision over certainty.

What is the main drawback of Umami?

Self-hosting means you own uptime, upgrades and database growth forever. Analytics traffic writes to a database you must size and prune yourself.

What is the main drawback of Vercel Analytics?

Only useful while you host on Vercel, so it cannot outlive that choice. Reporting is basic next to any dedicated analytics product.

Can you switch from one to the other later?

Usually, at a cost that grows with how much of your product leans on the analytics layer. Keep the integration behind a thin module of your own and the migration stays a weekend rather than a quarter.

Related comparisons