Analytics scattered everywhere
A different dashboard per client, none of them comparable, all of them asking your visitors to accept cookies.
One platform, every site you run
Stop wiring the same four things into every project. Tusua gives every site you maintain cookieless analytics, form intake with antispam built in, alerts that reach you, and backups that tell you when they stop running.
Invite-only while we build. No card, no spam.
Every site you look after ends up with its own analytics account, its own contact form glued to something, its own backup script nobody has checked in a year.
A different dashboard per client, none of them comparable, all of them asking your visitors to accept cookies.
A PHP mailer here, a third-party embed there, and spam arriving in an inbox nobody reads.
The cron job stopped six weeks ago. You will find out the day you need the backup.
A site goes down on a Friday and the first person to notice is the client on Monday.
Add a site, paste one line, and all of it starts working.
Pageviews, sources, campaigns and outbound clicks. No cookies, no fingerprinting, no banner to click away.
Point any form at Tusua and get a clean inbox. Honeypot, time-trap and scoring included; the spam is filed, not thrown away.
One place to send email and Telegram from every site, with delivery status and a suppression list.
Your backup script pings Tusua when it finishes. If the ping stops arriving — or the file gets suspiciously small — you hear about it.
Every site checked from outside, with alerts that group instead of flooding you at three in the morning.
Stack traces from your apps, compatible with the Sentry SDKs you already know.
The privacy is in the architecture. There is nothing to configure and nothing to promise.
Visitors are counted with a salted hash that is thrown away every month. Nothing is stored on their device, so there is nothing to ask consent for.
The salt that produced last month’s identifiers is deleted, not archived. Once it is gone, nobody — including us — can work back to an address.
They exist only in a separate security log, kept six months for abuse prevention, and only if you switch it on.
One server, in Europe, running software you can read. No data broker in the middle.
Name it, list its domains, get a site key.
A single script tag, one kilobyte over the wire, loaded after your page has already rendered.
Visits show up live. Point your contact form at the same account and the leads land in the same place.
Every integration ships as a skill for Claude Code and similar agents: paste the prompt, let it edit your templates, confirm the test pageview arrives. It is how we integrate our own sites.
It is smaller, it is yours, and it does not need a consent banner. You lose the parts of Google Analytics built for advertising audiences; you keep the parts that tell you what people did on your site. And it answers in one page instead of eleven.
Those are excellent analytics products. Tusua is analytics plus the other four things you were going to install anyway: form intake, alerting, backup heartbeats and uptime. If you only want analytics, use them — honestly.
It is about one kilobyte over the wire, loaded deferred, and it sends data with sendBeacon after the page is interactive. It cannot block rendering, and if our server is down your page does not notice.
Not for Tusua. We store nothing on the visitor’s device — no cookie, no localStorage entry, no fingerprint. If you have a banner it is because of something else you installed.
You export it and we delete it. Deleting an account deletes its rows, not flags them.
The integration snippets and SDKs are yours to read and audit — they run on your pages, so you should be able to. The platform itself is a hosted service.
Registration is invite-only while we build it out with a handful of real sites. Tell us what you run and we will get in touch.