Skip to content
Back to search

hitkeep

100% open-source, AI-native web analytics with cookieless tracking, open exports, custom domains, and SSO—self-hosted as one Go binary or managed in EU/US cloud.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/HitKeep/hitkeep with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/HitKeep/hitkeep'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pascalebeier--hitkeep/badge.svg)](/listings/pascalebeier--hitkeep)

HTML

<a href="/listings/pascalebeier--hitkeep"><img src="/api/listings/pascalebeier--hitkeep/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

On Apple silicon macOS or x86_64 Linux, install HitKeep with Homebrew:

brew install PascaleBeier/hitkeep/hitkeep
hitkeep --version

Follow the [Homebrew installation guide](https://hitkeep.com/guides/installation/homebrew/) to configure and start HitKeep. On Linux ARM64, use the published ARM64 binary or Docker instead.

For a production-oriented self-hosted setup, download the Docker Compose file and environment template:

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

Open `.env` and replace `paste-the-generated-value-here` with a long random value from your password manager. Then start HitKeep:

docker compose up -d

Open [http://localhost:8080](http://localhost:8080) and create the first account. Keep `.env` private and retain the same secret across restarts.

Before exposing an instance publicly, follow the [Docker Compose guide](https://hitkeep.com/guides/installation/docker-compose/) for HTTPS and trusted proxies, then review [backups](https://hitkeep.com/guides/data/backups-and-restore/) and the [configuration reference](https://hitkeep.com/reference/configuration/). For a native Linux service, download an AMD64 or ARM64 binary from [GitHub Releases](https://github.com/PascaleBeier/hitkeep/releases) and follow the [binary installation guide](https://hitkeep.com/guides/installation/binary/).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 147 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="./frontend/dashboard/public/hitkeep-wordmark-white.png">
  4. <source media="(prefers-color-scheme: light)" srcset="./frontend/dashboard/public/hitkeep-wordmark-blue.png">
  5. <img src="./frontend/dashboard/public/hitkeep-wordmark-blue.png" alt="HitKeep" width="352">
  6. </picture>
  7. </p>
  8. <h1 align="center">AI native, sovereign, privacy-first web analytics in one binary.</h1>
  9. <p align="center">
  10. 100% open source under MIT, HitKeep unifies traffic, conversions, Search Console, and AI visibility with custom tracking domains, SSO, open exports, and no separate database, queue, or cache.
  11. </p>
  12. <p align="center">
  13. <a href="https://hitkeep.com/guides/installation/">Self-host</a> ·
  14. <a href="https://hitkeep.com/guides/introduction/">Documentation</a> ·
  15. <a href="https://hitkeep.com/cloud">Cloud</a> ·
  16. <a href="https://hitkeep.com">Website</a>
  17. </p>
  18. <p align="center">
  19. <a href="https://github.com/HitKeep/hitkeep/releases"><img alt="Latest release" src="https://img.shields.io/github/v/release/HitKeep/hitkeep?sort=semver"></a>
  20. <a href="https://github.com/HitKeep/hitkeep/actions/workflows/ci.yml"><img alt="Continuous integration status" src="https://github.com/HitKeep/hitkeep/actions/workflows/ci.yml/badge.svg?branch=main"></a>
  21. <a href="./LICENSE"><img alt="MIT license" src="https://img.shields.io/github/license/HitKeep/hitkeep"></a>
  22. <a href="https://hub.docker.com/r/pascalebeier/hitkeep"><img alt="Docker pulls" src="https://img.shields.io/docker/pulls/pascalebeier/hitkeep?logo=docker&label=docker%20pulls"></a>
  23. <a href="https://www.bestpractices.dev/projects/11990"><img alt="OpenSSF Best Practices badge" src="https://www.bestpractices.dev/projects/11990/badge"></a>
  24. </p>
  25. ![HitKeep dashboard showing traffic metrics, a 30-day comparison chart, and analytics navigation](./.github/assets/dashboard-overview.png)
  26. ## Why HitKeep
  27. - **100% open source.** The complete product is MIT-licensed. Custom tracking domains and team SSO live in the same public codebase—not in a separate proprietary edition.
  28. - **Full data sovereignty.** Self-host one Go binary with embedded DuckDB and NSQ, or export your data in open formats. Complete takeout, APIs, webhooks, share links, and permissions keep the data useful outside HitKeep.
  29. - **AI-native analytics.** HitKeep treats AI as a first-class traffic channel: crawler fetches, AI-referred visits, and chatbot outcomes remain distinct. Ask AI uses cited aggregate evidence, while read-only MCP gives approved assistants governed analytics access.
  30. - **Privacy by default.** The browser tracker sets no analytics cookies, respects Do Not Track, and collects focused website analytics without building a cross-site identity.
  31. - **Reporting that reaches the outcome.** Follow acquisition through pages, automatic and custom events, goals, funnels, ecommerce revenue, UTM and QR campaigns, Search Console, and Web Vitals.
  32. Self-host the complete open-source product, or use [HitKeep Cloud](https://hitkeep.com/cloud) in a managed EU or US region when you do not want to operate it yourself.
  33. HitKeep is web-focused. It favors aggregate traffic and conversion evidence over visitor profiles, session replay, mobile SDKs, or built-in experimentation. The result is a smaller collection boundary and operating surface without stopping at a basic pageview counter.
  34. ## Quick Start
  35. On Apple silicon macOS or x86_64 Linux, install HitKeep with Homebrew:
  36. ```bash
  37. brew install HitKeep/hitkeep/hitkeep
  38. hitkeep --version
  39. ```
  40. Follow the [Homebrew installation guide](https://hitkeep.com/guides/installation/homebrew/) to configure and start HitKeep. On Linux ARM64, use the published ARM64 binary or Docker instead.
  41. For a production-oriented self-hosted setup, download the Docker Compose file and environment template:
  42. ```bash
  43. mkdir hitkeep && cd hitkeep
  44. curl -fsSLo compose.yml https://raw.githubusercontent.com/HitKeep/hitkeep/main/examples/compose.yml
  45. curl -fsSLo .env https://raw.githubusercontent.com/HitKeep/hitkeep/main/examples/.env.example
  46. ```
  47. Open `.env` and replace `paste-the-generated-value-here` with a long random value from your password manager. Then start HitKeep:
  48. ```bash
  49. docker compose up -d
  50. ```
  51. Open [http://localhost:8080](http://localhost:8080) and create the first account. Keep `.env` private and retain the same secret across restarts.
  52. Before exposing an instance publicly, follow the [Docker Compose guide](https://hitkeep.com/guides/installation/docker-compose/) for HTTPS and trusted proxies, then review [backups](https://hitkeep.com/guides/data/backups-and-restore/) and the [configuration reference](https://hitkeep.com/reference/configuration/). For a native Linux service, download an AMD64 or ARM64 binary from [GitHub Releases](https://github.com/HitKeep/hitkeep/releases) and follow the [binary installation guide](https://hitkeep.com/guides/installation/binary/).
  53. ## Authentication
  54. Native apps sign in through the system browser. Native Android passkeys are disabled until the operator configures the release app's signing certificate and verified domain association.
  55. See the [security reference](https://hitkeep.com/reference/security/), [social sign-in setup](https://hitkeep.com/guides/security/social-sign-in/), and [native Android passkey setup](https://hitkeep.com/guides/security/two-factor-authentication/#native-android-passkeys-operator-setup).
  56. ## Track Your First Site
  57. Create a site in the dashboard, then add the tracker to your pages:
  58. ```html
  59. <script async src="https://analytics.example.com/hk.js"></script>
  60. ```
  61. Pageviews and supported automatic interaction events—outbound clicks, file downloads, and form submissions—start flowing immediately. Use the [custom events guide](https://hitkeep.com/guides/tracking/custom-events/) for product-specific actions such as signups, purchases, or qualified leads.
  62. ## Explore HitKeep
  63. <details>
  64. <summary>See AI visibility, ecommerce, Search Console, Ask AI, and Assistants</summary>
  65. ### AI visibility
  66. ![HitKeep AI visibility report separating crawler fetches, AI referrals, and related activity](./.github/assets/analytics-ai-visibility.png)
  67. ### Ecommerce
  68. ![HitKeep ecommerce analytics showing revenue KPIs, trends, top products, and revenue sources](./.github/assets/analytics-ecommerce.png)
  69. ### Search Console
  70. ![HitKeep Search Console report showing clicks, impressions, click-through rate, position, and query trends](./.github/assets/analytics-search-console.png)
  71. ### Ask AI
  72. ![HitKeep Ask AI answer with completed analytics tools, cited evidence, a table, and a safe dashboard action](./.github/assets/feature-ask-ai-answer.png)
  73. ### Assistants
  74. ![HitKeep Assistants setup showing the MCP endpoint, connection guides, and OAuth access controls](./.github/assets/mcp.png)
  75. </details>
  76. ## Documentation, Community, and Support
  77. Find answers in the documentation, report reproducible bugs through GitHub Issues, and disclose vulnerabilities privately through the security policy.
  78. <details>
  79. <summary>Contributor quick path</summary>
  80. Run `./hk setup`, then start seeded development with `./hk dev --seed` or use `./hk dev --detach`. Capture product proof with `./hk screenshot`; inspect `./hk catalog commands --output json` and `./hk catalog configuration --output json` instead of copying mutable workflow facts. Validate with `./hk qa pr`. The Compose stack and complete workflow live in [CONTRIBUTING.md](./CONTRIBUTING.md).
  81. </details>
  82. - **Operate:** [Installation](https://hitkeep.com/guides/installation/) · [Configuration](https://hitkeep.com/reference/configuration/) · [REST API](https://hitkeep.com/api/) · [Goals](https://hitkeep.com/guides/analytics/goals/) · [Funnels](https://hitkeep.com/guides/analytics/funnels/)
  83. - **Evaluate:** [Comparison library](https://hitkeep.com/vs/) · [Compliance](https://hitkeep.com/compliance/overview/) · [Releases](https://github.com/HitKeep/hitkeep/releases) · [Changelog](./CHANGELOG.md)
  84. - **Contribute:** [Contributor guide](./CONTRIBUTING.md) · [Security policy](./SECURITY.md) · [Issues](https://github.com/HitKeep/hitkeep/issues)
  85. - **Support open source:** [Fund HitKeep on GitHub Sponsors](https://github.com/sponsors/PascaleBeier) or [make a one-time contribution](https://www.paypal.me/kreuztal).
  86. ## License
  87. HitKeep is distributed under the [MIT License](./LICENSE).
  88. ### DuckDB extensions
  89. HitKeep includes the DuckDB extensions required for S3 backups and XLSX exports.
  90. It does not download extensions at startup. On first use, bundled files are
  91. extracted into `HITKEEP_DATA_PATH/.duckdb/extensions`; this directory must be
  92. writable by the process running HitKeep and reside on a mount without `noexec`.
  93. The cache is disposable and can be
  94. recreated without network access. No `HOME` override or separate extension
  95. installation is needed for binary, Homebrew, or container deployments.
  96. Contributor instructions for DuckDB upgrades are in
  97. [the extension bundle documentation](duckdbextensions/README.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.