Vemetric is an open-source web and product analytics platform, written in TypeScript and licensed under AGPL-3.0, for teams and site owners who want to understand how users behave across a website or a product.

What it is

Vemetric lives in the Data & Analytics / Web & Product Analytics category of this registry. It is a TypeScript codebase with 390 stars, 36 forks, and 8 open issues, and its source is published under the AGPL-3.0 licence in LICENSE.md. The project describes itself as a platform that helps you understand your users' behavior, designed to be simple yet powerful, and it provides insights into how users interact with a website or product. Its topic list points to the data layer it is built around, naming both clickhouse and postgresql alongside analytics, privacy, product-analytics, and web-analytics.

The concrete problem it solves is the split between the tracking snippet a site owner points at an external analytics service and the richer product-level questions that snippet cannot answer, such as which sequence of actions a user took before converting. Because self-hosting is not yet available, what Vemetric replaces today is a prior hosted analytics provider in a site's tracking snippet, including the contract and data-processing relationship that comes with it. Custom event tracking and User Journeys are the features that carry that product-analytics load, while real-time analytics covers the basic traffic view.

Key capabilities

• Real-time analytics, as listed in the README's feature set, so that incoming activity appears in the dashboard as it arrives.
• Behavior tracking via User Journeys, which reconstructs the path a user takes through a product rather than reporting isolated pageviews.
• Custom event tracking for actions beyond pageviews, which feeds the journey and filtering views.
• Filtering mechanisms described as powerful, used to see how users interact with the product and the website.
• Tracking across several subdomains, allowing one property to span a set of related hosts.
• A data layer named by the repository topics as ClickHouse and PostgreSQL, with privacy listed among the topics.
• Project governance files visible in the repository, including CONTRIBUTING.md for contributions, SECURITY.md for the security policy, and a status endpoint at status.vemetric.com.

Who uses it and how

• Site owners who run one website spread across several subdomains and want a single view of that traffic rather than per-host reporting.
• Product teams that need journeys and custom events rather than pageview counts alone, using User Journeys plus custom event tracking to see how users move through the product.
• Privacy-conscious organizations that weigh the privacy topic and an AGPL-3.0 codebase when choosing an analytics provider.
• Contributors, which the project actively invites: the README carries a "PRs Welcome" badge and links CONTRIBUTING.md, and the hacktoberfest topic indicates participation in that program. The repository currently shows 8 open issues as an entry point.
• Teams that are content to consume the hosted dashboard at vemetric.com today, described in the README's Dashboard documentation link.

Getting started

Use the hosted product: the README points to the website at vemetric.com and to documentation at vemetric.com/docs, including a Dashboard guide and an FAQ page. Self-hosting is not available yet, so no package, image, or compose file is published for it.

How it compares

The facts provided for this page name no paid products that Vemetric replaces and no comparable open-source tools, so it stands alone in this registry on that axis. The comparison that the facts do support is internal rather than competitive: the licence terms change with deployment, since the AGPL-3.0 obligations apply to network services as well as distributed software.

When to use it — and when not to

Vemetric is a reasonable pick if a hosted analytics service is acceptable and the value is in User Journeys, custom events, and subdomain-wide tracking. It is the wrong pick for a team that needs to run analytics on its own infrastructure now, because self-hosting is described as still very early, with the feature scope of the planned Community Edition undecided; self-hosters should also expect to operate ClickHouse and PostgreSQL, which its topics name. The AGPL-3.0 terms are strict for network services: anyone running a modified version for users must release the derivative work under AGPL-3.0 and provide the corresponding source. The README is short, and the last push recorded for the repository is 2026-09-17.