Guides, comparisons, and engineering
Building OwlEye
Practical guides to tracking useful actions, reading funnels, and understanding where visitors drop off. Plus the engineering decisions behind OwlEye.
OwlEye vs Plausible vs Umami: An Honest Comparison
Compare analytics workflows, dashboard-managed events, funnels, and dated plan allowances across OwlEye, Plausible, and Umami.
How We Built a Cookie-Free Analytics SDK
The engineering choices behind OwlEye: visitor estimates, SPA page views, lifecycle events, bounded delivery, and a measurable bundle budget.
Why We Chose ClickHouse Over Postgres for Analytics
How OwlEye separates analytics facts from metadata, batches inserts, and weighs ClickHouse against a simpler PostgreSQL deployment.
The GDPR Analytics Compliance Checklist for Indie Hackers
A practical review of analytics purposes, lawful basis, consent, event payloads, processors, retention, and evidence—with primary legal sources.
Cookie-free is not a legal force field
What OwlEye's browser defaults reduce, what the server still processes, and why analytics needs a deliberate data policy.
Small is a budget, not a leaderboard
Why OwlEye checks compressed SDK bytes in CI and keeps core analytics, rules, and performance timing separate.
The button got redesigned. Your analytics can keep up.
How OwlEye's console-managed rules reduce repeat tracking deploys, and where application code is still the right tool.
Find the step between a visit and a signup
Install tracking once, add supported events from your dashboard, and use funnels to see where visitors leave.