Host Umami without installing anything
Web analytics without cookies: two kilobytes of script served from your own domain, and no banner left to click through.
Starting at €4.99/month
Introduction
Umami installed, updated and backed up by us, on a machine in France. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Essentiel at €4.99/month incl. VAT — 2 GB of memory. Umami is a Node.js application backed by a PostgreSQL database, and it is the database that carries the weight: every page view becomes a row, and the dashboard aggregates those rows on the fly to draw its curves. A site with a few thousand visits a month is untroubled; the headroom is for the busy moments, when an aggregate query covers several months at once.
Umami replaces Google Analytics for everyone who never needed three quarters of Google Analytics. The tracker goes into your template as a single line; UTM campaign parameters come back exactly as you set them; an event is declared by naming a click or a form submission. There is, however, no import from Google Analytics: the two data models do not line up, and the usual approach is to run both for a few weeks and then start a clean history on a chosen date.
What managed hosting changes
No cookie, therefore no banner
Umami leaves nothing on the visitor's machine and builds no identifier that follows them from site to site: visits are tied to a fingerprint recomputed every day. That is the condition that makes a consent banner unnecessary in most setups.
Two kilobytes, served by your domain
The tracker weighs a fraction of Google's and loads from your own domain name: it does not hold up rendering and escapes the blocklists that quietly remove part of the traffic measured elsewhere.
A dashboard that needs no manual
Page views, sessions, average duration, bounce rate, referrers, countries, browsers, devices, campaigns: it all fits on one screen, with no custom report to build before the first useful number appears.
Named events and share links
A click on "Request a quote", a form submission, a download: each event is named and counted. A site dashboard can then be shared through a public read-only link, without creating an account for whoever receives it.
Why hand it over rather than install it
A tradesperson's brochure site
Knowing how many visitors opened the "Contact" page and which search brought them there. Three useful numbers, with no plugin to install and no banner to click.
A blog or a local news site
Which articles are read, how long people stay on them, which sites send traffic: enough to choose the next subject without handing your audience to an ad network.
An agency reporting to clients
One dashboard link per client, read-only and limited to their own figures. No more screenshots pasted into a monthly report.
A shop following its campaigns
The UTM parameters of a newsletter or an ad come back unchanged in the dashboard, and an "add to basket" event is counted like everything else.
A public body or a charity
Measuring a public website without shipping visitor data outside Europe, and being able to explain in one sentence what is collected when the question comes up at a board meeting.
Hosted in France
In our own infrastructure in Nouvelle-Aquitaine, which we operate ourselves. The audience data stays with you, and the person on the phone speaks your language.
Frequently asked questions
Umami sets no cookie and no persistent identifier, which is the main condition. The exemption still depends on use: European data protection authorities expect the measurement to stay aggregated, not to be cross-referenced with other processing, and not to be passed on to third parties. An instance of your own, shared with nobody, sits within that frame; the exact conditions are published by your national authority and deserve a read before the banner comes down.
No, there is no GA4 import into Umami: the two tools do not count the same things in the same way. The usual method is to leave both trackers in place for a few weeks, export the GA4 reports you care about as CSV, then start the Umami history on a clean date.
Page views usually go up: the Umami tracker is served by your domain and is not cut off by blocking extensions, which quietly remove part of the traffic Google measures. On the other hand, with no persistent identifier, unique visitors are counted per day: an Umami monthly total and a Google Analytics monthly total are not directly comparable.
One line of script in your site template, and that is the whole tracking side. On the server, nothing: you choose the application, fill in the fields it asks for, and it goes online. Access arrives by email with the address and the credentials.
Yes, they are part of the service, database migrations included — the delicate part with Umami, whose major releases reshape the schema. We apply them and we check that the dashboard still answers afterwards.