Contents
1 Introduction
In previous articles, I wrote two about building your own Umami, one of which was about setting up version 1.33.1 (see article:Docker series builds a website traffic monitoring system based on umamiOne article is about setting up version 2.11.3 (see article:Home Data Center Series The latest version of umami (2.11.3) detailed construction tutorialAlthough I also deployed Google Analytics 4, Umami is indeed a very good complementary tool—its interface is clean and its data is intuitive, making it ideal for quickly viewing visitor behavior and trends. From a personal user perspective, it is even more lightweight and user-friendly than GA4.
However, building my own Umami also has its challenges that make me feel a bit "tired": every major version upgrade (such as from 1.x to 2.x, or from 2.x to 3.x).If the data structure changes, the old data may not be able to be seamlessly compatible.For example, the newly released v3 version even removed support for MySQL, retaining only PostgreSQL. This is awkward for older sites built on MySQL: they either have to go through the trouble of a complete migration or discard historical data and start from scratch. Of course, there's another option: stick to one version for life. However, those who know there's a new version and still refuse to upgrade are incredibly patient and have immense patience—far beyond the average person.
I'm now facing the choice of whether or not to upgrade Umami to version 3. I want to see what new features the new interface has, but I really don't want to go through the hassle again. After all, I've already gone through the process of upgrading from version 1 to version 2 once, and even if I upgrade from version 2 to version 3 this time, there are countless other major version upgrades to come, since Umami has a major version upgrade almost every year. Although theoretically I could manually back up and migrate the database and then follow the upgrade documentation step by step, in practice it always feels like performing "brain surgery" on the database—a slight mistake can lead to errors, data loss, or even rebuilding the service. For this reason, many people simply deploy everything from scratch during major version transitions, leaving no historical data.
On the other hand, self-hosting Umami actually consumes a significant amount of resources. Especially if you're like me and using WordPress to build your blog, with WordPress + MariaDB already running on your VPS, plus a Docker version of Umami (and PostgreSQL), even a "mid-range" machine with 2 vCPUs + 2GB of memory isn't very powerful. Not to mention that most people's servers definitely run more than just these two services; logs, backups, proxies, and a bunch of other smaller things also compete for resources.
So, is there a way to enjoy Umami's useful statistics without having to build your own server, go through the hassle of upgrades, and always keep using the latest version?
Of course there are, and that's what this article will introduce— Umami Cloud Managed ServiceWith official hosting, you can always experience the latest features of Umami, saving you the hassle of maintenance and setup. Crucially, the free version's quota is more than enough for most personal blogs.
2. Comparison of advantages and disadvantages between self-built Umami and Umami Cloud hosting methods
While I think the free version of Umami Cloud's quota is perfectly adequate for most personal blogs, everyone's needs are different, and the free version of Umami Cloud does have its shortcomings. Therefore, in this chapter, I will briefly explain... Self-built Umami and Umami Cloud HostingThe advantages and disadvantages are listed so that everyone can see them at a glance and choose the most suitable method according to their own situation after comparison.
| Dimension | Self-built Umami | Umami Cloud Hosting |
|---|---|---|
| Deployment and Maintenance | It requires setting up your own server and database (starting from version 3, only PostgreSQL database is supported), which offers high flexibility but also high maintenance costs. | Simply register an account, create the corresponding site, generate and embed the tracking code in the site code to use it. The server and database are officially hosted, requiring no maintenance, and upgrades are completed automatically, saving you time and effort. |
| Data migration and upgrade | When upgrading to a major version, the database structure may change, requiring manual data migration. Careless operation may result in errors or loss of historical data. | Data migration and compatibility are handled by the official team; upgrades are transparent, stable, and reliable.The free version only saves data from the last 12 months.. |
| Performance and resource consumption | For VPS or server performance requirements, especially when running WordPress + Umami simultaneously, even a mid-range model with 2 vCPUs + 2GB of memory will not be able to handle the demands. | Performance is handled by the official system, does not consume local server resources, and eliminates concerns about resource bottlenecks caused by traffic fluctuations, making it suitable for lightweight usage scenarios. |
| cost | The software is open source and free, but you need to pay for the VPS to run it. | Eliminating maintenance costs, the free version supports up to 3 sites and 1 million events per month, which is generally sufficient for personal blogs; the paid version is charged based on features and the number of events. |
| Privacy and Data Control | Data is stored on our own servers, giving us complete control, including backup, deletion, and export, all in accordance with our own privacy policies. | Data is stored on Umami Cloud, where privacy and compliance are officially guaranteed and the data can be used on legitimate websites, but ultimately the data is not entirely under your control. |
| safety | You need to manage server security, database access control, firewall rules, bot protection, HTTPS configuration, etc. yourself. Security depends on proper configuration and there is a risk of human error. | Using the official cloud service, which uses HTTPS by default, with built-in security mechanisms and an isolated environment, reduces operational risks, but requires trust in the security of the official data hosting. |
| Flexibility | It allows for free modification of the source code, customization of configurations, expansion of functions, and integration with the system, making it suitable for secondary development or complex scenarios. | The functionality is limited by the official interface and API, so customization is not high, but it is sufficient for most common monitoring needs. |
| Applicable scenarios | It is suitable for users who rely heavily on historical data, value autonomy, or enjoy tinkering with the system, as well as those who want complete control over privacy and interface openness. | Suitable for users who want a hassle-free, quick deployment and focus on data visualization without maintaining the backend, especially individual bloggers, small businesses, and small websites. |
Summarize:
From an overall comparison, the biggest advantage of self-built Umami is that... Complete control over data, unlimited historical records, and unlimited monitoring sites.However, at the same time, it is necessary to Maintaining servers yourself, manually upgrading them, and bearing the performance pressure.Umami Cloud's advantage is... No maintenance required, automatic upgrades, stable performance, and quick to learn.It's very worry-free.
Of course, the free version of Umami Cloud also has obvious disadvantages:It only supports a maximum of 3 sites, and data can only be retained for the most recent 12 months.If you can accept these two points, then for personal blogs or small websites, Umami Cloud is undoubtedly the most worry-free and straightforward solution.
3. Register for Umami Cloud and complete the basic configuration steps.
Visit the official website registration link —https://cloud.umami.is/signupConfigure according to the following illustrated tutorial:

Umami Cloud will then send a confirmation email to the registered email address:

In the confirmation email, copy the 6-digit confirmation code and click the "Login" button to be redirected to the login verification page:

Log in using your registered username and password on the login page. On the confirmation page, enter the 6-digit confirmation code from the confirmation email to confirm.


When registering for Umami Cloud, you need to select a data storage region (USA or EU).The chosen region determines which data center the data will be stored in, as well as the applicable laws and privacy rules.Generally speaking,The EU region is more compliant with GDPR requirements, making it suitable for users who prioritize privacy and compliance.The US region may offer faster global access and a simpler legal environment. If your visitors are primarily not from the EU, the US region is recommended.


Generate a JavaScript script containing the tracing code:


Similarly, you can add other sites (a free account can add up to 3 sites). After that, you just need to insert the saved site tracking code script into the code of the site you want to monitor (for WordPress users, please refer to the following link for instructions on how to insert the code:Inserting Umami tracking code in WordPress).
If you have a Cloudflare account and your site is published through Cloudflare, you can directly load JavaScript scripts from the cloud using Zaraz technology, without adding them directly to your website code. For those interested, please refer to the article:Home Data Center Series Optimizing Website Loading Speed: Cloud Loading and Management of Third-Party Scripts via Cloudflare ZarazAlso, Cloudflare's UI has changed significantly again. The zaraz feature has been moved to the following location, which took me ages to find:

Finally, click on the website name to access the monitoring interface:


Note: To save time, I won't take screenshots of each feature individually. If you're interested, you can register a Umami Cloud account and try it out for yourself.
4. Enable sharing via dedicated links
At the end of the previous chapter, I briefly introduced the site statistics displayed in the official Umami Cloud UI. However, this UI is only visible after logging into Umami Cloud and cannot be used for external publishing. To publish externally, you need to enable the "Share Link" feature, which is located in the upper right corner of the official UI.


After that, anyone can view the site's access statistics in read-only mode via this link. You can see the demonstration effect directly through this link:Umami Cloud statistics display link.
5. Data Export
Umami Cloud has one more feature than a self-built Umami: exporting statistical data. So, for bloggers who are unsure whether they need to build their own Umami, they can try using Umami Cloud for a while first. If they are satisfied and confirm that they need to retain the data for a long time, they can export the statistical data from Umami Cloud and import it into their self-built Umami according to the official manual.

Click the "Settings" button:



You will then receive an email in your registered email address containing a link to download and export the data.

Clicking the download link will download a zip file. After unzipping, the resulting folder contains three CSV files:

The main file is "website_event.csv". Opening it will show the statistics:

The remaining task is to import the CSV file into the corresponding PostgreSQL or MySQL database of your self-built Umami. There are many tutorials online, and interested users can explore them on their own.
6 Conclusion
Choosing between building your own infrastructure or using cloud services is essentially a balance between "self-control" and "delegating to others."There is no absolute good or bad, only what is suitable or unsuitable.
For example, many bloggers choose to build their own Umami because they value its flexibility—complete control, no restrictions, and self-control over major version upgrades; while some later migrated back from Umami Cloud to their own platform because they didn't want to be limited by the 12-month data retention restriction of the free version.
However, if you simply want a simple and stable access statistic, without relying on long-term data or demanding highly customizable capabilities, then... The free version of Umami Cloud already has enough features.This is especially true for personal blogs, static sites, and some lightweight information pages.
Therefore, the key is still the demand:
- If you have a high degree of control, want to retain detailed data for a long time, and are willing to maintain the service, building your own system is definitely the right choice.
- If you want to quickly get started with statistical analysis, don't want to go through the hassle, and don't mind that historical data is kept for a maximum of 12 months,Therefore, the free version of Umami Cloud is actually the optimal solution..
For most personal blogs,The data from the past 12 months is sufficient to fully reflect key indicators such as reader trends, content performance, and SEO effectiveness.Umami Cloud's free version guarantees one year of data retention, which already covers the vast majority of usage needs.
Only users with strict analytical needs for long-term data will consider the requirement to "retain 3-5 years of data" as a necessity.But frankly, for most individual bloggers, this is more of an obsession or "compulsion"—especially when the number of visits is not high. Keeping old data that is rarely reviewed for a long time not only takes up storage space but also has little practical value.
Personally, aside from checking Umami's statistics daily out of novelty when I first deployed it, I'm now too lazy to look at them anymore. After all, it only gets a few hundred visits a day at most, so it doesn't really matter whether I check it or not. At most, I might check the recent 24-hour visitor count on a whim. It seems a bit wasteful to spend VPS resources building and maintaining an application that I only occasionally think of checking (and then there's a major version upgrade every year) now (at least for me).
Therefore, for someone like me, Umami Cloud is a more suitable choice.
我在2.X时就用的PostgreSQL版本的,倒是没什么感觉直接就升级到3.X。唯一就是残留了一个小bug,2.X时代,默认页是跳转「/dashboard」的。3.X默认页变成了「/websites」,升级3.X后,直接访问应用的域名,还是会跳「/dashboard」直接404了。
如果一直是PostgreSQL的话,跨大版本升级正常应该没问题,怕的就是不正常嘛。如果真的对历史数据非常在意的话,升级前常规的备份预防手段还是应该要做的,毕竟不怕一万,只怕万一。我之前从1.x升级到2.x,主要是部署方式都变了,从docker compose的一体化部署方式变成了linux容器部署Umami服务端+docker部署POstgreSQL的分离式部署,所以才瞎折腾了半天。不过,关键还是对历史数据到底有没有那么在意的问题,不在意的话,一年的数据足够用了,这种情况下Umami Cloud托管的方式就最省心了。