{"id":"5b65cc06-45be-4942-9af7-be5936edf21e","slug":"hitkeep-hitkeep","kind":"mcp","name":"hitkeep","summary":"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.","owner":"HitKeep","repoUrl":"https://github.com/HitKeep/hitkeep","license":"MIT","licenseTier":"permissive","trust":"community","stars":99,"match":null,"fewStars":false,"format":"mcp","createdAt":"2025-11-08T11:56:11.000Z","addedAt":"2026-10-25T13:26:08.266Z","logoUrl":"https://avatars.githubusercontent.com/u/347324614?v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["data-analytics","databases","memory-knowledge"],"tags":["analytics","go","ai-analytics","ai-visibility","analytics-dashboard","conversion-analytics","cookieless","duckdb"],"runtime":"go","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-25T13:26:08.258Z","sample":false,"url":"https://conduits.dev/tools/hitkeep-hitkeep","language":"Go","transports":["stdio"],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"<p align=\"center\">\n  <picture>\n    <source media=\"(prefers-color-scheme: dark)\" srcset=\"./frontend/dashboard/public/hitkeep-wordmark-white.png\">\n    <source media=\"(prefers-color-scheme: light)\" srcset=\"./frontend/dashboard/public/hitkeep-wordmark-blue.png\">\n    <img src=\"./frontend/dashboard/public/hitkeep-wordmark-blue.png\" alt=\"HitKeep\" width=\"352\">\n  </picture>\n</p>\n\n<h1 align=\"center\">AI native, sovereign, privacy-first web analytics in one binary.</h1>\n\n<p align=\"center\">\n  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.\n</p>\n\n<p align=\"center\">\n  <a href=\"https://hitkeep.com/guides/installation/\">Self-host</a> ·\n  <a href=\"https://hitkeep.com/guides/introduction/\">Documentation</a> ·\n  <a href=\"https://hitkeep.com/cloud\">Cloud</a> ·\n  <a href=\"https://hitkeep.com\">Website</a>\n</p>\n\n<p align=\"center\">\n  <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>\n  <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>\n  <a href=\"./LICENSE\"><img alt=\"MIT license\" src=\"https://img.shields.io/github/license/HitKeep/hitkeep\"></a>\n  <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>\n  <a href=\"https://www.bestpractices.dev/projects/11990\"><img alt=\"OpenSSF Best Practices badge\" src=\"https://www.bestpractices.dev/projects/11990/badge\"></a>\n</p>\n\n![HitKeep dashboard showing traffic metrics, a 30-day comparison chart, and analytics navigation](./.github/assets/dashboard-overview.png)\n\n## Why HitKeep\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\nSelf-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.\n\nHitKeep 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.\n\n## Quick Start\n\nOn Apple silicon macOS or x86_64 Linux, install HitKeep with Homebrew:\n\n```bash\nbrew install HitKeep/hitkeep/hitkeep\nhitkeep --version\n```\n\nFollow 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.\n\nFor a production-oriented self-hosted setup, download the Docker Compose file and environment template:\n\n```bash\nmkdir hitkeep && cd hitkeep\ncurl -fsSLo compose.yml https://raw.githubusercontent.com/HitKeep/hitkeep/main/examples/compose.yml\ncurl -fsSLo .env https://raw.githubusercontent.com/HitKeep/hitkeep/main/examples/.env.example\n```\n\nOpen `.env` and replace `paste-the-generated-value-here` with a long random value from your password manager. Then start HitKeep:\n\n```bash\ndocker compose up -d\n```\n\nOpen [http://localhost:8080](http://localhost:8080) and create the first account. Keep `.env` private and retain the same secret across restarts.\n\nBefore 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/).\n\n## Track Your First Site\n\nCreate a site in the dashboard, then add the tracker to your pages:\n\n```html\n<script async src=\"https://analytics.example.com/hk.js\"></script>\n```\n\nPageviews 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.\n\n## Explore HitKeep\n\n<details>\n<summary>See AI visibility, ecommerce, Search Console, Ask AI, and Assistants</summary>\n\n### AI visibility\n\n![HitKeep AI visibility report separating crawler fetches, AI referrals, and related activity](./.github/assets/analytics-ai-visibility.png)\n\n### Ecommerce\n\n![HitKeep ecommerce analytics showing revenue KPIs, trends, top products, and revenue sources](./.github/assets/analytics-ecommerce.png)\n\n### Search Console\n\n![HitKeep Search Console report showing clicks, impressions, click-through rate, position, and query trends](./.github/assets/analytics-search-console.png)\n\n### Ask AI\n\n![HitKeep Ask AI answer with completed analytics tools, cited evidence, a table, and a safe dashboard action](./.github/assets/feature-ask-ai-answer.png)\n\n### Assistants\n\n![HitKeep Assistants setup showing the MCP endpoint, connection guides, and OAuth access controls](./.github/assets/mcp.png)\n\n</details>\n\n## Documentation, Community, and Support\n\nFind answers in the documentation, report reproducible bugs through GitHub Issues, and disclose vulnerabilities privately through the security policy.\n\n<details>\n<summary>Contributor quick path</summary>\n\nRun `./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).\n\n</details>\n\n- **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/)\n- **Evaluate:** [Comparison library](https://hitkeep.com/vs/) · [Compliance](https://hitkeep.com/compliance/overview/) · [Releases](https://github.com/HitKeep/hitkeep/releases) · [Changelog](./CHANGELOG.md)\n- **Contribute:** [Contributor guide](./CONTRIBUTING.md) · [Security policy](./SECURITY.md) · [Issues](https://github.com/HitKeep/hitkeep/issues)\n- **Support open source:** [Fund HitKeep on GitHub Sponsors](https://github.com/sponsors/PascaleBeier) or [make a one-time contribution](https://www.paypal.me/kreuztal).\n\n## License\n\nHitKeep is distributed under the [MIT License](./LICENSE).\n\n### DuckDB extensions\n\nHitKeep includes the DuckDB extensions required for S3 backups and XLSX exports.\nIt does not download extensions at startup. On first use, bundled files are\nextracted into `HITKEEP_DATA_PATH/.duckdb/extensions`; this directory must be\nwritable by the process running HitKeep and reside on a mount without `noexec`.\nThe cache is disposable and can be\nrecreated without network access. No `HOME` override or separate extension\ninstallation is needed for binary, Homebrew, or container deployments.\n\nContributor instructions for DuckDB upgrades are in\n[the extension bundle documentation](duckdbextensions/README.md).\n"}