About Wingtics
An open-source React kit for reading your website analytics, whichever tool holds them.
The problem it solves
Analytics dashboards are usually written against one vendor’s API. Moving from Plausible to GA4, or from GA4 to Vercel Web Analytics, means rewriting the charts, the number formatting, the empty states and the loading behaviour — none of which had anything to do with the vendor.
Wingtics splits the two apart. A connector speaks to one analytics provider and answers a single provider-agnostic query model. The components render whatever comes back. Switching provider is a constructor change; the dashboard does not move.
What it is, concretely
@wingtics/core— the query model, the connector contract, metric and dimension registries.@wingtics/react— 37 chart and dashboard components, plus the provider and hooks that feed them.@wingtics/next— route handlers that proxy a connector so vendor credentials never reach the browser.- Six connectors: Vercel Web Analytics, Plausible, GA4, Umami, PostHog, and a deterministic mock for tests and demos.
Components also install as source through a shadcn registry, so you can own the file instead of the dependency.
What it is not
It is not an analytics provider and not a hosted service. It collects nothing, stores nothing, and has no account. You bring the analytics tool you already pay for; Wingtics is the interface on top of it. There is no paid tier — the whole thing is MIT.
Capabilities, not crashes
Providers disagree about what they can answer. Plausible has no per-page bounce rate; Vercel Web Analytics has no event properties. Every connector declares its capabilities, and components that cannot be answered say so instead of rendering a zero. A dashboard built on Wingtics degrades honestly when you change vendor.
Who builds it
Wingtics is built by Eduardo Calvo and is developed in the open at github.com/educlopez/wingtics. It was called Analytics Kit until September 2026. Issues and pull requests are welcome — see contact.