Matomo provides a full set of web analytics features, but sometimes that's too much. Funnels, A/B tests, and heatmaps remain unused, and all you really need is a traffic chart and a list of the most popular subpages. Umami is exactly that: one screen with charts, no cookies, no consent banner, and the data stays on your server. Below is a step-by-step guide on how to set up Umami on Saplo.
Umami or Matomo, which one to choose?
Both tools solve the same basic problem as Matomo, which is analytics without handing over visitor data to a third-party company, but they target a different user:
- Umami offers a single screen with charts of traffic, sources, and the most popular pages. Installation takes just a few minutes, with zero configuration beyond pasting a script. It's great when you want to know "how many people and from where" without delving into settings.
- Matomo is a full equivalent of Google Analytics: conversion funnels, goals, segmentation, and optional heatmaps. It's ideal when analytics is your primary work tool, not just a way to check visit counts.
If you're unsure which to choose, start with Umami. It's lighter and quicker to set up, and if you find yourself needing more features later, Matomo is right there in the same App catalog.
Why Umami Instead of Google Analytics
Like Matomo, Umami keeps data on your server instead of sending it to Google, which eliminates the most common reason for a cookie consent banner:
- Zero cookies. Umami identifies visits without storing anything in the visitor's browser, so in most cases, you don't need an analytical cookie consent banner.
- Data doesn't leak anywhere. Your own Box is the data processor, so there's no basis for a data processing agreement with a foreign provider.
- You paste the tracking code just like Google Analytics. A single JavaScript tag in the
<head>section, without changing the rest of the page.
Requirements
To install Umami on Saplo, you need:
- A Box with Docker running. The engine automatically enables it during installation from the catalog, and the required nesting in the Saplo container is enabled by default.
- A minimum of 1 GB RAM and 2 GB of free disk space on your Box.
- A Domain or subdomain
*.saploapp.pl, which is included in the price of every plan.
Umami, unlike Matomo, doesn't use Saplo's shared MySQL database. It requires PostgreSQL, so the recipe deploys its own database container alongside the application, following the same pattern as Wiki.js, Directus, or Listmonk. This means the installation doesn't require a separate database from the catalog.
Step-by-step installation
- In the Saplo panel, go to App catalog and select Umami (category "Data").
- Indicate the Box on which it should be installed, and the domain or subdomain under which the analytics panel will be available.
- Confirm the installation. The engine deploys two Docker containers: the official
ghcr.io/umami-software/umamiimage and its own PostgreSQL for data, and then exposes the panel under the specified domain via nginx with a free SSL certificate. - Once completed, the domain will display the Umami login screen.
First login and password change
Unlike Matomo, where you create an administrator account yourself in the wizard, Umami does not have variables for setting up your own account during installation. The image assumes a fixed, default account:
- login:
admin - password:
umami
Change this password immediately after your first login, in Settings → Profile → Change password. Until you do so, anyone who knows the address of your installation can log in to it using the default credentials.
Adding a website and pasting the tracking code
- After logging in, go to Settings → Websites → Add website and provide the name and Domain you want to measure.
- Umami will generate a JavaScript code snippet with its website ID. Paste it into the
<head>section of the measured website, exactly like with Google Analytics. - After a few visits, the data will appear on the Dashboard: traffic over time, countries, traffic sources, and most popular subpages.
Umami vs. Matomo on Saplo
| Umami | Matomo | |
|---|---|---|
| Complexity | single screen, minimal configuration | full suite: goals, funnels, segmentation |
| Database | dedicated PostgreSQL container | shared Saplo MySQL |
| Admin account | default admin/umami, changed manually | created by you during setup |
| Cookies | none, no consent banner | optional cookie-less mode |
| For whom | quick traffic overview | analytics as a work tool |
| Price | included in your Saplo plan | included in your Saplo plan |
FAQ
Do I need to change the default administrator password? Yes, absolutely, and immediately after your first login. The Umami image assumes a fixed admin/umami account, so until you change it, anyone who knows your installation's address can log in.
Does Umami free me from the cookie banner? Umami does not store cookies on the visitor's side, so in most cases, yes. However, it's worth consulting a lawyer for a final assessment of GDPR compliance, as it depends on your website's overall configuration.
How does Umami differ from Matomo, besides its appearance? Umami is a single screen with basic statistics: traffic, sources, popular pages. Matomo adds goals, conversion funnels, segmentation, and optional heatmaps. More about Matomo can be found in a separate post.
Can I have Umami and Matomo on the same Box? Yes. Each plan has an unlimited number of applications; the only limitations are the Box's RAM and disk space. You can even keep both if you want to compare them.
How many websites can I measure with one Umami installation? No limit. A single installation supports any number of websites, and each gets its own tracking code and separate statistics in the same panel.
If you have questions about setting up Umami on your own Box or are hesitating between Umami and Matomo, write to us. We'll help you choose.
- #Analytics
- #Matomo
- #Guide
- #GDPR
- #Umami
