PascaleBeier/hitkeep

curl -fsSLo compose.yml https://raw.githubusercontent.com/PascaleBeier/hitkeep/main/examples/compose.yml && curl -fsSLo .env https://raw.githubusercontent.com/PascaleBeier/hitkeep/main/examples/.env.example && docker compose up -d

Usage

• •Fill .env with a long random value (replace paste-the-generated-value-here), run docker compose up -d, then open http://localhost:8080 and create the first account.
• •Add the tracker to your pages: <script async src="https://analytics.example.com/hk.js"></script>.
• •Use custom events for product-specific actions such as signups, purchases, or qualified leads.
• •Before exposing an instance publicly, follow the Docker Compose guide for HTTPS and trusted proxies, and review backups and the configuration reference.

Key features

• ✓100% open source (MIT) with custom tracking domains and team SSO in the same public codebase.
• ✓AI-native analytics: crawler fetches, AI-referred visits, and chatbot outcomes stay distinct; Ask AI answers with cited aggregate evidence; read-only MCP gives approved assistants governed analytics access.
• ✓Privacy by default: the browser tracker sets no analytics cookies, respects Do Not Track, and doesn't build a cross-site identity.
• ✓Reporting across pages, automatic and custom events, goals, funnels, ecommerce revenue, UTM/QR campaigns, Search Console, and Web Vitals.
• ✓Full data sovereignty: self-host one binary or export via takeout, REST APIs, webhooks, and share links.

Best for

Self-hosters who want cookie-free, open-source web analytics with AI visibility and governed assistant/MCP access.

Caveats

• ⚠Web-focused by design: favors aggregate traffic and conversion evidence over visitor profiles, session replay, mobile SDKs, or built-in experimentation.
• ⚠Keep .env private and retain the same secret across restarts; follow the HTTPS/proxy guide before public exposure.
• ⚠The README doesn't document the MCP transport; MCP access is described as read-only.