HitKeep is a 100% open-source, MIT-licensed, AI-native web analytics platform written in Go that self-hosts as a single binary with embedded DuckDB and NSQ, or runs as a managed cloud service in EU or US regions, and it is built for teams that want cookieless traffic, conversion, and AI-visibility reporting under their own control.

What it is

HitKeep is a web analytics product that unifies traffic, conversions, Search Console data, and AI visibility in one Go binary. It lives in the Go and DuckDB ecosystem: the storage engine is embedded DuckDB, the messaging layer is embedded NSQ, and the whole installation ships without a separate database, queue, or cache to operate. The complete product is MIT-licensed, so custom tracking domains and team SSO sit in the same public codebase rather than a separate proprietary edition.

The concrete problem it solves is fragmentation and lock-in. A typical analytics stack means a hosted pageview counter or self-managed analytics server, plus a database, a queue, and a cache that someone has to run and back up, plus a proprietary tier where custom tracking domains and SSO actually live. HitKeep replaces that combination with one binary and open export formats, so the data stays useful outside the tool through complete takeout, APIs, webhooks, share links, and permissions.

Key capabilities

• Cookieless browser tracker that sets no analytics cookies, respects Do Not Track, and collects focused website analytics without building a cross-site identity.
• AI-native channel reporting that keeps crawler fetches, AI-referred visits, and chatbot outcomes distinct, with Ask AI built on cited aggregate evidence and a read-only MCP server for governed analytics access by approved assistants.
• Full reporting chain from acquisition through pages, automatic and custom events, goals, funnels, ecommerce revenue, UTM and QR campaigns, Search Console, and Web Vitals.
• Automatic interaction events for outbound clicks, file downloads, and form submissions, plus custom events for signups, purchases, and qualified leads.
• Data sovereignty features: open exports, complete takeout, APIs, webhooks, share links, and permissions.
• Custom tracking domains and team SSO delivered in the same public MIT codebase.
• Deployment as one Go binary with embedded DuckDB and NSQ, with Homebrew (PascaleBeier/hitkeep/hitkeep), Docker Compose (compose.yml), and AMD64/ARM64 release binaries as supported paths.

Who uses it and how

• Self-hosters who want full data sovereignty run the single Go binary on their own infrastructure and keep analytics traffic inside their own boundary.
• Teams that do not want to operate it use HitKeep Cloud in a managed EU or US region while keeping the same product surface.
• Privacy-conscious site owners deploy the cookieless tracker and rely on Do Not Track handling instead of consent-heavy cookie analytics.
• Product and ecommerce teams follow acquisition through pages, goals, funnels, and ecommerce revenue, using UTM and QR campaigns and custom events for signups, purchases, or qualified leads.
• Organisations exposing an instance publicly run it behind HTTPS and trusted proxies and pair that with the documented backup and configuration references.

Getting started

On Apple silicon macOS or x86_64 Linux, install with Homebrew: brew install PascaleBeier/hitkeep/hitkeep, then verify with hitkeep --version. For a production-oriented self-hosted setup, download compose.yml and .env.example, replace paste-the-generated-value-here with a long random value, run docker compose up -d, and open http://localhost:8080.

How it compares

No competing products are named in the facts for this entry, and no list of paid products it replaces is provided. On the evidence available it stands alone in this registry.

When to use it — and when not to

A self-hoster operates the binary, manages the .env secret across restarts, terminates HTTPS behind a trusted proxy, and owns backups and restore, though there is no separate database, queue, or cache to run. HitKeep is deliberately web-focused: it favours aggregate traffic and conversion evidence over visitor profiles, and it does not offer session replay, mobile SDKs, or built-in experimentation, so teams needing those should look elsewhere. Public signals are also early-stage — 88 stars, 8 forks, and 9 open issues — which is worth weighing before a large deployment.

brew install PascaleBeier/hitkeep/hitkeep
hitkeep --version

mkdir hitkeep && cd 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

<script async src="https://analytics.example.com/hk.js"></script>