Tracking and analysis
Websites, events, goals and reports are configured traceably and documented in a versionable form.
We design and operate Umami as a controlled analytics platform - including PostgreSQL, tracking design, events, roles, backups and clearly defined service levels.
The following are trademarks of their respective owners: Umami (Umami Software, Inc.). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
Umami captures page views, acquisition, device classes and custom events and turns them into dashboards, funnels, journeys, retention and campaign insights. With a self-hosted platform, infrastructure and analytics data remain under your control.
WZ-IT looks beyond the tracking container. We design PostgreSQL, reverse proxy, collection endpoint, roles, retention, monitoring, updates, backups and recovery as one service and connect it to existing websites and applications where required.
We inventory websites, domains, existing metrics, events, campaign parameters, dashboards and privacy requirements. This becomes a measurement design, test phase and traceable cutover.
Historical data and metrics cannot be transferred equivalently from every analytics system. We assess available exports and APIs and define in advance what is migrated, kept in parallel or rebuilt.
Reliable web analytics depends on measurement design, data collection and operations. We combine Umami, PostgreSQL, collection endpoints, access, retention and recovery into a documented platform.
Websites, events, goals and reports are configured traceably and documented in a versionable form.
PostgreSQL, data growth, retention and exports are included in capacity and privacy planning.
Teams, roles, shared views and integrations follow an agreed access and data model.
Monitoring, updates, backups, restore tests and incident processes protect the technical platform.
We separate technical analytics operations, tracking implementation and business interpretation of metrics.
| Area | Responsibility | Scope and boundaries |
|---|---|---|
| Architecture and provisioning | WZ-IT | Umami, PostgreSQL, TLS, reverse proxy, secrets and reproducible deployment. |
| Umami runtime and updates | WZ-IT | Maintenance of the agreed instance with release assessment, backup and controlled updates. |
| Monitoring and backups | WZ-IT | Monitoring and protection of database, configuration and relevant operational data. |
| Measurement and event model | Shared | WZ-IT implements technical collection; the customer defines goals, metrics and business meaning. |
| Privacy and retention | Shared | WZ-IT implements agreed settings; the customer defines the legal basis, notices and retention rules. |
| Interpretation and decisions | Customer | Assessment of metrics, campaigns and user behaviour remains with the responsible business team. |
| Migration and integrations | Optional WZ-IT service | Tracking migration, event implementation, reporting connections and historical data are planned separately. |
Analyse page views, visitors, sessions, referrers, campaigns, countries, browsers and device classes across multiple websites.
Model clicks, forms, downloads and application steps as events and include them as traceable goals in the measurement design.
Analyse usage paths, drop-offs, return behaviour and cohorts without leaving the business interpretation of metrics to the tool.
Organise websites and reports in teams, distribute role-based access and share selected views in a controlled way.
Connect analytics data and events to applications, reports or automations through the REST API and document the resulting data flows.
Configure cookieless tracking and self-controlled data storage properly. Legal assessment still depends on the specific implementation and context.
A clearly defined operating scope instead of an opaque hosting flat fee.
Compute, applications, storage and response are shown separately. You can see what ongoing operations include and which requirements need a technical assessment.
We also design custom Umami architectures, integrations and migrations. Contact us for a technical assessment.
One managed standard Umami application is included in the Starter workload. Every service level also includes flexible expert time for planned work during regular service hours. Select compute, additional applications, storage and the appropriate service level.
A workload is one compute instance with the applications agreed for it.
One standard app per workload is already included. Additional dedicated servers count as separate workloads.
€79.90 per started TB and month, including daily encrypted offsite backup with 7-day retention.
Website count alone is insufficient. Page views, custom events, retention, concurrent dashboards and complex insights determine compute, PostgreSQL and storage.
| Usage scenario | Technical starting point | Key factors |
|---|---|---|
| One or a few websites with moderate traffic | S or M, PostgreSQL | A sensible starting point for moderate event volume and standard reports. |
| Several websites with regularly used dashboards | M or L, PostgreSQL | Traffic peaks, retention, teams and report usage are assessed in advance. |
| Product analytics with many custom events and insights | L or custom sizing | Event cardinality, funnels, journeys and retention can materially affect database and query load. |
| Business-critical analytics with specific recovery objectives | Custom architecture | Database, replication, backup, monitoring and recovery are designed against explicit RPO/RTO targets. |
Measurement design, custom event implementation and migration of historical analytics data are project services and are not included in the generic workload price.
The standard price describes one managed workload. Very high event volume, special availability objectives and custom data pipelines are added transparently.
Dedicated workload with agreed compute, backup, monitoring and service level.
Operation in the customer's account when data paths and governance should remain there.
Integration with existing virtualisation, network, database and backup processes.
Several websites or applications send data through defined endpoints to a deliberately placed instance.
Umami connects publicly embedded tracking scripts to an internal reporting platform. Data collection, proxy, access, retention and exports therefore form one architecture.
Tracking scripts, custom events, marketing parameters, dashboards, APIs and authorised users.
TLS, collection endpoint, reverse proxy, firewall rules and optional private administrative access.
Administrators, teams, website assignments, shared views and technical API access.
Web analytics, events, goals, funnels, journeys, retention, campaigns and reports.
Sessions, page views, events, configuration and reporting data with planned retention.
Monitoring, logs, updates, backups and tested recovery.
Controlled connections to websites, applications, reporting and automation.
Before production launch, we document collected data, events, retention, roles, backup scope and recovery of the complete platform.
Answers about licensing, privacy, migration, PostgreSQL and operations.
Yes. The official Umami repository is released under the MIT licence. WZ-IT is an independent provider of installation, integration and operations; Umami Cloud is a separate vendor offering.
Umami's standard tracking operates without cookies and without cross-site tracking. Whether a specific setup requires consent or notice still depends on configuration, additional events, connected data and applicable law and should be assessed legally.
Yes, as a controlled migration project. We compare metrics and event models, implement the new tracking and validate it in parallel. Depending on exports and APIs, historical data cannot always be transferred fully or equivalently.
Current Umami documentation specifies PostgreSQL. We size the database, connections, storage, maintenance and backup according to event volume and retention.
We assess release notes and database migrations, create a consistent backup, test higher-risk changes in advance and perform the update during the agreed maintenance window with a rollback plan.
The PostgreSQL database contains the core analytics data. We also protect relevant configuration and secrets for the agreed setup and test recovery instead of monitoring only the backup job.
Yes. Websites can be managed separately and assigned to teams. Roles, shared views and API access are aligned with the desired governance model before rollout.
Whether you run Umami in-house or need to host confidentiality-professional data §203-ready - we build, operate and maintain Umami on an encrypted on-site server. Data never leaves the building in cleartext.
See Umami on-premise
These solutions are often used together with Umami
These solutions offer similar functionalities and can be evaluated together
These solutions are direct alternatives with similar use cases
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep & Robin Zins
Managing Directors of WZ-IT
