Privacy-first analytics you actually own
Statiz tracks your visitors, campaigns, revenue, and AI referrals on a dashboard you deploy yourself — one Next.js app, your own Postgres database, and the full source code in your hands. No cookies, no third-party scripts, no monthly fee.
Unique visitors
3,721
Total pageviews
8,154
Bounce rate
42.31%
Avg. visit duration
2m 34s
Live users
12
Visitors
Features
Everything a maker needs. Nothing phoning home.
Every card below is a real screen in the product — the same dashboard you saw above, running on your own infrastructure.
Privacy-first by default
No cookies, no fingerprinting, no data shared with ad networks. Visitor ids live in localStorage — or switch on cookieless mode and identify visitors server-side instead.
Live map & realtime stats
Watch visitors land on a world map with a live session sidebar, online counts, and a realtime range that updates as people browse.
Revenue attribution
Connect Stripe, Polar, Creem, Dodo Payments, Paddle, or Lemon Squeezy. Refunds net out, payers get real identities, and MRR/ARR chart themselves.
AI analytics
See which AI assistants — ChatGPT, Claude, Perplexity, and friends — send you visitors, and track how crawlers index your pages.
Goals, funnels & journeys
Custom events and page goals, sequence-aware conversion funnels, and per-visitor journeys — all filterable from every card.
Campaigns & keywords
UTM and ?ref= campaigns work out of the box, and Google Search Console integration surfaces the keywords that bring you clicks.
Public dashboards & widgets
Share a read-only dashboard with visitor PII masked, or embed realtime widgets anywhere with a one-line iframe.
Full source included
A complete Next.js + Prisma + TypeScript codebase. Deploy to Vercel and Postgres in about ten minutes — then change anything you like.
FAQ
Questions, answered honestly
Everything else — tracking setup, revenue, goals, deployment — is documented in the docs.
Is Statiz open source?
No. Statiz is distributed as paid source code under the Statiz Commercial Source Code License. You get the complete codebase and can modify it freely for your own use — but it is not open source, and it may not be redistributed or resold.
Where does my analytics data live?
In your own PostgreSQL database. Statiz is self-hosted: you deploy it to your own Vercel account (or any Node host) with a Postgres database such as Neon or Supabase. There is no Statiz-operated server receiving your visitors’ data — the only network calls are the ones you configure (your payment provider’s webhooks, the Google Search Console you connect).
Does Statiz use cookies?
No. The default tracker keeps a random visitor id in your site’s localStorage — enough for new-vs-returning counts without a cookie. The cookieless mode goes further: no identifier is stored in the browser at all, and visitors are recognized server-side with daily-rotating hashes.
How long does setup take?
About ten minutes. Deploy to Vercel, point it at a Postgres database, run npx prisma migrate deploy, create your account, and paste one script tag into your site. The onboarding flow walks you through every step, and the docs cover each screen.
Which payment providers can I connect?
Stripe, Polar, Creem, Dodo Payments, Paddle, and Lemon Squeezy. You create a webhook in your own provider dashboard (Statiz never touches your provider account), revenue arrives in real time, and “Sync now” backfills up to 365 days. Or skip providers entirely and track revenue client-side with a single statiz.revenue() call.
Can my team use Statiz?
Yes. Each deployment has one admin account, and the admin creates team users with editor or viewer roles. Team members share every website on the deployment — editors can manage settings, viewers get read-only dashboards.
Can I import history from another tool?
Yes — built-in importers for Umami and datafa.st bring over sessions, pageviews, and goals. Imports are idempotent (re-running never doubles anything) and overlap-aware, so running Statiz alongside your old tool won’t double-count the switch-over period.
How do updates work?
Releases ship as a fresh source zip you re-download from the Polar customer portal, for 12 months after purchase. Your deployment’s Settings page polls for new versions and shows an update banner whenever one is published — the changelog’s first line always tells you whether a database migration is needed.
What’s the license — and the refund policy?
One purchase licenses one production installation (plus your dev and staging copies) serving websites you own or operate — including running it for one client organization on their behalf. Each additional business or client deployment needs its own license. Modify the code freely for your own use; don’t redistribute or resell it. Because the source is delivered instantly, all sales are final after download — genuinely defective deliveries get fixed or refunded at our discretion. The full policy is on the refund policy page.