White-labeled analytics for your clients, from your own domain
If you build websites for clients — as an agency, a freelancer, or a platform — you eventually hit the same question: do I add analytics, and with what?
Google Analytics works, but it's heavy, it's a cookie banner magnet, and it leaks a big "powered by Google" signal onto every client site. Plausible and Fathom are nicer, but you're paying per-site and you still can't put your own brand on it. Building analytics yourself is a six-month project nobody wants.
That's the gap Vergate Analytics fills: a white-labeled, cookieless analytics product you can launch for a client in one script tag — from your own name, with no third-party brand anywhere in the pipeline.
#What you get per site
Analytics lives on your projects in Vergate. Create an analytics site, give it a name and a domain, and Vergate provisions it instantly. You get:
- An embed snippet — one
<script>tag pointing athttps://api.vergate.dev/analytics/script.jswith a per-site website ID. - A dashboard for that site: pageview counts, visitors, visits and bounce rate, a 7/30/90-day pageview chart, top pages, top referrers, top browsers, and a recent-sessions table.
- Pause/resume and delete controls, so a churned client's tracker stops immediately.
The tracker is brand-stripped end to end. The served script, the collection endpoint it posts to, the response it gets back, and the dashboard all say Vergate — or nothing at all. No Umami logo, no third-party hostname in the embed, nothing to explain to a suspicious client.
#How it works under the hood
The tracker is a single async <script>:
<script async defer src="https://api.vergate.dev/analytics/script.js"
data-website-id="vg-xxxxxxxx"></script>
The script sends an event to the endpoint derived from its own origin:
https://api.vergate.dev/analytics/api/send. The request carries the page
title, URL, referrer, screen size, language, and the user agent. No cookies,
no fingerprinting, no cross-site stitching. Sessions are reconstructed
server-side from timestamp gaps, which is why you get real visitor/visit
numbers without a single cookie banner.
Because the script and the collector share an origin, we ship the
Access-Control-Allow-Origin: * header for the analytics path — the tracker
works on every client site, Vercel, Netlify, a shared PHP host, anywhere.
#The privacy pitch, in one sentence
"This site uses cookieless analytics. No cookies, no personal data, no cross-site tracking."
That sentence — which is now literally true — resolves a conversation your client was dreading. GDPR and ePrivacy are getting stricter, not looser, and cookie-banner law firms actively scan sites for consent violations. Cookieless analytics removes you from that exposure entirely.
#Tier limits
| Plan | Analytics sites |
|---|---|
| Free | 0 |
| Starter | 1 |
| Pro | 3 |
| Max | 10 |
No per-pageview billing, no surprise overage. If a client outgrows their site quota, an upgrade unlocks more — and existing sites are never interrupted.
#A concrete reseller flow
- Client signs a site build with you.
- You create the site in Vergate → paste the one-line embed into their layout template.
- You hand over a dashboard link. If you want, that's the whole deliverable — many clients are delighted to get "their own analytics" with zero setup.
- You bill them in your own invoice. Nothing on their site references a competing brand, so the analytics product is indistinguishable from yours.
That last point is the whole game. Agencies reselling blog hosting, e-commerce or email have known it for decades: the tool underneath barely matters if no client can see it. Vergate Analytics is that same lever, for web analytics.
#What's deliberately not included
- No per-pageview pricing. This is a product, not a metered utility.
- No cookie banners needed. The tracker is cookieless by construction.
- No data reselling. Analytics data is your client's, full stop.
If you've been putting off adding analytics to client projects — or quietly embarrassing your brand with a Google Analytics badge — Vergate Analytics is the one-script-tag fix. Create your first analytics site in under a minute.
Frequently asked questions
Is this a reskin of a third-party analytics tool?
The engine is battle-tested open source (Umami), but the product is entirely Vergate's. Every surface is white-labeled: the tracker script, the collection endpoint, the dashboard, embed code, and response headers. No Umami hostname, brand, or logo ever appears anywhere your client can see.
Is Vergate Analytics cookieless and GDPR-friendly?
Yes. The tracker sets no first-party or third-party cookies, collects no personal data, and does no cross-site tracking. That's by design — cookieless analytics are the low-friction default for sites that don't want cookie banners.
Which plan do I need to resell analytics?
Analytics is included with paid plans: Starter includes 1 analytics site, Pro 3, and Max 10 sites. There's no per-visitor billing — one price per plan, unlimited pageviews, and you can pause or delete sites any time.
Where does the data live?
Inside Vergate's own infrastructure. The tracker posts to a collection endpoint on the same host that serves the script — your embed points at your Vergate account, not at any third-party analytics SaaS.
Can I point the embed at my own custom domain?
Not yet — the script comes from Vergate's API host. What matters for white-labeling is that the client never sees a competing analytics brand, and that the collection works on any site regardless of origin. Custom CNAMEs are on the roadmap.