Product analytics, without the surprise bill.

Anonymous by design. EU-hosted. €19/mo for 1M events — not "starting at €25 then €0.0001 per event after that." Funnels and retention cohorts that read your schema, not the other way around.

No card · 100k events / month free · EU servers · GDPR-clean

How we compare

 OwlsignalMixpanel / AmplitudeSegment / RudderstackPostHog Cloud
Pricing modelFlat monthly tier. €19 = 1M events. No per-event metering.Per-event after a small free quota. Bills swing with traffic.Per-MTU + per-event passed downstream. Stack stacks up.Per-event after 1M free. Cheap then steep.
Data residencyEU-only stack (Frankfurt + Amsterdam + Paris).US default. EU-hosting is enterprise-tier.US default. Regional routing on paid tiers.US or EU on Cloud, but ingestion is global.
What you instrumentWhatever your team calls things. Anonymous device hash; no PII.Page views + opinionated event taxonomy. Identified users by default.Pipes everything everywhere; you also pay each downstream tool.Auto-capture browser events; identified users; session replay sold separately.
Loop verdictDefine your funnel + targets. Get "on / below / above target" per app.Builds funnels — you have to interpret them yourself every Monday.Pipes data. Funnel-building lives in whichever tool you forwarded to.Builds funnels — same "interpret it yourself" pattern.
Cookie bannerNot required. Anonymous, no PII collected.Yes (identified user tracking).Yes (typically).Yes (session replay + identification).

Why teams switch

Predictable bill
€19/mo gets you 1M events, 30-day raw retention, 5 apps. No surprise charge after a viral spike, no "platform fee" stacking on top, no "talk to sales" for a real price.
Loop verdict, not a buffet
You define what success looks like — funnel stages with target conversion %. Owlsignal tells you "on target / below target" per app, on the dashboard. Not 12 charts you have to interpret on Mondays.
Anonymous by design
No emails, no IPs, no fingerprinting. Device-hash generated client-side. GDPR-clean without the cookie-banner theatre — no consent dialog needed because there's no PII to consent to.
EU stack, period
Database in Frankfurt (Supabase). Functions in fra1. Billing via Mollie (Amsterdam). Email via Brevo (Paris). One US sub-processor on the control plane (Vercel) under SCCs — disclosed.
Your event schema, untouched
No imposed page_view / button_click model. You name events how your team talks about the product. Loop builder reads your existing names — no remapping the whole codebase to fit "auto-capture".
SDKs in two flavors
Web (JS/TS) for browsers, vanilla JS, React, Vue, Svelte. Unity SDK for game devs. One backend, one event schema across both — drop in the SDK, ship events, see the dashboard fill up.

Who it fits

Owlsignal is currently in closed beta. Anyone shipping a product with a "did the user reach the moment we wanted them to" question is a fit.

  • SaaS & web products — drop in the JS/TS SDK; track activation funnels, feature adoption, retention cohorts.
  • Indie game studios — Unity SDK + run analytics + opt-in run-shape views. See the games-specific pitch →

How it works

  1. Sign up free — no card, get an organization + first app + API key in under a minute.
  2. Drop in the SDK — Web or Unity. Three lines to Initialize, ship events.
  3. Define your loop — pick a template or describe your product in plain English and let the AI suggest stages. Edit anything; you own the schema.
  4. Read the verdict — funnels, retention, errors. One-line "on / below target" per app. Drill in when something needs attention.
Closed beta, invites open. hello@owlsignal.dev if you want in.
Owlsignal · operated by Zisomedia · The Netherlands Privacy · Terms · DPA · Cookies