Skip to main content

Fully Managed Umami
as a Service

Deploy Umami as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Umami is an open-source web analytics platform — pageviews, events, sessions, and Core Web Vitals — combining the clarity of a privacy-respecting tool with the control of self-hosted infrastructure. Your data stays in your chosen region. Your visitors never see a cookie banner. Your database is one pg_dump away whenever you want to leave.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Umami

Umami

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Umami Preview Image

ABOUT THE SOFTWARE

What is Umami

Umami is an open-source, privacy-respecting web analytics platform — a server-rendered Next.js application on Node.js backed by PostgreSQL. It tracks pageviews, events, sessions, and Core Web Vitals without setting cookies, fingerprinting visitors, or sending data to a third party.

Umami was open-sourced by Mike Cao in 2020 under the MIT license — the most permissive license among privacy-focused analytics tools, which makes the project effectively un-fork-and-leaveable from the user's side. The codebase has been built and maintained by Umami Software, Inc., with roughly 36,700 GitHub stars and 345 public contributors at the time of writing.

The platform supports a single Umami instance tracking unlimited websites, with team accounts, segments, custom events, and revenue tracking baked into the core. v3.1.0 added Boards — drag-and-drop custom dashboards with shareable read-only URLs — alongside Session Replay built on rrweb, and real-user Core Web Vitals measurement covering LCP, INP, CLS, FCP, and TTFB. The tracker script itself is under 2 KB gzipped. The database schema runs on PostgreSQL; the older MySQL path is no longer documented upstream.

FEATURES

What Umami does

Umami covers pageview counting, event tracking, custom dashboards, session replay, real-user performance metrics, team-managed read-only sharing, and an HTTP collection API. Eight features pull most of the weight for the privacy-focused operator who needs more than a cookie-banner ornament.

Cookie-free visitor tracking

A server-side salted hash of IP and User-Agent rotates daily, producing a unique-visitor count that cannot be linked across days. No cookies, no localStorage, no fingerprinting.

Session Replay

Per-visit playback built on rrweb, with configurable input and content masking. Filterable replay table by URL, country, browser, or custom event.

Pixels and Links

Invisible 1×1 tracking pixels for email newsletters and short-link redirects with click counting. Useful for measuring channels outside the website itself.

Segments and filtered views

Saved filter sets and query-string-driven filters that survive sharing. Drill into "European visitors on mobile who saw the pricing page" in one URL.

Boards (custom dashboards)

Drag-and-drop layouts combining metric tiles, charts, and tables. Each board has a shareable URL with read-only access for clients or stakeholders.

Core Web Vitals

Real-user LCP, INP, CLS, FCP, and TTFB measured from the same tracker, no extra script. Per-page breakdowns and country-level performance views.

Custom events and revenue

umami.track() JS calls or data-umami-event HTML attributes. v3 added revenue tracking as a dedicated event type with currency support.

Collection API

Send events server-side from Node, Python, Go, or any HTTP client. Useful for backend conversion tracking, mobile apps, or hybrid analytics workflows.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Umami

On February 12, 2026, the European Data Protection Board published its 2025 enforcement report on the Right to Erasure — and named "sector-specific inspections through 2026" as the next step. Nine European data protection authorities have already opened formal investigations. Operators running Google Analytics on European traffic are now on the inspection list.

That report is the reason most of our Umami signups since March 2026 have come from European e-commerce and publishing operators who finally moved off Google's stack. They picked Umami because it doesn't set cookies, doesn't store IPs, doesn't fingerprint, and runs on a database they control.

What they discovered, three weeks in, is that running Umami on a $24 production-class VPS is the easy part. The hard part is everything around it.

We have run Umami in production long enough to have hit, and fixed, the specific failure modes the project's own GitHub Issues are full of:
  • Issue #3204 — the GeoLite2 city lookup leak that pinned 32 GB of RAM until restart, on a small instance. The maxmind library re-opens the database file on every request unless you cache it. We cache it.
  • Discussion #2490 — the shared-memory segment exhaustion when Postgres tries to resize past the default Docker 64 MB /dev/shm limit. The error message is opaque ("could not resize shared memory segment"). The fix is a docker-compose.yml edit and a container rebuild. We ship the larger shm_size by default.
  • Discussion #1026 — uBlock Origin and Brave block the default script.js filename and the /api/send endpoint out of the box. We rename the tracker script via TRACKER_SCRIPT_NAME and reverse-proxy the collection endpoint on your domain, so your analytics doesn't quietly stop working.

What we ship by default on every managed Umami instance: PostgreSQL with raised shm_size, autovacuum tuned for the events table, and a tested upgrade path that doesn't lose your schema migrations; GeoLite2 refreshed monthly via cron with the maxmind reader cached at module load; a renamed, domain-proxied tracker that survives uBlock Origin, Brave, and the default Pi-hole blocklists; and nightly off-site backups with a tested restore procedure.




REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Umami on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

PERSON E-COMMERCE STORE (LYON, FRANCE)

Moved off GA4 the week the CNIL hardened its 2025 cookie inspection

Region: France. Tracks the Shopify storefront and a customer portal on a separate subdomain. Custom events: add-to-cart, checkout-step-completed, refund-issued. Revenue tracked in EUR. Dashboard shared read-only with the marketing manager and legal counsel. Board "Funnel by region" splits French, German, and Italian traffic onto separate cards.

12-PERSON DIGITAL AGENCY (HAMBURG, GERMANY)

One Umami instance per client, billed inside the retainer

Region picked per client — Germany for the local clients, UK for the British ones, Singapore for an Asia-Pacific retailer. Each Umami instance is a separate €9 line in the agency's monthly DANIAN invoice. Clients get a shareable Board URL; the agency gets one operator to call when something breaks.

2-PERSON INDEPENDENT PUBLISHER (TORONTO)

Replaced GA4 plus Plausible after the Plausible Growth tier crossed three sites

Region: Canada. Tracks the main publication, a paid-newsletter site, and an archive subdomain. Uses Umami Pixels in the email newsletter to measure open rates without a third-party tracker. LCP, INP, and CLS monitored via Core Web Vitals — surfaces slow articles before reader complaints arrive.

COMPARISON

Four ways to run Umami

The same Umami codebase runs four different ways. The math below holds for a typical privacy-focused operator tracking one to ten sites with combined traffic up to 500,000 pageviews per month. DANIAN is the lowest figure in the column once your time costs more than zero.

 PATH1 SITE / 10K PAGEVIEWS3-5 SITES / 100K PAGEVIEWS10 SITES / 500K PAGEVIEWSOPERATIONAL TIME
Privacy SaaS 
(Plausible Cloud)
$9/mo Starter$14/mo Growth$39/mo Business0 hrs (vendor-managed, European-only datacenters)
Self-host on a VPS
~$44/mo
$24 production-class VPS + $5 object-storage backup + $15 monitoring
~$44/mo + DB tuning~$44/mo + DB scaling at 25+ users5–10 hrs setup + 1–2 hrs/mo ongoing
Home server
 ~€90–150/mo effective
€700 hardware amortised over 36 mo + €17–32/mo power + €40–80/mo business uplink + €10–20/mo off-site backup target
samesame2–4 hrs/mo + ISP terms-of-service risk
DANIAN Managed Umami€9/mo€9/mo per app€9/mo per app0 hrs — pick your region

A single Umami instance tracks unlimited websites, so multiple sites on one install share the same €9 as long as combined traffic fits the base resource envelope. Plausible pricing verified at plausible.io/pricing, May 2026.

BY INDUSTRY

Umami for specific industries

Different industries put different pressure on web analytics. The four below are where managed Umami has the strongest argument — and where the wrong configuration becomes a regulatory or commercial liability. Each block names the regulatory anchor, the specific configuration we ship, and a real workflow.

The regulatory anchor: the European Data Protection Board's February 2026 enforcement report named consent-driven web analytics as a 2026 sector inspection priority.

Nine European data protection authorities have already opened formal investigations against operators relying on US-hosted analytics for European visitor traffic.

The configuration we ship: Umami in your choice of European datacenter — Germany, France, Netherlands, Sweden, Spain — Postgres encrypted at rest, daily-rotating visitor salt, no PII columns in the events table.

The workflow: a French e-commerce operator measuring an end-to-end checkout funnel — landing page through product, cart, and order — without a cookie banner, with revenue events in EUR, and a quarterly board export for the company's controller.

Typical traffic: 50,000 to 500,000 pageviews per month.

At that scale, Plausible's Business tier runs $39 per month per site; managed Umami on DANIAN stays flat at €9 across unlimited tracked sites on one instance.
The operational anchor: cookie-banner click-through is the single biggest source of false bounce-rate readings on publishing sites.

For a 100,000-pageview newsletter, a 30 percent consent decline rate means analytics misses 30,000 sessions per month.

Umami's cookie-free model removes the banner entirely.

The configuration we ship: Umami Pixels enabled for newsletter open-rate measurement without a third-party email tracker.

The workflow: a Toronto-based publisher running three publications on one Umami instance, sharing a single Board URL with the editorial team, and surfacing slow-loading articles via the Core Web Vitals view before reader complaints reach the support inbox.
The commercial anchor: agency clients pay a retainer that includes "analytics setup."

That retainer should not include four hours of monthly Postgres tuning, GeoLite refresh, and Cloudflare CORS debugging.

The configuration we ship: one DANIAN Umami instance per client, each pinned to the client's headquarters region — Germany for the German manufacturer, UK for the British retailer, Australia for the Australian SaaS startup.

Each €9 instance is a line item on the agency's monthly invoice, billable straight into the client retainer.

The workflow: a 12-person German agency runs 18 client Umami instances, hands every client a shareable read-only Board URL, and routes all operational issues to one place — our support chat.

The agency adds analytics as a managed-service line item, not a billable engineering hour.
The operational anchor: public-sector procurement increasingly mandates that visitor analytics for government and university web properties remain in a chosen sovereign jurisdiction with no third-country data transfer.

The UK Information Commissioner's Office removed Google Analytics from its own website after the Austrian data protection authority's 2022 ruling.

Umami's architecture — no cookies, no IP storage, hashed-and-rotated visitor identifier — means there is no user record to subpoena or breach.

The configuration we ship: Umami in the customer's chosen sovereign region (Sweden for Nordic public bodies, UK for UK departments), no cross-region replication, no external CDN on the tracker.

The workflow: a Swiss municipal department site measures page-level engagement on its citizen-services pages and exports monthly board snapshots for the digital-services committee, with no third-party tracker on the page.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

No. The visitor identifier is a server-side hash of IP plus User-Agent salted with a value that rotates daily. The salt rotation breaks any ability to link a visitor across days. No cookies, no localStorage, no fingerprinting libraries are loaded by the tracker.
Both blocklists target the default script filename and the /api/send endpoint. We rename the tracker script via the TRACKER_SCRIPT_NAME environment variable, and reverse-proxy the collection endpoint to a subdomain on your own zone. After that the tracker runs on every default blocklist we've tested.
PostgreSQL on every DANIAN-managed instance. The MySQL path is no longer documented upstream as of v3.x. We run Postgres with raised shm_size — the default 64 MB Docker /dev/shm is the root cause of the "could not resize shared memory segment" error in Discussion #2490 — and autovacuum tuned for the high-write events table.
The base tracker is under 2 KB gzipped — invisible in Core Web Vitals readings. The Session Replay module adds weight; we keep it disabled by default and turn it on per-site on request. Replay traffic is rate-limited at the collection endpoint to prevent runaway costs.
Yes. The tracker auto-detects History API route changes, so React Router and Next.js client navigations register as pageviews without any extra code.
Yes. The events table is yours; we provide an SQL export on request, or a streaming endpoint for Business-tier feature parity on the open-source build. Your data is one pg_dump away whenever you want it.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
No. The Umami project does not ship a GA4 import tool, and the GA4 export format is not directly compatible with Umami's events schema. Historical GA4 data is a fresh start. We document a parallel-tracking period of two to four weeks so you can validate Umami's numbers against GA4 before the cutover.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Umami for 7 days

No card. Cancel from the dashboard.