About
EU-hosted web and product analytics, built on the assumption that a privacy-first analytics tool should actually behave differently, not just say so on the homepage.
Metricward is an event-based analytics platform for websites and products: pageviews and custom events, funnels, retention cohorts, segments and dashboards, all served from infrastructure hosted in the EU. Revenue analytics, scheduled reports, session replay, experiments and a reporting API are on the roadmap at different stages of readiness. The pricing page and the changelog say plainly which of those exist today and which do not, so the plan you choose is the plan you will still want.
Metricward is built by the same people behind Formward, a European form-submission backend. Building a second EU-hosted product meant deciding, file by file, what generalises and what does not: authentication, billing metering, the SSRF guard on outbound webhooks and the deployment conventions carried over largely unchanged, while identity hashing, the event pipeline and the ClickHouse schema were written from nothing, because an analytics platform's hardest problems are not a form backend's hardest problems.
We are not disclosing a headcount, a founding date or a funding position here. None of those change what the product does, and stating a number just to have one on the page is the kind of padding this page exists to avoid.
EU hosting is not a checkbox.
The stack runs on infrastructure in Sweden. Where a subprocessor is not EU-resident, it is named and explained rather than buried, on the subprocessor page.
Raw IP does not belong on a disk.
An IP address is used in memory for a geo lookup and a daily salted hash, then discarded. No table anywhere has a column that could hold one.
Every number says what kind of number it is.
Observed, calculated, modelled or generated. A chart that quietly presents a guess as a measurement is the failure mode we designed the whole product against.
Bots are labelled, not disappeared.
Detected traffic is flagged and kept out of your reports and your bill, but it is never silently discarded, because a filter you cannot see is a filter you cannot audit.
Cookieless is not a legal shortcut.
We will not tell a customer that removing cookies removes their consent obligations. ePrivacy covers accessing information on a device generally, not only cookies, and whether a given setup needs consent is a question for that customer's counsel, not for our marketing copy.
A tool cannot make you compliant.
We are a processor. Compliance is a property of an organisation's legal basis and notices, not of software it installed. We say this on the privacy page and we mean it.
Metricward is new. There are no customers yet, no case studies and nothing to point to beyond what is actually built. A fair amount of the architecture described in these pages is implemented and has automated tests behind it; some of it is a specification waiting to be built. Billing and outbound email are not wired yet, so a paid plan today is an email conversation rather than a card form, and we say so on the pricing page rather than let anyone find out at checkout. The unglamorous list of what does and does not work yet lives on /security and /legal/compliance, written for the person who has to check before they buy, not the person we would like to impress.